|
|
The following are Database Connection error messages.
Error Message
%DBCONN-3-BADLICENSEKEY: Bad license key configured for Database Connection.Explanation The license key configured with the dbconn license configuration command is not valid.
Recommended Action Check that the license key was entered correctly in the dbconn license configuration command. Refer to the Database Connection (DBCONN) feature documentation for information on how to obtain a valid license key.
Error Message
%DBCONN-3-BADMODE: Unknown mode '[chars]' configured for server [chars]Explanation The mode configured for the Database Connection (DBCONN) server was rejected by the remote database server.
Recommended Action Contact your Systems Network Architecture (SNA) network administrator to determine the correct name of the mode to use to connect to DB2 on the remote database server.
Error Message
%DBCONN-3-BADRLU: Bad remote LU '[chars]' configured for server [chars]Explanation The remote logical unit (LU) configured for the Database Connection (DBCONN) server is incorrect.
Recommended Action Contact your Systems Network Architecture (SNA) network administrator to determine the correct name of the remote LU for DB2 on the remote database server. Ensure that the SNA network name and the LU name are correct.
Error Message
%DBCONN-3-BADTPNAME: Bad TP name configured for server [chars]Explanation The TP name configured for the Database Connection (DBCONN) server is not recognized by the remote database server.
Recommended Action Configure a TP name that is available on the remote database server. Most DB2 systems will accept the Distributed Relational Database Architecture (DRDA) default TP name of X except for SQL/DS. Contact your Systems Network Architecture (SNA) network administrator or your DB2 administrator to determine the TP name used by your DB2. To use the DRDA default, do not explicitly configure a TP name for your DBCONN server.
Error Message
%DBCONN-3-DRDASYNTAX: DRDA protocol error from server [chars], SYNERRCD x'[hex]'Explanation An unexpected Distributed Relational Database Architecture (DRDA) protocol error has occurred between Database Connection (DBCONN) and the remote database server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug dbconn drda command, and a Systems Network Architecture (SNA) line trace between the router and the remote database server, for the period during which this message appeared.
Error Message
%DBCONN-3-LICENSEEXPERROR: License is expired for Database and Transaction Connection.Explanation This system is using a temporary key for its Database and Transaction Connection. The license is expired.
Recommended Action Contact StarQuest Software to acquire a permanent key.
Error Message
%DBCONN-3-LICENSEEXPWARNING: License is about to expire for Database and Transaction Connection.Explanation This system is using a temporary key for its Database and Transaction Connection. The license is about to expire.
Recommended Action Contact StarQuest Software to acquire a permanent key.
Error Message
%DBCONN-3-LICENSEHWWARNING: Number of connections for TXCONN and DBCONN is at 90%% license limit.Explanation The number of allowed Database and Transaction Connection clients in this system is reaching the limit.
Recommended Action Contact StarQuest Software to acquire more licenses.
Error Message
%DBCONN-5-IDLETIMEOUT: Client [int] connected to server [chars] has timed out after %TE.Explanation The client was idle for too long, and the idle timeout configured for the Database Connection (DBCONN) server has expired.
Recommended Action No action is required.
Error Message
%DBCONN-5-PWDEXPIRED: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The password supplied by the client was rejected by the remote database server because it has expired.
Recommended Action No action is required.
Error Message
%DBCONN-5-PWDINVALID: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The password supplied by the client was rejected by the remote database server.
Recommended Action No action is required.
Error Message
%DBCONN-5-PWDMISSING: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The remote database server requires a user ID and password, but the password was not provided.
Recommended Action No action is required.
Error Message
%DBCONN-5-SECFAIL: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The user ID or password supplied by the client was rejected by the remote database server.
Recommended Action No action is required.
Error Message
%DBCONN-5-SECUNKNOWN: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation An unspecified security failure has occurred. The database host system may be able to provide more specific information.
Recommended Action No action is required.
Error Message
%DBCONN-5-UIDINVALID: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The user ID used to connect to the remote database server is not valid.
Recommended Action No action is required.
Error Message
%DBCONN-5-UIDMISSING: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The remote database server requires a user ID, but the user ID was not provided.
Recommended Action No action is required.
Error Message
%DBCONN-5-UIDREVOKED: APPC security failed, client [int] using userid '[chars]' for server [chars]Explanation The user ID used to connect to the remote database server has been revoked.
Recommended Action No action is required.
Error Message
%DBCONN-5-WLMDOWN: All WLM routes on server [chars] have become unavailable. Recovery is in progress.Explanation A load-balanced Workload Manager (WLM) server has lost connectivity to all destinations in its server list. All client connections to this server will be rejected until a host in the complex becomes available again.
Recommended Action No action is required.
Error Message
%DBCONN-5-WLMMISMATCH: WLM transport type mismatch on server [chars].Explanation The transport type within a server list received from a Workload Manager load- balanced database does not match the transport type of the corresponding Database Connection (DBCONN) server. If the conflicting server list specifies the Systems Network Architecture (SNA) network transport type, the default mode #INTER will be used to establish the connection.
Recommended Action No action is required.
The following are data bus error messages.
Error Message
%DBUS-3-BADCTRLRTYPE: Invalid controller type [dec] in slot [dec]Explanation An interface processor responded with an unknown or illegal controller type when queried. This problem should not happen unless the running software does not support the interface processor in question, or the interface processor fails.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-BADEEPROM: Invalid EEPROM data found for card in slot [dec], card disabledExplanation The ID EEPROM on the indicated card is not programmed correctly.
Recommended Action Call your Cisco technical support representative for a replacement.
Error Message
%DBUS-3-BADHSACONF: Down rev RSP EPROM found HSA system, upgrade EPROM, or remove one RSPExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-CXBUSERR: Slot [dec], CBus ErrorExplanation A processor has reported a bus error. The processor will be reset and will not be used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-DAUGHTER_STATS: Slot [dec] control 0x[hex], status 0x[hex]Explanation A processor has reported an error. This message is sent out in conjunction with other error messages to provide additional information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-DBUSINTERR: Slot [dec], Internal ErrorExplanation A processor has reported an internal error. The processor will be reset and will not used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-DBUSINTERRSWSET: Slot [dec], Internal Error due to VIP crashExplanation A processor has reported an error. The processor will be reset and will not be used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-MSGOVERFLOW: Slot [dec], too many DBUS messagesExplanation A board in the slot identified in the error message has tried to send too many logger messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-NOMAGIC: No magic number found in RP1 EEPROMExplanation The structure containing the system MAC address required by the online insertion and removal (OIR) facility cannot be found in the Route Processor (RP) EEPROM. The RP must be returned for reprogramming.
Recommended Action Return the RP for reprogramming and call your Cisco technical support representative for assistance.
Error Message
%DBUS-3-NORESP: bad or no response, slot [int]Explanation A board in the slot identified in the error message has failed to respond.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-NOSUPPORT: No driver support in this image for [chars] in slot [dec] (card type [dec]) - disabledExplanation The Cisco IOS image does not have driver support code for the specified interface processor.
Recommended Action Remove the unsupported interface processor card or reload the router with a Cisco IOS image that has driver support code for that interface processor card. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-SLOTCOMP: Slot [dec], dbus error, slot (0x[hex]) and complement (0x[hex]) do not matchExplanation A processor has reported a mismatch between the contents of the slot register and its complement. This condition indicates a hardware failure in the diagnostic bus controller on that processor or on the diagnostic bus. The processor will be reset and will not be used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-SW_NOTRDY: DBUS software not ready after [chars], elapsed [int], status 0x[hex]Explanation An interface processor failed to appear online after being reset. A software or hardware has error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-2-UNKNOWN: Slot [dec], unknown controller type 0x[hex], ignoringExplanation A processor has reported a controller type that is unknown to the system. The processor will not be used and must be repaired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-WCSCTRLRERR: Slot [dec], WCS Controller Instruction ErrorExplanation The writable control store (WCS) is the set of devices on each interface processor that contains the running microcode. It can be loaded either from the ROM on the interface processor or from the system by using the downloadable microcode facility. In this message, a processor reported a WCS controller instruction error. The processor will be reset and will not be used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-WCSERR: Slot [dec], WCS controller in error state (0x[hex]), resettingExplanation The processor in the slot identified in the error message has reported a writable control store (WCS) controller error. The processor will be reset and new microcode will be loaded. This error message appears only when microcode is downloaded.
Recommended Action Reset the processor and load new microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-WCSFLOW: Slot [dec], flow cntrl error loading WCS, last data 0x[hex] pos [dec]Explanation A processor has indicated an error condition while downloading microcode. The status, cmd/data, and position+ numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted and the ROM microcode is loaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-WCSLDERR: Slot [dec], error loading WCS, status 0x[hex] cmd/data 0x[hex] pos [dec]Explanation A processor has indicated an error condition while downloading microcode. The status, cmd/data, and position numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted and the ROM microcode is loaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-WCSPARERR: Slot [dec], WCS Controller Parity ErrorExplanation A processor has reported a writable control store (WCS) parity error. The processor will be reset and will not be used until the next OIR event or microcode download, when it will be retested.
Recommended Action Replace the processor or download microcode. If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DBUS-3-XILINX: ready wait timeout, slot [int]Explanation The field-programmable gate arrays on an interface processor failed to load after being reset. This error indicates a probable software or hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are ATM access concentrator PCI port adapter error messages.
Error Message
%DCU-3-DCU_RESET: [chars]: DCU keep-alive failure, card resetExplanation The port adapter has stopped processing keepalives.
Recommended Action The system should recover. No action is required.
Error Message
%DCU-1-NODCUPORTS: The maximum number of DCU ports ([dec]) is exceededExplanation The system has detected too many DCU ports.
Recommended Action Check the configuration. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DCU-1-NOMEMORY: No memory available for [chars] [dec]Explanation Memory exhaustion has occurred.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
The following are DEC21140 Fast Ethernet controller error messages.
Error Message
%DEC21140-5-COLL: [chars] excessive collisionsExplanation A Fast Ethernet packet has been dropped because too many attempts to transmit it were stopped by collisions. This problem can be caused by a Fast Ethernet segment that is full to capacity or by other malfunctioning equipment on the LAN.
Recommended Action No action is required.
Error Message
%DEC21140-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bayExplanation The number of interfaces found was not what was expected. This error may indicate a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-3-DUPLEX_SPEED: [chars] doesn't support the configured duplex and speed combinationExplanation The Fast Ethernet port was configured for a speed and duplex combination that this particular hardware does not support.
Recommended Action Specify a different duplex and speed combination. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-3-ERRINT: [chars] csr0=[hex], csr5=[hex]Explanation The Fast Ethernet controller has signaled an error condition on the specified port.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-1-INITFAIL: [chars] timed out, csr5=[hex]Explanation The Fast Ethernet port initialization has failed. This error can be caused by disconnected cabling or a failure to detect the media in use.
Recommended Action Check the cabling. Try initializing the port again. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-5-JABBER: [chars] transmit timed outExplanation The transmitter for the Fast Ethernet port of the port adapter has timed out and has caused the transmission of a packet to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-5-LATECOLL: [chars] transmit errorExplanation Late collisions happen when a collision occurs after the preamble has been sent. The packet will be sent, but this problem could indicate that another device is failing to detect when the network is in use.
Recommended Action If this message recurs, check for other malfunctioning devices on the Fast Ethernet. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-5-LOSTCARR: [chars] cable/transceiver problem?Explanation The Fast Ethernet port lost its carrier while transmitting,. This means that it is no longer receiving signals from the LAN. This problem can be caused by disconnected Fast Ethernet cabling or a transceiver failure.
Recommended Action Check the Fast Ethernet wiring and port adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-5-NOCARR: [chars] cable/connector problem?Explanation The Fast Ethernet port did not find a carrier when preparing to send a packet. This means that it is no longer receiving signals from the LAN. This problem can be caused by disconnected Fast Ethernet cabling or a transceiver failure.
Recommended Action Check the Fast Ethernet wiring and the port adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-2-NOISL: Interface [chars] does not support ISLExplanation The Inter-Switch Link (ISL) is not supported on the hardware of the specified interface.
Recommended Action No action is required.
Error Message
%DEC21140-3-NOTDEC21140: Bay [dec] device ID seen as [hex], expected [hex]Explanation The Fast Ethernet driver has failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-3-OWNERR: [chars] packet buffer, pak=0x[hex]Explanation An internal software inconsistency exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-3-RXFIFO: [chars] overflow errorExplanation The Fast Ethernet receiver was unable to send received data to a hardware buffer because the input rate exceeded the ability of the receiver to handle the data. This problem could be caused by excessive system load.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-3-UNDERFLO: [chars] transmit errorExplanation The Fast Ethernet transmitter was ready to go before a packet was in the buffer. This problem could be caused by excessive system load.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DEC21140-5-WATCHDOG: Enormous packet received on [chars]Explanation A packet received from the Fast Ethernet was dropped because of its excessive size.
Recommended Action Adjust the maximum transmission unit (MTU) of the interface if necessary. Otherwise, no action is required.
The following are Dynamic Host Configuration Protocol (DHCP) Server error messages.
Error Message
%DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client [chars] declined %I.Explanation The DHCP client has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, use the clear ip dhcp conflict command.
Recommended Action Resolve the misconfiguration. Clear the conflict from the DHCP database.
Error Message
%DHCPD-2-MALLOC_ERROR: There is inadequate memory for DHCP services.Explanation The Dynamic Host Configuration Protocol (DHCP) could not allocate mandatory data structures.
Recommended Action Add more memory.
Error Message
%DHCPD-2-NO_PROCESS: DHCP could not start its [chars] process.Explanation The Dynamic Host Configuration Protocol (DHCP) could not start one of its processes.
Recommended Action Add more memory.
Error Message
%DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged %I.Explanation The Dynamic Host Configuration Protocol (DHCP) server has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, execute the clear ip dhcp conflict command.
Recommended Action Resolve the misconfiguration. Clear the conflict from the DHCP database.
Error Message
%DHCPD-2-READ_DEADLOCK: DHCP has detected a deadlock condition (excessive read failures).Explanation The Dynamic Host Configuration Protocol (DHCP) server could not read the bindings from any database agent. All read attempts have failed. To prevent a possible deadlock, the server has made all pool addresses available for assignment.
Recommended Action Verify that all the URLs are correct and ensure that connectivity exists between the server and all database agents. Check for corrupt database files. All files must contain the time and end keywords. Enter the show ip dhcp database command. If there are aborted file transfers, increase the appropriate timeouts. Restart the DHCP server.
Error Message
%DHCPD-3-READ_ERROR: DHCP could not read bindings from [chars].Explanation The Dynamic Host Configuration Protocol (DHCP) server could not read bindings from the specified database agent.
Recommended Action Verify that the URL is correct and that connectivity exists between the server and database agent. Check for a corrupt database file. The file must contain the time and end keywords. Enter the show ip dhcp database command. If there are aborted file transfers, increase the database transfer timeout.
Error Message
%DHCPD-2-RECVMSG_ERROR: Recvmsg failed unexpectedly. DHCP services have been terminated.Explanation The reason for this failure is unknown.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DHCPD-4-RELAY_ONLY: DHCP will run as a relay agent only.Explanation The Dynamic Host Configuration Protocol (DHCP) could not start its database process. The server component has been disabled. Only the relay agent is active.
Recommended Action Add more memory.
Error Message
%DHCPD-2-SOCKET_ERROR: DHCP could not open UDP port [int].Explanation The Dynamic Host Configuration Protocol (DHCP) could not open the User Datagram Protocol (UDP) port.
Recommended Action Check if another application is using the UDP. If the port is available, add more memory.
Error Message
%DHCPD-3-WRITE_ERROR: DHCP could not write bindings to [chars].Explanation The Dynamic Host Configuration Protocol (DHCP) server could not write bindings to the specified database agent.
Recommended Action Verify that the URL is correct and that connectivity exists between the server and database agent. Enter the show ip dhcp database command. If there are aborted file transfers, increase the database transfer timeout.
The following are dial-on-demand routing (DDR) error messages.
Error Message
%DIALER-6-BIND: Interface [chars] bound to profile [chars]Explanation A dialer interface has been bound to a dialer profile.
Recommended Action No action is required.
Error Message
%DIALER-2-CIRCUITCOUNT: Dialer count 0 on [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALER-2-NOSWIDB: No software interface associated with hw interface [chars]Explanation An internal software error has occurred.
Recommended Action Call your Cisco technical support representative, and report the error message, the system version, and the router configuration. Use the show version command to obtain the software version.
Error Message
%DIALER-2-NULLPTR: Unexpected null pointer in [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALER-6-UNBIND: Interface [chars] unbound from profile [chars]Explanation A dialer interface has been unbound to a dialer profile.
Recommended Action No action is required.
The following are dial peer configuration error messages.
Error Message
%DIALPEER_DB-3-ADDPEER_MEM_THRESHOLD: Addition of dial-peers limited by available memoryExplanation The available memory does not permit the addition of more dial peers.
Recommended Action In order to be able to add more dial-peers, increase the processor memory.
Error Message
%DIALPEER_DB-3-ADDPEER_PLATFORM_LIMIT: Addition of dial-peers limited by platformExplanation This platform does not permit the addition of more dial peers.
Recommended Action Reduce the number of dial peers in your numbering plan.
Error Message
%DIALPEER_DB-6-ADDPEER_WARNING: Addition of too many dial-peers may affect performanceExplanation The number of dial peers is high. This will have an effect on the dial-peer lookup time, resulting in longer call setup time.
Recommended Action Use the minimum number of dial peers necessary for your numbering plan.
The following are dial shelf error messages that involve the router shelf.
Error Message
%DIALSHELF-2-DSCDOWN: DSC in slot [dec] changes state to down.Explanation The Dial Shelf Controller (DSC) in the dial shelf has gone down.
Recommended Action Try to bring up that DSC by checking the liquid crystal display (LCD) and LEDs of the DSC and by ensuring that the Ring Station (RS)-to-DSC connection functions. If the DSC does not come back up, report the error to your Cisco technical support representative.
Error Message
%DIALSHELF-3-EVENT: Unknown event [dec] for slot [dec]Explanation The software has generated an unknown event for the specified slot. An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALSHELF-3-INVALIDMSG: [chars] ([dec])Explanation The router shelf has received an invalid message from the Dial Shelf Controller (DSC) in the dial shelf. This is a software error or compatibility issue. Check the software versions on the router shelf and the DSC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALSHELF-3-MSG: Unknown message type [dec] from DSCExplanation The router shelf has received an unknown message from the Dial Shelf Controller (DSC) in the dial shelf. This is a software error or compatibility issue. Check the software versions on the router shelf and the DSC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALSHELF-6-RELOAD: Reload requested for card in shelf [dec] slot [dec].Explanation The hw-module slot [shelf] | [slot] reload command was entered. This message is a confirmation that the command is being processed.
Recommended Action No action is required.
Error Message
%DIALSHELF-3-SLOTSTATUS: Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]Explanation The software has detected an invalid state change for the specified slot. This is a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALSHELF-2-TIMEOUT: [chars] slot [dec] after [dec] secs in state '[chars]'Explanation The specified dial shelf slot has timed out. A software or hardware component has failed.
Recommended Action Try removing and reinserting the card. If removing and reinserting the card does not help, try a different card. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALSHELF-2-UNDEFCARD: Card type [dec] in slot [dec]Explanation The software does not have a driver for the card in the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIALSHELF-4-UNRECOMMENDED: Number of [chars] may exceed recommended configurationExplanation On NPE200, more than one CT3 or more than two T1s or E1s are installed, exceeding the recommended configuration parameters.
Recommended Action Stay within recommended limit of CT3s, T1s, and E1s, install a split dial shelf configuration, or upgrade the router shelf to NPE300.
The following are director server error messages.
Error Message
%DIRECTOR-3-BADCOMPL: plug-in returned orphan statusExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIRECTOR-3-DRPDOWN: DRP [int] was down [atalk_address] ago in the last [dec] minute period ! There may be problems related to this DRP server.Explanation The remote Director Response Protocol (DRP) agent has not responded within the time period reported.
Recommended Action Ensure that the remote DRP agent is running and that it is accessible from the system reporting the problem. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIRECTOR-3-NOALIAS: [chars] can not create ip aliasExplanation A resource problem has probably occurred within the system.
Recommended Action Reboot the system as soon as possible. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIRECTOR-3-NOPORT: [chars] port in useExplanation The IP address requested is already in use on an interface connected to the system or within the system itself.
Recommended Action Either select another IP address for use or locate the system making use of this address and reconfigure it to use another address.
Error Message
%DIRECTOR-3-NOPROC: unable to create [chars] processExplanation A resource problem within the system.
Recommended Action Reboot the system as soon as possible. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIRECTOR-3-NOSOCKET: [chars] unable to create socketExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DIRECTOR-3-NOWRITE: [chars] unable to write to socketExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are data-link control (DCL) error messages.
Error Message
%DLC-3-BADPARAM: Function [chars]: value [hex] passed in parameter [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLC-3-INVPCEP: Close Station, invalid P_CEPExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLC-2-NOMEMORY: no memory for [chars]Explanation There was not enough free memory to complete the operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLC-3-WPUTERR: unknown port type [hex]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are data-link switching (DLSw) error messages.
Error Message
%DLSWC-3-BADCLSI: [chars] primitive not valid for dlsw [chars] [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSICNF: [chars] Invalid confirm [chars] [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSIDATALEN: [chars] Bad data len = [dec] [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSIHDRLEN: [chars] Bad header len = 0x[hex] [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSIIDTYPE: [chars] Invalid ID type = 0x[hex] [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSIIND: [chars] Invalid indication [chars], [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSIPRIMTYPE: [chars] Invalid primitive type = 0x[hex] [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSIRET: [chars] Invalid ret code (0x[hex]) [chars], [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADCLSISAP: [chars] Bad clsi SAP id = [hex] [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADDLCOP: dlsw_action, bad dlc event [dec], [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADPEEROP: bad peer op in peer_to_core [dec]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADSSPEVENT: dlsw_action, bad ssp event [dec], [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADSSPHDR: bad ssp hdr in proc ssp - [chars] = 0x[hex]Explanation A Silicon Switch Processor (SSP) header that was received from the remote peer contains errors in one of the fields.
Recommended Action If the remote peer is not a Cisco router, confirm that it supports the DLSw RFC 1795 standard.
Error Message
%DLSWC-3-BADSSPOP: bad ssp op in proc ssp [dec]Explanation A Silicon Switch Processor (SSP) frame containing an invalid command has been received from the remote peer. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Recommended Action If the remote peer is not a Cisco router, confirm that it supports the DLSw RFC 1795 standard. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-BADTIMEROP: dlsw_action, bad timer event [dec], [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-FAILASSERT: Assertion failed: [chars]Explanation An internal software inconsistency has occurred. The router continues to operate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-FORKFAIL: Can't fork : [chars] processExplanation The DLSw process cannot run.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory. If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-FSMACTION: [chars]Explanation This messages identifies the frames sent by DLSw on the LAN or WAN side. This message indicates normal behavior.
Recommended Action No action is required.
Error Message
%DLSWC-3-FSMCALL: [chars] state [chars], event: [chars][chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-FSMERR: fsm error [chars] [chars] [chars] event: [chars][chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-FSMINTERR: fsm internal error - [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-FSMUNKERR: [chars] [dec]: [chars] [chars] event:[chars][chars] input: [dec] [dec] states: [dec] [dec]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-IDMGR: [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-INVALIDSTATE: finite state machine in invalid stateExplanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-INVALIDTIMER: bad timer pop for [chars], new state [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-NODLSW: no dlsw, [chars]Explanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-NOPARAM: dlsw_action, null param blkExplanation A data-link switching system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-NOPEER: no peer, [chars]Explanation A data-link switching system error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWC-3-RECVSSP: SSP OP = [dec]([chars]) [chars] from [chars]Explanation A Silicon Switch Program (SSP) frame was received from the remote peer.
Recommended Action No action is required.
Error Message
%DLSWC-3-SENDSSP: SSP OP = [dec]([chars]) [chars] to [chars] [chars]Explanation A Silicon Switch Program (SSP) frame was sent to the remote peer.
Recommended Action No action is required.
The following are data-link switching (DLSw) core error messages.
Error Message
%DLSWMasterSlave-3-DLSWMS: [chars]Explanation A DLSw master-slave error has occurred.
Recommended Action No action is required.
Error Message
%DLSWMasterSlave-3-DLSWMSDLX: [chars] [hex] from [sci_notation]Explanation A DLSw master-slave error has occurred.
Recommended Action No action is required.
Error Message
%DLSWMasterSlave-3-DLSWMSRCV: [chars] from [sci_notation]Explanation A DLSw master-slave error has occurred.
Recommended Action No action is required.
Error Message
%DLSWMasterSlave-3-DLSWMSSAP: [chars] [chars]Explanation A DLSw master-slave error has occurred.
Recommended Action No action is required.
The following are data-link switching (DLSw) peer module error messages.
Error Message
%DLSWP-3-PBADVALUE: DLSw: [chars]: invalid [chars] [dec]Explanation An invalid parameter value was passed. This error should not cause any network problems unless it happens repeatedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWP-3-PCAPMISMATCH: DLSw: [chars]: [chars]Explanation The priority keyword was used on one router but not on the other. The priority keyword is an option on the data-link switching (DLSw) remote peer definition. If the priority keyword is used on one router, it must be used on the other one.
Recommended Action If you wish to use prioritization, use it on both routers.
Error Message
%DLSWP-3-PGENERAL: DLSw: [chars] [chars]Explanation A general error condition has been detected. This error should not cause any network problems unless it happens repeatedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DLSWP-3-PLFCHANGE: [chars] [dec]; [chars]Explanation The largest frame size configured in the data-link switching (DLSw) remote peer definition is being changed because the maximum transmission unit (MTU) size configured on the interface, used by DLSw, is less than the configured value of the largest frame on DLSw remote peer definition. The largest frame size is being changed to the maximum frame size configured on the interface.
Recommended Action If you want to use this largest frame size for DLSw, increase the MTU on the interface to a value larger than the largest frame size configured.
Error Message
%DLSWP-3-PNOCOOKIE: DLSw: uninitalized peer [chars] from [int]([dec]) to [int]([dec])Explanation The data-link switching (DLSw) has received a packet on an uninitialized peer connection.
Recommended Action Verify the configuration and the DLSw peer status on both routers.
Error Message
%DLSWP-3-PNOMEM: DLSw: No memory to [chars]Explanation The router has run out of system memory for operation. Probably the router image requires more system memory than the router contains.
Recommended Action Consult your Cisco technical support representative about the memory requirements for the specific image used on the router.
Error Message
%DLSWP-3-PPASSIVE: DLSw: passive open failed from [int]([dec]) -> [dec]Explanation The system does not have enough main memory for TCP to allocate the data structures required to accept an incoming TCP connection. Probably the router image requires more system memory than the router contains.
Recommended Action Consult your Cisco technical support representative about memory requirements for a specific image.
The following are digital/discrete multitone digital subscriber line (DMTDSL) error messages.
Error Message
%DMTDSL-3-BADINITDSL: DMTDSL([dec]/[dec]),interface not initialized.Explanation The ATM network module hardware may be defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DMTDSL-3-DMTHWBAD: DMTDSL([dec]/[dec]), Hardware failed self testExplanation The digital subscriber line (DSL) chipset has failed its self-test.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DMTDSL-3-FAILFINDATM: DMTDSL([dec]/[dec]), Could not find ATM interface.Explanation The digital subscriber line (DSL) network module hardware may be defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DMTDSL-1-INITFAIL: DMTDSL([dec]/[dec]), Init failed, [chars]Explanation The asymmetric digital subscriber line (ADSL) network module hardware may be defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DMTDSL-3-NOMEM: DMTDSL([dec]/[dec]), Out of memoryExplanation The router does not have enough memory installed to run this image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are DECnet error messages.
Error Message
%DNET-3-HEARSELF: Hello type [hex] for my address from [dec].[dec] via [chars]Explanation The system is receiving its own DECnet packets. Either a serial line is looped back or another host with the same DECnet address is already present on the LAN.
Recommended Action Check the serial lines (if present) and the DECnet configuration.
Error Message
%DNET-4-MAPCON: Map entry [dec].[dec] conflicts with adjacency to [dec].[dec]Explanation Your DECnet configuration is incorrect. A host that is specified as nonlocal is present on your local network.
Recommended Action Correct the configuration. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Domain Name System (DNS) server error messages.
Error Message
%DNSSERVER-3-BADQUERY: Bad DNS query from [int]Explanation A client has sent an incorrectly formatted Domain Name System (DNS) query to the server.
Recommended Action Check the DNS server and the network attached to it.
Error Message
%DNSSERVER-3-NOINIT: Can't initialize DNS serverExplanation Ports cannot be initialized for the Domain Name System (DNS) server because of internal problems.
Recommended Action Ensure that the DNS server port is available on the local machine.
Error Message
%DNSSERVER-3-TOOSHORT: DNS query from [int] too shortExplanation A client has sent a short Domain Name System (DNS) query packet to the server.
Recommended Action Check the client and the network attached to it. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are AS5200 T1 BRIMUX error messages.
Error Message
%DPM-3-BADMAGIC: SMP hasn't initialized the DPRAM.Explanation The remote peer has not finished initializing its dual port RAM (DPRAM) .
Recommended Action Check the software compatibility between the peers.
Error Message
%DPM-3-BADSMP: SMP hasn't initialized the DPRAMExplanation The remote peer has not finished initializing its dual port RAM (DPRAM) layout area.
Recommended Action Check the software compatibility between the peers.
Error Message
%DPM-3-NOIDB: Copernico failed on acquiring DPRAM idb.Explanation Internal resources are not sufficient to create the idb (internal descriptor for the interface).
Recommended Action Check the available memory capacity on the router.
Error Message
%DPM-3-OOBINIT: Copernico failed on out-of-band sub-system initialization.Explanation The dual port RAM (DPRAM) initialization failed.
Recommended Action Check the software compatibility between the peers.
The following are Duplicate Ring Protocol error messages.
Error Message
%DRIP-3-DRIPFAIL: DRIP: Assertion failed: [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DRIP-6-DRIP_CONFLICT: DRIP conflict with CRF [dec].Explanation A Duplicate Ring Protocol (DRIP) conflict has occurred. The Concentrator Relay Function (CRF) of either the virtual ring or the pseudo ring is being reused in the network
Recommended Action Ensure that the CRF virtual LAN (VLAN) ID of the virtual ring and the pseudo ring are unique in the network.
The following are Director Response Protocol (DRP) error messages.
Error Message
%DRP-3-MULTICOMMAND: multiple DRP commands encounteredExplanation Multiple Director Response Protocol (DRP) commands were found in a single DRP packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DRP-7-NOROUTE: no route for destination [int]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DRP-3-NOWRITE: unable to send response to [int]:[dec]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DRP-3-SUBNETTED: unable to determine metric for [int], [int] subnettedExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are interface driver operational error messages.
Error Message
%DRVGRP-3-CMD: Interface ([chars]): [chars] (cause :[int])Explanation Interface driver initialization errors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are dial shelf controller (DSC) error messages.
Error Message
%DSC-4-MANUALBOOT: Setting config-register to 0x0 will prevent the feature boards from booting when router shelf is rebootedExplanation The dial shelf controller (DSC) cannot be booted manually.
Recommended Action Set the configuration register to 0x2 for autoboot.
The following are dial shelf controller clock error messages.
Error Message
%DSCCLOCK-3-DUP_PRI: Duplicate priority ([dec]) clock sources: slot [dec] port [dec], and slot [dec] port [dec].Explanation Two split-dial-shelf separate clocks sources (one on each router shelf) have been configured with the same priority.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-FAIL: The System Primary Clock is down. Moving to HOLDOVER state and waiting to see if it comes upExplanation This message is generated whenever the current primary clock becomes invalid. The time-division multiplexing (TDM) clock circuit goes into HOLDOVER state, and a holdover timer is started in order to check whether or not the clock becomes valid within the holdover time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-NOMEMORY: Failed to allocate memory for the DSC clocksExplanation The clock switching software has failed to allocate memory while adding a clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-5-SWITCH1: Clock moving to NORMAL from FREERUN, selected clock is on slot [dec] port [dec] line [dec]Explanation The primary time-division multiplexing (TDM) clock, which has been running off the local oscillator of DSC in FREERUN mode, has switched to the line clock coming in via the specified trunk.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH2: Clock moving to FREERUN from HOLDOVERExplanation The current primary time-division multiplexing (TDM) clock has been deleted. Therefore the system primary has switched to the dial shelf control (DSC) local oscillator, which is the current highest-priority functioning clock. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH3: Clock moving to NORMAL from HOLDOVER, selected clock is on slot [dec] port [dec] line [dec]Explanation The current primary time-division multiplexing (TDM) clock has been deleted. Therefore the system primary has switched to the clock coming in from the trunk specified by the slot/port, which is the current highest-priority good clock. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH4: Switching to the user configured clock on slot [dec] port [dec] line [dec]Explanation The time-division multiplexing (TDM) primary clock is switching from the default clock to the user-configured clock coming in via a trunk. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH5: Switching to the clock on slot [dec] port [dec] line [dec]Explanation The time-division multiplexing (TDM) primary clock is switching to the clock coming in via the trunk specified, most likely after the router shelf and feature boards have reloaded. The phase of the output TDM clock is forced to align with the input reference during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH6: Switching to the clock on slot [dec] port [dec] line [dec] as the current primary has gone badExplanation The time-division multiplexing (TDM) primary clock has switched to a backup clock coming in via the specified trunk since the current primary clock has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH7: Moving to NORMAL mode from HOLDOVER mode, clock is slot [dec] port [dec] line [dec]Explanation The time-division multiplexing (TDM) primary clock, which is in HOLDOVER mode and whose source was a trunk port, has switched to the same trunk port and moved to NORMAL mode with a phase alignment between the input source clock and the output TDM reference clock. The router shelf and the feature boards have probably reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH8: Moving to NORMAL mode from HOLDOVER mode without phase correction, clock is slot [dec] port [dec] line [dec]Explanation The source trunk port of the time-division multiplexing (TDM) primary clock, which had failed, has recovered within the holdover time. Therefore, the primary clock has moved from HOLDOVER to NORMAL state without the phase correction between the input trunk reference and the output TDM clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-SWITCH_ERROR1: Failed to select any clock as the system clock. Remaining in HOLDOVER modeExplanation The clock selection algorithm has failed to select any clock as the time-division multiplexing (TDM) primary clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCCLOCK-3-UP: The System Primary Clock is up. Moving to NORMAL state from HOLDOVERExplanation The time-division multiplexing (TDM) primary clock, which had failed, has recovered within the holdover time. Therefore, the TDM primary clock switched to NORMAL state from HOLDOVER state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are dial shelf controller clock (DSC) error messages.
Error Message
%DSCEXTCLK-5-SWITCH1: Clock moving to NORMAL from FREERUN, selected clock is external clock on DSCExplanation The primary time-division multiplexing (TDM) clock that has been running off the local oscillator of dial shelf controller (DSC) in FREERUN mode is switching to the external network reference clock whose source was the DSC front panel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCEXTCLK-3-SWITCH3: Clock moving to NORMAL from HOLDOVER, selected clock is external clock on DSCExplanation The current primary time-division multiplexing (TDM) clock has been deleted. Therefore, the system primary has switched to the clock coming in via the external network reference clock on the dial shelf controller (DSC) front panel, which is the current highest-priority functioning clock. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCEXTCLK-3-SWITCH4: Switching to the user configured external clock on DSCExplanation The time-division multiplexing (TDM) primary clock is switching from the default clock to the user-configured clock coming in via the dial shelf controller (DSC) front panel clock feed. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCEXTCLK-3-SWITCH5: Switching to the external clock on DSCExplanation The time-division multiplexing (TDM) primary clock is switching to the clock coming in via the dial shelf controller (DSC) front panel, most likely after the router shelf and feature boards have reloaded. The phase of the output TDM clock is forced to align with the input reference during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCEXTCLK-3-SWITCH6: Switching to the external clock on DSC as the current primary has gone badExplanation The current primary clock has failed.The time-division multiplexing (TDM) primary clock is switching to a backup clock coming in via the dial shelf controller (DSC) front panel external clock feed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCEXTCLK-3-SWITCH7: Moving to NORMAL mode from HOLDOVER mode, selected external clock on DSCExplanation The time-division multiplexing (TDM) primary clock, which was in HOLDOVER mode and whose source was the dial shelf controller (DSC) front panel clock, has switched to the same clock and returned to NORMAL mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCEXTCLK-3-SWITCH8: Moving to NORMAL mode from HOLDOVER mode without phase correction, selected external clock on DSCExplanation The dial shelf controller (DSC) front panel clock that is the source of the current time-division multiplexing (TDM) primary clock, which had failed, has recovered within the holdover time. Therefore, the primary clock has moved from a HOLDOVER to a NORMAL state without a phase correction between the input reference and the output TDM clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are dial shelf controller (DSC) redundancy clock error messages.
Error Message
%DSCREDCLK-2-BACTFAIL: Clock on other DSC has failed - immediate clock takeoverExplanation The backup dial shelf controller (DSC) clock has detected a failure on the other DSC clock hardware and will become the active clock manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCREDCLK-2-BACTGONE: Removal of other DSC detected - immediate clock takeoverExplanation The backup dial shelf controller (DSC) clock has detected the removal of the other DSC clock hardware and will become the active clock manager.
Recommended Action Reinstall a DSC clock in the other DSC slot to replace the removed DSC hardware. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCREDCLK-3-BACTIOSF: Other DSC IOS keepalive failure - clock takeoverExplanation The other dial shelf controller (DSC) has failed to respond to keepalives to the current DSC; therefore the current DSC will become the active clock manager.
Recommended Action Recover or replace the failed DSC to provide a backup DSC.
Error Message
%DSCREDCLK-2-BCLKCMDFAIL: Clock command hardware failedExplanation A clock hardware command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSCREDCLK-5-BNORMAL: Backup clock moving to NORMAL to phase lock to active clockExplanation The backup dial shelf controller (DSC) has detected a change to the clock.
Recommended Action No action is required.
Error Message
%DSCREDCLK-3-BTAKEDELAY: Active DSC requests backup to takeover clock - delaying for syncExplanation The other dial shelf controller (DSC) has requested the current DSC to take over active clock management, but the current DSC is waiting for clock hardware synchronization before doing so, to avoid a call loss.
Recommended Action No action is required.
Error Message
%DSCREDCLK-3-BTAKEOVER: Active DSC requests backup to takeover clock - doneExplanation The other dial shelf controller (DSC) has requested the current DSC to take over active clock management, and the current DSC has become the active clock manager.
Recommended Action No action is required.
Error Message
%DSCREDCLK-5-BSWITCHE: Backup clock matched to active clock reference, external clock on DSCExplanation The backup dial shelf controller (DSC) has detected a change in the selected clock reference on the active DSC and has changed its own clock hardware to match the new selection. The selected clock reference is now supplied from the DSC front panel external clock.
Recommended Action No action is required.
Error Message
%DSCREDCLK-5-BSWITCHT: Backup clock matched to active clock reference, slot [dec] line [dec]Explanation The backup dial shelf controller (DSC) has detected a change in the selected clock reference on the active DSC and has changed its own clock hardware to match the new selection. The selected clock reference is now from the specified trunk line.
Recommended Action No action is required.
The following are Cisco AS5800 environment monitor error messages.
Error Message
%DSC_ENV-1-CRITICAL: Slot [dec], [chars] [int] [chars]Explanation The card environmental parameters specified are outside the normal range of operation.
Recommended Action Check the blowers and the ambient room temperature.
Error Message
%DSC_ENV-0-CRITICAL_BLOWER: Slot [dec], [chars]Explanation The fans in the blower unit have failed. Operation of the unit may cause the cards to overheat and shut down.
Recommended Action Power down the dial shelf to avoid overheating. Replace the defective fans.
Error Message
%DSC_ENV-0-DSC_FB_POWERDOWN: Temperature/Voltage has reached a critical level for DSC in slot [dec]. No backup DSC available. Powering down all feature boards in the chassis.Explanation The temperature or voltage sensor has reached a condition outside the acceptable range for the dial shelf controller (DSC). No backup is available to take over the control and monitoring of the feature boards; therefore, all the feature boards are being shut down.
Recommended Action Correct the voltage and temperature problems. If you cannot resolve the problems, call your Cisco technical support representative for assistance.
Error Message
%DSC_ENV-2-NORMAL: Slot [dec], [chars] [chars] [int] [chars]Explanation The environmental parameters that were previously abnormal have returned to normal.
Recommended Action No action is required.
Error Message
%DSC_ENV-0-SHUTDOWN: Slot [dec], [chars] [int] [chars]Explanation The card environmental parameters specified are outside the normal range of operation.
Recommended Action Check the blowers and the ambient room temperature.
Error Message
%DSC_ENV-2-WARNING: Slot [dec], [chars] [int] [chars]Explanation The card environmental parameters specified are outside the normal range of operation.
Recommended Action Check the blowers and the ambient room temperature.
Error Message
%DSC_ENV-2-WARNING_BLOWER: Slot [dec], [chars]Explanation A fan in the blower unit has failed. Operation of the unit can continue, but you should research the fan failure.
Recommended Action Replace the defective fan.
The following are Cisco AS5800 dial shelf controller (DSC) redundancy error messages.
Error Message
%DSC_REDUNDANCY-3-MODECONFLICT: Other DSC/router in split modeExplanation There is another router connected to the dial shelf. In this situation both routers must be configured in split mode.
Recommended Action Configure the other router in split mode.
Error Message
%DSC_REDUNDANCY-3-SLOTCONFLICT: Slot ownership conflict detected for slot [dec]Explanation Another router that is connected to the dial shelf is claiming ownership of a slot that this router is also claiming.
Recommended Action Resolve the ownership conflict by reconfiguring one of the routers so that it does not own the slot.
The following are Cisco AS5800 dial shelf interconnect board error messages.
Error Message
%DSI-3-AGENTSTATUS: Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]Explanation An internal software error has occurred. The software detected an invalid state change for the maintenance bus (MBus) agent of the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSI-3-AGENTSTSCHNG: From [chars] ([dec]) to [chars] ([dec]) for slot [dec]Explanation The software has detected a maintenance bus (MBus) agent state change for the specified slot.
Recommended Action No action is required.
Error Message
%DSI-2-BADPORT: Out of range PCI port [dec]Explanation An internal software error has occurred. The software specified an out-of-range port on the dial shelf interconnect board.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSI-3-EVENT: Unknown event [dec] for slot [dec]Explanation An internal software error has occurred. The software has generated an unknown event for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSI-3-SLOTSTATUS: Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]Explanation An internal software error has occurred. The software has detected an invalid state change for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSI-3-SLOTSTSCHNG: From [chars] ([dec]) to [chars] ([dec]) for slot [dec]Explanation The software has detected a state change for the specified slot.
Recommended Action No action is required.
The following are Digital Signal Processor Device Driver (DSPDD) error messages.
Error Message
%DSPDD-1-DSPFWFAILURE: DSPRM internal error[[chars]:[dec]Explanation The router or access server has detected an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPDD-1-INTERNALERROR: DSPRM internal error[[chars]:[dec]Explanation The router or access server has detected an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPDD-1-NOIOSBUFFERS: IOS buffer pool unavailable [[chars]:[dec]]Explanation The router or access server could not allocate internal resources.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPDD-1-NOIOSMEMORY: IOS memory unavailable [[chars]:[dec]]Explanation The router or access server could not allocate memory for internal data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Digital Signal Processor Device Driver (DSPDD) error messages.
Error Message
%DSPRM-5-DSPFAIL: DSP [dec] in slot [dec], is in the failed stateExplanation The Digital Signal Processor (DSP) entered the FAILED state because of alarm indications.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPRM-3-INSUFFICIENT: Insufficient DSP resources for timeslot [dec] on port [chars]Explanation The configuration requires more Digital Signal Processor (DSP) resources than are available.
Recommended Action Change the configuration to specify fewer used time slots. Install additional DSP resources to allow for more complex configurations. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPRM-5-KEEPALIVE: DSP [dec] in slot [dec], NOT RESPONDING - auto restart([dec] times)Explanation The Digital Signal Processor (DSP) has failed the background keepalive test.
Recommended Action No action is required.
Error Message
%DSPRM-5-UPDOWN: DSP [dec] in slot [dec], changed state to [chars]Explanation The DSP resource changed state.
Recommended Action No action is required.
The following are downstream physical unit (DSPU) error messages.
Error Message
%DSPU-3-ActpuNegResponse: ACTPU Neg rsp received from PU [chars]Explanation The remote physical unit (PU) has rejected the request from the router for a system services control points (SSCP)-PU session.
Recommended Action Verify the PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and if so, correct it. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIBadAdptCorr: CLSI bad Adaptor correlator, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIBadIdentifier: CLSI bad identifier, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIBadIdentifierType: CLSI bad identifier type, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIBadLength: CLSI bad length, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIBadPrimitiveCmd: CLSI bad primitive command, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIBadPrimitiveType: CLSI bad primitive type, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIBadReturnCode: CLSI bad return code: [dec], header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIUnexpctActSapCnf: CLSI unexpected ActivateSapCnf, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIUnexpctDeactSapCnf: CLSI unexpected DeactivateSapCnf, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIUnexpctEnableCnf: CLSI unexpected EnableCnf, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-CLSIUnexpctIdStnInd: CLSI unexpected IdStnInd, header= [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-DSPU_BufferCorrupted: DSPU could not free buffer - buffer corruptedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-LSConnInFailed: Connect in from remote address [chars] failed.Explanation A connection with the remote station could not be established.
Recommended Action Verify the configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connection from this remote station.
Error Message
%DSPU-3-LSConnInFailedNoMem: Connect in from remote address [chars] failed; insufficient memory.Explanation A connection with the remote station could not be established because of insufficient memory in the router.
Recommended Action Correct the low memory problem in the router. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-LSConnInFromHostFailed: Connect in from host [chars] with remote address [chars] failed.Explanation A connection with the remote host could not be established.
Recommended Action Verify the host configuration parameters at the router and at the host. Determine whether the router is configured to accept a connection from this host.
Error Message
%DSPU-3-LSConnInFromPuFailed: Connect in from pu [chars] with remote address [chars] failed.Explanation A connection with the remote physical unit (PU) could not be established.
Recommended Action Verify the PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept connection from this remote PU.
Error Message
%DSPU-3-LSConnOutToHostFailed: Connect out to host [chars] failed.Explanation A connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests.
Error Message
%DSPU-3-LSConnOutToPuFailed: Connect out to pu [chars] failed.Explanation Connection with the remote physical unit (PU) could not be established.
Recommended Action Verify the PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests.
Error Message
%DSPU-3-LSInvalidMaxIFrame: Connection attempt failed from XID= [chars], Invalid MaxIFrame= [dec]Explanation An invalid MaxIFrame value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct the link-station configuration at the remote station.
Error Message
%DSPU-3-LSInvalidWindowSize: Connection attempt failed from XID= [chars], Invalid WindowSize= [dec]Explanation An invalid WindowSize value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct the link-station configuration at the remote station.
Error Message
%DSPU-3-LSNoACTPUCapability: Connection attempt failed from XID= [chars], ACTPU not supportedExplanation The remote station did not request PU 2.0 activation; connection with the remote station is terminated.
Recommended Action Correct the link-station configuration parameters at the remote station to request a system services control point (SSCP)-physical unit (PU) session with the router.
Error Message
%DSPU-3-LSXIDNegotiationError: XID Negotiation Error, bad byte= [dec], bad bit= [dec], sense data= [chars]Explanation An XID3 with an error indication was received from the remote station; connection with the remote station could not be established.
Recommended Action From the CV 22 byte or bit information, determine which field in the XID3 is rejected by the remote station, and correct the link-station configuration parameters at either the router or the remote station.
Error Message
%DSPU-3-NotifyNegRsp: LU [dec] received a Notify Neg Resp from host [chars]Explanation The remote host rejected the request from the router to activate or deactivate an system services control point (SSCP)-logic unit (LU) session.
Recommended Action Verify the host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and if so, correct it. If the problem persists, call your Cisco technical support representative for assistance.
Error Message
%DSPU-3-SnaBadData: Bad SNA data received from PU [chars], data= [chars]Explanation Unrecognized Systems Network Architecture (SNA) data was received from the remote physical unit (PU).
Recommended Action Correct the problem at the remote physical unit (PU). If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%DSPU-3-UnknownXid: XID Format not supported, XID= [chars]Explanation Unsupported exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Configure the remote station to send supported XID (if possible). Supported XID formats are XID Format 0 and XID Format 3.
Posted: Fri Jun 16 11:48:49 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.