|
|
NIC100 driver error messages
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Explanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
Network interface module error messages
Explanation The indicated network interface module (NIM) is not supported because it is not of the correct revision. Certain platforms (Cisco 4500 or Cisco 4700, for example) require some NIMs to be of a minimum revision level.
Recommended Action Upgrade the NIM to the proper level.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The indicated NIM is not supported on this platform.
Recommended Action Remove the NIM.
Online insertion and removal error messages
Explanation The specified hot-swappable card was inserted in the system. The interface(s) on the card will remain administratively disabled until specifically enabled, because they may need to be configured.
Recommended Action This is an informational message only. Configure the interface(s) and enable them.
Explanation A hot-swappable card that was inserted into the system has failed to respond. The card may not be properly seated.
Recommended Action Remove and re-insert the specified card. 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.
Explanation This card is capable of online insertion and removal (OIR) but is not capable of extended online insertion and removal (EOIR). Even though no damage would occur to the hardware, insertion or removal of the card will cause a CBUS complex restart, which would be disruptive to traffic on other cards in the system.
Recommended Action Try to restrict insertion or removal of this card to instances when a CBUS complex restart will be least disruptive. Or, upgrade the card to the latest revision that supports EOIR.
Explanation The specified hot-swappable card was removed from the system.
Recommended Action This is an informational message only. No action is required.
Explanation The OIR facility detected an incorrectly seated card, causing the insertion or removal of this card to fail.
Recommended Action Reseat the card in the indicated slot.
Out of band port error messages
Explanation An asynchronous driver did not respond to the ASYNC RESET command.
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.
Explanation An asynchronous driver cannot send out the oobp message because there is no resource.
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.
Explanation OOBP response time-out at wrong OOBP 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.
Open Shortest Path First error messages
Explanation An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.
Recommended Action No action is required.
Explanation The system received an OSPF packet with a length field of less than normal header size or inconsistent with the size of the IP packet in which it arrived. This indicates an error in the sender of the packet.
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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The router received a link-state advertisement (LSA) with invalid LSA Type. The cause is either memory corruption or unexpected behavior on a router.
Recommended Action From a neighboring address, locate the problem router and reboot it. To determine what is causing this problem, call your Cisco technical support representative for assistance.
Explanation An internal software 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation OSPF has a problem locating the LSA, which could lead to a memory leak.
Recommended Action Check for possible routing problems and monitor the router's log for recurrence of this message. If routing problems are discovered, or if the message recurs, upgrade your software version. If the upgrade fails to correct the problem, contact Cisco technical support.
Explanation An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender.
Recommended Action Check the OSPF configuration of the receiver and the sender for inconsistency.
Explanation An internal 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The router was flagged as an Area Border Router (ABR) without backbone area in the router.
Recommended Action Restart the OSPF process.
Explanation While calculating OSPF routes, the router could not find the link-state advertisement that represents the connected route in the router.
Recommended Action Clear the IP routes in the routing table by entering the clear ip route command.
Explanation The router is not able to find its own router link-state advertisement. This can occur occasionally and self-correct. However, if this message recurs, restart the OSPF process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Explanation OSPF hello, database description, or database request packet was received, but the router could not identify the sender.
Recommended Action This situation should correct itself. If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation OSPF failed while attempting to allocate a router ID from the IP address of one of its interfaces.
Recommended Action Ensure that at least one interface is up and has a valid IP address. If multiple OSPF processes are running on the router, each process needs its own unique router ID. You must have enough up interfaces so that each of them can obtain a router ID.
Explanation An internal 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation OSPF attempted to redistribute a route, but could not find a valid source protocol.
Recommended Action No action is required.
Explanation This message is for information only.
Recommended Action No action is required.
Explanation This message is for information only.
Recommended Action No action is required.
Explanation The software detected an unexpected condition. The router will take corrective action and continue.
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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An inconsistency in an internal state was found and corrected.
Recommended Action No action is required.
Explanation OSPF found inconsistency between its database and IP routing table.
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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The interface reports its bandwidth as zero.
Recommended Action No action is required.
Port adapter error messages
Explanation The port adapter system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).
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.
Explanation The software specified an out-of-range port adapter interface.
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.
Explanation The software specified an out-of-range port adapter bay.
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.
Explanation The port adapter system control block (PASCB) data structure was incorrectly set in the command data structure.
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.
Explanation An attempt to reset and initialize the port adapter timed out.
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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter is being powered off.
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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter is not supported by the controller it is plugged into.
Recommended Action Remove the port adapter and return the controller to its original configuration.
Explanation The system side PCI bridge for this PA failed initialization. The PA will not be operational.
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.
Explanation This message indicates a possible memory shortage or adaptor hardware 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.
Explanation While getting the daughter card information for the chassismib, the platform SNMP code went into an infinite loop.
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.
Explanation An attempt was made to register an interrupt handler for either a non-existent port adapter or the wrong interrupt priority level.
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.
Explanation The software does not have a driver for the port adapter type located in the specified bay.
Recommended Action Ensure that the image you are running supports this card. Check that the card is properly seated. 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.
Explanation The software does not have a driver for the port adapter protocol control information bridge in the specified bay.
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.
X.25 packet assembler/disassembler error messages
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Parser error messages
Explanation This message occurs when a configuration is read from the Trivial File Transfer Protocol (TFTP) server or nonvolatile RAM (NVRAM) and the end of the file is encountered before the end statement. The configuration may be corrupted or incomplete. What was read is in effect.
Recommended Action Ensure that the configuration is good, then execute either a copy running-config startup-config command to write the good configuration to NVRAM, or a copy running-config tftp command to write to a network TFTP server.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An error occurred.
Recommended Action Copy the error message exactly as it appears. Execute a show version command, and copy the displayed information. Contact your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
PPP per-user configuration error message
Explanation The configuration cannot be applied to individual ISDN channels.
Recommended Action You need virtual profiles and virtual access interfaces in order to apply the configuration to ISDN. Refer to the Dial Solutions Configuration Guide for information on virtual profiles.
Protocol-independent multicast error messages
Explanation A downstream PIM router sent a join message for the shared tree, which this router does not want to accept. This behavior indicates that this router will let only downstream routers join to a specific rendezvous point.
Recommended Action Configure all downstream leaf routers to join to the RP that is allowed by upstream routers toward the validated rendezvous point.
Explanation A PIM router received a register message from another PIM router that thinks it is the rendezvous point. If the router is not configured for another rendezvous point, it will not accept the register message.
Recommended Action Configure all leaf routers (first-hop routers to multicast sources) with the IP address of the valid rendezvous point.
Private Network-Network Interface error messages
Explanation A PVC port address assignment has collided with an existing address. An address that would have been assigned by this switch has already been assigned by another.
Recommended Action If possible, assign a new MAC address to the peer system that caused the assignment collision.
Explanation An internal software error 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.
Explanation An invalid packet was received from a network peer.
Recommended Action Check the originating device for a cause of the corrupted packets.
Explanation A source routing request by another network host was corrupted.
Recommended Action Check the originating system for a cause of the problem.
Explanation A configuration error in the PNNI subsystem occurred. The message will display more specific information about the cause of problem.
Recommended Action Change the configuration to correct the error.
Explanation This is an informational message only. It is used by Cisco for testing.
Recommended Action Informational messages can be disabled by changing the logging level.
Explanation An internal software error 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.
Explanation An internal software error occurred. The message contains more information that can be used to identify the 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.
Explanation An internal software error occurred.
Recommended Action Use the show atm pnni trace error command to collect more information. 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.
Explanation An internal software 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error 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.
Packet over SONET double wide PCI port adapter driver error messages
Explanation The POSDW hardware failed. An incorrect number of interfaces was discovered.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The POSDW port adaptor failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The POSDW hardware failed. A non-POSDW device pointed at the software for the POSDW.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software or hardware error occurred. The POSDW driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Point-to-Point Protocol error messages
Explanation The two ends of a serial link have different IPX network numbers.
Recommended Action Confirm the configuration of both devices.
Explanation A Multilink PPP bundle was not appointed. This error message is most likely to be caused by no memory being available.
Recommended Action Record the output of the show memory summary command, then analyze the output to find a possible memory leak.
Explanation A Multilink PPP bundle was not cleared. This error message is most likely to be caused by no memory being available.
Recommended Action Record the output of the show memory summary command, then analyze the output to find a possible memory leak.
Explanation PPP was configured to use the Terminal Access Controller Access Control System (TACACS), but extended TACACS was not configured or was disabled.
Recommended Action Either issue the no ppp use-tacacs command to stop PPP from using TACACS, or issue the tacacs-server extended command to enable extended TACACS.
Explanation A LAN Extender interface could not be found with the specified MAC address when bringing up a LAN Extender link. This is a configuration error.
Recommended Action Refer to the documentation on configuring a LAN Extender Interface.
Explanation A PPP NCP request encountered an internal 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.
Explanation This error message should never occur in normal 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.
MPC860 quad integrated communications controller error messages
Explanation A bad event was detected in the state machine for half duplex transmission/reception.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The clear to send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU).
Explanation The software failed to initialize or restart a 1T serial card.
Recommended Action Clear the serial interface. If the message recurs, call your technical support representative for assistance.
Explanation The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both DCD and DSR.
Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.
Explanation The MPC860/PowerQUICC CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes:
Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.
Explanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Explanation A packet greater than the assigned MTU of this serial interface was queued for transmission.
Recommended Action The system should recover. No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A small packet (less than 2 bytes) was queued for transmission. The interface cannot handle such small packets for transmission.
Recommended Action The system should recover. No action is required. If the message recurs, it may indicate a hardware error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Explanation The software did not expect to see a modem control signal change on this type of WIC card interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Explanation The software does not recognize the type of WIC card plugged into the port module.
Recommended Action Check the part number on the WIC card to verify that it is supported in the Cisco IOS release operational on the router or contact your technical support representative.
Explanation It is not possible to support this type of BRI card in slot 1 with another BRI card in slot 0.
Recommended Action Remove one of the BRI cards from either slot.
Explanation The BRI card is not supported in WIC slot 0.
Recommended Action Power down, move the BRI card to the other WIC slot on the port module and reboot.
Queue and accumulator error messages
Explanation This is a software error.
Recommended Action Copy the error message exactly as it appears. Also copy the output of the show version and show controllers cbus commands. Contact your technical support representative.
Explanation This is a diagnostic message.
Recommended Action This message appears after a QA error, and contains diagnostic information regarding that error. Copy the original QA error message and all the following QA diagnostic error messages exactly as they appear. Also copy the output of the show version and show controllers cbus commands. Contact your technical support representative.
QEM error message
Explanation The QEM driver either found no switch processors or more than one. Exactly one is the only supported configuration.
Recommended Action Ensure that there is only one switch processor.
Qualified Logical Link Control error messages
Explanation Either remote source-route bridging or local acknowledgment is configured incorrectly.
Recommended Action Verify that remote source-route bridging and local acknowledgment are configured correctly.
Explanation An invalid QLLC primitive was detected.
Recommended Action Verify that the partner QLLC device is configured correctly.
Explanation Either remote source-route bridging (RSRB) is incorrectly configured, or the other RSRB device is down.
Recommended Action Verify that remote source-route bridging is configured correctly with the right version of the Cisco IOS software.
Explanation An invalid LLC primitive was detected.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
Explanation The LLC primitive specified placed the router in an invalid state.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
Explanation The IBM Gateway (3172) or front-end processor on the LAN is sending XID Format 3, which is used to communicate with PU2.1 devices. The X.25 device is a PU2.0 (3174) that is configured to send XID Format 1 messages. This is a very rare situation. A likely cause is that the revision levels on the IBM equipment are incompatible.
Recommended Action Check the revision levels on the external equipment, and upgrade them if necessary.
Explanation The partner for this QLLC virtual MAC address does not match the MAC address that was defined with the qllc partner command.
Recommended Action Verify that the qllc partner statement in the configuration file is correct.
Explanation The text string provided with this error message describes the specific QLLC problem.
Recommended Action Follow the instructions that appear with the error message. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An I-Frame was discarded because of network congestion.
Recommended Action Verify that the LAN is not beaconing and that it is not in a congested state. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A remote X.25 device is calling the router for QLLC service using a subaddress that was not configured by the X.25 routing facility. The subaddress was not configured for QLLC service.
Recommended Action Correct the QLLC configuration. Configure only the subaddress on the QLLC service, not the complete X.121 address that the remote X.25 device uses.
Explanation There is an incoming call, but a connection cannot be initiated to a partner since no partner is configured in a qllc dlsw command (for QLLC/DLSw+ only).
Recommended Action Configure a partner for the incoming call (such as by using the qllc dlsw partner command).
Explanation The qllc srb command was not defined for this interface.
Recommended Action Add a valid qllc srb statement for this serial interface.
Explanation An LLC2 session could not be established with the destination MAC address.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Explanation No virtual MAC address was defined for this interface.
Recommended Action Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command.
Explanation There is not enough memory in the system to complete this request.
Recommended Action Add more memory to the router. Otherwise, reduce the configuration or the load on the router.
Explanation An attempt to create an IEEE XID failed.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Explanation A packet was not sent to the LAN.
Recommended Action Verify that the LAN partner is configured correctly, and that the partner is on the desired LAN.
Explanation A QLLC session could not be established.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
Explanation The router ran out of memory to allocate buffers.
Recommended Action Ensure that the router configuration is adequate for the service expected of it. You might want to tune the buffer pools, or upgrade to a larger router. At the very least, you will need more memory.
Explanation No QLLC services have been configured, even though the router will accept incoming calls for QLLC.
Recommended Action Configure the QLLC service required.
Explanation This message is reporting insufficient system memory.
Recommended Action Upgrade the memory.
Explanation The QLLC XID could not be forwarded to the LAN.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
Explanation The specified structure was not configured.
Recommended Action Confirm the configuration commands for the structure.
Explanation A device tried to connect to a QLLC VMAC, but the MAC address of that device does not match the partner in the qllc dlsw command.
Recommended Action Correct the QLLC configuration to match the right partner.
Explanation A software error in the router code occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
MC68360 quad integrated communications controller error messages
Explanation The MC68360/QUICC CPU was unable to access the memory it needs to carry out its functions. The following are some possible causes. The network is large, requiring a great deal of memory for routing tables, and so on. The router configuration has many features enabled, each of which require a certain amount of memory. A software error (memory leak) exists.
Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.
Explanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Explanation The MC68360/QUICC CPU was running an unexpected version of microcode. This could be possible if a new version of the QUICC chip was released or if a very old version was used in the manufacturing process. This could also occur if a new version of microcode was released to fix any bugs.
Recommended Action A decrease in performance might occur for any asynchronous interfaces running PPP. Call your technical support representative if this is an issue.
Asynchronous MC68360 quad integrated communications controller error message
Explanation The clear to send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection
Recommended Action Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU).
Ethernet MC68360 quad integrated communications controller error messages
Explanation An Ethernet cable is broken or unterminated.
Recommended Action Check cables for proper connections, termination, and so on.
Explanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Explanation The Ethernet 10BaseT cable is unplugged.
Recommended Action Connect the 10BaseT Ethernet cable.
Explanation While transmitting a frame, the Ethernet controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Serial MC68360 quad integrated communications controller error messages
Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem stems from a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and or communication equipment such as the channel service unit/data service unit (CSU/DSU).
Explanation The serial interface controller of the QUICC chip could not be initialized or started for operation. There is probably a hardware problem.
Recommended Action Power cycle the system. If the error reoccurs, replace the unit.
Explanation The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both a DCD and a DSR.
Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.
Explanation The RS-232C Carrier Detect (DCD) signal was de-asserted during message reception. The DCE equipment is responsible for asserting this signal.
Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected.
Explanation While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
RADIUS facility error messages
Explanation All RADIUS servers were found to be unresponsive.
Recommended Action Check the network connectivity to the RADIUS servers, and check that the servers are running.
Explanation Quite likely, the system ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation Initial IP-Pool definitions are being retrieved from RADIUS using the given user's profile.
Recommended Action No action is required.
Explanation Initial static routes are being retrieved from RADIUS using the given user's profile.
Recommended Action No action is required.
Explanation Since the configuration has been modified, the unique accounting IDENT cannot be saved to NVRAM.
Recommended Action Save the configuration and try again. If the error persists, call your technical support representative for assistance.
Explanation Saving an accounting ident in NVRAM.
Recommended Action No action is required.
Explanation Could not find the router's hostname. A hostname must be defined, since it determines the RADIUS profile to be retrieved.
Recommended Action Define a hostname in the router's configuration.
Explanation RADIUS is attempting to send a request, but there are no hosts configured to send the request to.
Recommended Action Configure a host using the radius-server command.
Explanation A RADIUS server, which previously was dead, has started responding again.
Recommended Action No action is required.
RADIX error messages
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The system ran out of memory during initialization. This should only occur if an image is too large for the existing dynamic memory.
Recommended Action Use a smaller subset image or upgrade hardware.
Explanation The system is out of memory.
Recommended Action To correct the problem, reduce the number of routes accepted by this router, upgrade hardware, or use a smaller subset image on run-from-RAM platforms.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Remote command error messages
Explanation The IP address for an incoming rcmd request is not registered with Domain Naming System (DNS).
Recommended Action Add the IP address to DNS.
Explanation An attempt was made to connect to a router through remote copy protocol (rcp), but the router was not configured as an rcp server.
Recommended Action Configure an rcp server.
Explanation An attempt was made to connect to a router through remote shell protocol (rsh), but the router was not configured as an rsh server.
Recommended Action Configure an rsh server.
Explanation An attempt was made to connect to a router through the rshell port (514), but the router was not configured as an rsh or rcp server.
Recommended Action Configure an rsh or rcp server.
IP Routing Information Protocol error message
Explanation The requested operation could not be accomplished because of a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Redundant power supply error messages
Explanation The Redundant Power System (RPS) experienced a DC output voltage failure condition in one of the power supplies.
Recommended Action One of the DC outputs has failed on the redundant power supply. For Cisco 3600 and Cisco 2600 redundant power supplies, the "DC Status" LED on the front of the power supply will identify which DC output has failed. For the Cisco 5300 redundant power supply, the "DC OK" LED on the front of the power supply will identify which DC output has failed. When there is a DC failure, you need to replace the redundant power supply.
Explanation The Redundant Power System (RPS) DC Output Voltage is normal.
Recommended Action This is an informational message only. No action is required.
Explanation The Redundant Power System (RPS) experienced a fan failure condition.
Recommended Action One of the fans has failed and you should replace the redundant power supply.
Explanation The Redundant Power System (RPS) fan is now normal.
Recommended Action The redundant power supply previously detected a fan failure condition that has been cleared.
Explanation The Redundant Power System (RPS) experienced an input voltage failure in one of the power supplies.
Recommended Action One of the AC or DC inputs has failed on the redundant power supply. For Cisco 3600 and Cisco 2600 redundant power supplies, the "AC Input" LED on the front of the power supply will identify which AC input has failed. For the Cisco 5300 AC /DC redundant power supply, the "AC OK" LED on the front of the power supply will identify which AC input has failed. For the Cisco 5300 DC/DC redundant power supply, the "DC Input" LED on the front of the power supply will identify which DC input has failed. Make sure that the AC/DC circuit in your building is operational, verify that the power cord is plugged into the redundant power supply, and make sure that the AC/DC power switch on the redundant power supply is on.
Explanation The Redundant Power System (RPS) input voltage is normal.
Recommended Action This is an informational message only. No action is required.
Explanation The Redundant Power System (RPS) experienced multiple failures. This is a critical condition.
Recommended Action There are multiple failures on the redundant power supply. Examine the LEDs on the front of the redundant power supply to find out which failures have occurred.
Explanation The system is operating at a normal temperature.
Recommended Action The system previously detected an over temperature condition that has been cleared. This is probably caused by a high ambient temperature where the router is located.
Explanation The Redundant Power System (RPS) detected an overvoltage condition.
Recommended Action The RPS detected an over voltage condition in one of the internal power supplies. Replace the RPS unit.
Explanation The Redundant Power System (RPS) is operating normally.
Recommended Action This is an informational message only. No action is required.
Explanation The Redundant Power System (RPS) experienced either a fan failure or an over temperature condition.
Recommended Action For Cisco 3600 and Cisco 2600 redundant power supplies, look at the "FAN" and "TEMP" LEDs on the front of power supply. If the "FAN" LED is amber, one of the fans has failed and you should replace the redundant power supply. If the "TEMP" LED is amber, the ambient temperature is too high. For a Cisco 5300 RPS unit, this message is displayed when the ambient temperature is too high.
Explanation The Redundant Power System (RPS) thermal is now normal.
Recommended Action The redundant power supply previously detected an over temperature condition which has now cleared. This was probably caused by a high ambient temperature where the redundant power supply is located. A RPS thermal failure can also be caused by a fan failure in the redundant power supply.
Explanation The Redundant Power System (RPS) voltage is now normal.
Recommended Action The RPS previously detected an over voltage condition that has been cleared.
Route Switch Processor error messages
Explanation An incorrect value has been written on an accumulator.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. A microcode reload can correct the error condition as a workaround.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A packet greater than the maximum possible MTU was processed. Or, an illegal buffer header data area was found.
Recommended Action Call your technical support representative for support.
Explanation The hardware in the indicated slot must be upgraded for operation with the RSP.
Recommended Action Upgrade the board.
Explanation An error was discovered in an IPC message.
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.
Explanation This message indicates the part containing the MAC addresses allocated to this chassis could not be accessed or was found to be corrupt, either because of a hardware problem or manufacturing problem.
Recommended Action Report this error to your technical support representative.
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A command from the RSP to an IP took longer than expected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Memory size mismatch between a master and a slave RSP.
Recommended Action Configure both master and slave RSPs to have an equal amount of memory.
Explanation HSA requires a minimum of 24 MB of memory.
Recommended Action Upgrade your system to meet minimum memory requirements for HSA.
Explanation The ID EEPROM on the RSP is missing or bad.
Recommended Action This message indicates a manufacturing error. Report this error to your technical support representative.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Explanation Firmware for the interface processor experienced a critical condition.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of the show tech-support command.
Explanation An inconsistency was detected between the microcode and the system code.
Recommended Action Report this error to your technical support representative.
Explanation This message indicates miscommunication between the RSP and an IP.
Recommended Action Report this error to your technical support representative.
Explanation The system software failed to reset the master/slave watchdog timer, causing it to time out. This behavior could indicate a software problem or a hardware problem.
Recommended Action Copy the error message exactly as it appears. Copy the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Explanation The characters shown can be either on the slave RSP setting or on the master RSP setting. The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup, the system image detects the mismatch and modifies the ROM monitor setting to conform with these specifications. This mismatch most likely occurred because a new RSP was being installed and booted in a high system availability (HSA) environment (dual RSPs) for the first time. Alternatively, in established HSA configurations, this message may result from a previous Interprocess Communication (IPC) error occurring while the HSA environment is reconfigured.
Recommended Action Using the show version or show boot commands, determine which slot contains the current slave RSP. Using the show configuration command, determine which slot has been specified as the default slave RSP. If there is no slave default-slot command in the configuration file, the value defaults to the highest numbered CPU slot (slot 3 on a Cisco 7507, and slot 7 on a Cisco 7513).
If the slot number obtained in Step 1 is the same as the number obtained in Step 2, then no further action is required. You have configured HSA in simple hardware backup mode, and both RSPs are identical. However, if the two slot numbers differ, you have configured HSA in software error protection mode, and will have different images running, depending on which RSP is currently the slave RSP. If the slot numbers discovered in Steps 1 and 2 differ, reload your router to ensure that the desired system image is running. After the reload, the actual slave RSP will match the default slave RSP specified in (or inferred from) the system configuration file. For details of various HSA configuration modes consult the Cisco IOS Configuration Fundamentals Configuration Guide.
Explanation The master and slave are running incompatible software versions with regard to the master/slave exchange process.
Recommended Action If the slave image global configuration is used to override the default slave image from the bundle, then the slave image is incompatible. Update either the master or slave image to ensure that the two are compatible. If the slave is running the image from the bundle, execute and record the output of the following commands:
Report this information and the error message to your technical support representative.
Explanation A channelized interface driver received a packet on an unconfigured channel.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of the show tech-support command.
Explanation No MAC address was available for allocation to the specified interface.
Recommended Action Report this error to your technical support representative.
Explanation An attempt at memory allocation failed.
Recommended Action To remedy the problem, add memory, disable some features, or apply filtering to decrease the size of system data structures (the routing table, for example). In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation No microcode is defined or available for the specified card.
Recommended Action Reconfigure the card to specify an existing microcode file.
Explanation An error occurred while accessing RSP internal hardware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error was detected during packet switching.
Recommended Action Call your technical support representative for support.
Explanation The cBus buffer memory was reset and reallocated.
Recommended Action Report this error to your technical support representative, if memory is not reset manually (by changing the MTU on an interface, for example).
Explanation The quantity of RSP DRAM is below the recommended amount.
Recommended Action Add DRAM.
Explanation The slave RSP has undergone a hardware state change. Both the old state and new states are shown. Possible states are nonparticipant, slave, master, and unplugged. Possible state changes indicated by this message are any to unplugged, unplugged to nonparticipant, nonparticipant to slave or slave to nonparticipant. Any other combination is unexpected.
Recommended Action The following actions are recommended:
 | Caution Failure to ensure a consistent configuration on a freshly installed slave RSP might result in undefined behavior if the router reloads. |
Explanation The master RSP detected that the slave RSP had taken mastership of the router. The old master RSP will reload and become the slave RSP, letting the new master RSP take over. This behavior indicates a software or hardware error.
Recommended Action Copy the error message exactly as it appears. Copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Explanation Another process is temporarily locking the slave config.
Recommended Action Retry the command that caused the error message. If the error message recurs, check for other execs via the show users command. If you know that there are no other users locking the slave NVRAM, then contact your technical support representative for assistance.
Explanation This is an informational message to indicate that the slave RSP has started running the slave RSP image. This message appears after the router boots or after the slave reload global configuration command is issued on the master RSP.
Recommended Action No action is required.
Explanation Most likely, a board is not fully seated in the chassis. A less likely possibility is a hardware problem with the RSP or backplane.
Recommended Action Try reseating the boards. Call your technical support representative for assistance if this message persists.
Explanation Miscommunication occurred between the RSP and an IP.
Recommended Action Report this error to your technical support representative.
Remote source-route bridging error messages
Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Explanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up-to-date.
Recommended Action Call your technical support representative for an update.
Explanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up-to-date.
Recommended Action Call your technical support representative for an update.
Explanation The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up-to-date.
Recommended Action Call your technical support representative for an update.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The RSRB peer initiation logic failed because of a memory shortage or congestion condition.
Recommended Action The problem should clear and the peers should re-open without operator intervention.
Explanation The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
Explanation The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
Round trip time monitor error messages
Explanation An internal software 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The Round Trip Time Monitor (RTTMON) process could not be started because of a low-memory condition.
Recommended Action Reduce usage of resources in the configuration to resolve the memory shortage. Once the memory shortage is resolved in the configuration, the system will need to be rebooted because this error occurred during system initialization. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Explanation The Round Trip Time Monitor (RTTMON) process could not be started because of a low-memory condition.
Recommended Action Reduce usage of resources in the configuration to resolve the memory shortage. Once the memory shortage is resolved in the configuration, the system will need to be rebooted because this error occurred during system initialization. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Explanation An internal software 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 output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation Configuration of the Round Trip Time Monitor (RTTMON) failed because of the previously-reported memory shortage.
Recommended Action Reduce usage of resources in the configuration to resolve the memory shortage.
Explanation The Round Trip Time Monitor (RTTMON) process could not be started because of a low-memory condition.
Recommended Action Reduce usage of resources in the configuration to resolve the memory shortage. Once the memory shortage is resolved in the configuration, the system will need to be rebooted because this error occurred during system initialization. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
|
|