|
|
This section lists and describes the system error messages for Cisco IOS Release 11.2 P, up to and including 11.2(11)P. The system software sends these error messages to the console (and, optionally, to a logging server on another system) during operation. Not all system error messages indicate problems with your system; some are purely informational, while others may help diagnose problems with communications lines, internal hardware, or the system software.
This section only lists error messages for Cisco IOS Release 11.2 P that are not documented in the Cisco IOS Release 11.2 System Error Messages manual. For additional system error messages, refer to the System Error Messages publication.
The messages are organized according to the particular system facility that produces the messages. The facility sections appear in alphabetical order, and within each facility section, messages are listed alphabetically by mnemonic. Each error message is followed by an explanation and a recommended action.
System error messages begin with a percent sign (%) and are structured as follows:
%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text
FACILITY is a code consisting of two or more uppercase letters that indicates the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. Table 1 lists the system facilities codes.
SUBFACILITY is a code relevant only to Channel Interface Processor (CIP) error messages. There are no CIP error messages listed in this document.
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 2 lists the severity levels.
MNEMONIC is a code that uniquely identifies the error message.
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 3 lists the representations of variable fields and the type of information in them.
| Code | Facility |
|---|---|
| AAA | TACACS+ Authentication, Authorization, and Accounting security |
| AIP | ATM Interface Processor |
| ALIGN | Memory optimization in Reduced Instruction-Set Computer (RISC) processor |
| AMDP2 | Presidio Ethernet & Laguna Fast Ethernet |
| APPN | Advanced Peer-to-Peer Networking |
| ARAP | Apple Remote Access Protocol |
| ASPP | Asynchronous Security Protocol |
| AT | AppleTalk |
| ATM | Asynchronous Transfer Mode |
| BAP | PPP Bandwidth Allocation Protocol (BAP) |
| BGP | Border Gateway Protocol |
| BRI | Integrated Services Digital Network (ISDN) Basic Rate Interface |
| BRIMUX | AS5200 BRIMUX board |
| BSC | Binary Synchronous Communications mode |
| BSTUN | Block serial tunneling |
| C1600 | Cisco 1600 platform |
| C3600 | Cisco 3600 platform |
| C5RSP | Cisco Catalyst 5000 platform |
| CBUS | ciscoBus controller |
| CDM | Cable Data Modem subsystem |
| CI | 75xx platform chassis interface |
| CIP facility | Channel Interface Processor |
| CIRRUS_PM | Slow speed async/sync port module |
| CLEAR | Clear facility |
| CLNS | OSI Connectionless Network Service |
| CLS | Cisco Link Services |
| CLSDR | Cisco Link Services Driver |
| COMP | Point-to-point compression |
| CONTROLLER | Controller |
| CPAD | Compression service adapter |
| CPM | Combo Port Module device driver |
| CSC2 | CSC2/CSC3 CPU cards |
| CT3 | Channelized T3 port adapter |
| DBUS | Data bus |
| DIALER | Dial-on-demand routing |
| DLC | Data-link control |
| DLSw | Data-link switching |
| DMA | Direct memory access |
| DNET | DECnet |
| DRP | Director Response Protocol |
| DSPU | Downstream physical unit |
| DSX1 | Channelized E1 (Europe) and T1(US) telephony standard |
| DUAL | Enhanced Interior Gateway Routing Protocol |
| DVMRP | Distance Vector Multicast Routing Protocol |
| EGP | Exterior Gateway Protocol |
| ENT_API | Entity MIB API |
| ENV | Environmental monitor card |
| ETHERNET | Ethernet for the C1000 series |
| FDDI | Fiber Distributed Data Interface |
| FLASH | Flash nonvolatile memory |
| FR | Frame Relay |
| FTC_TRUNK | Cisco 3801 platform |
| GRIP | Xerox Network Systems (XNS) Routing Protocol |
| HD | HD64570 serial controller |
| HOOD | LAN controller 100VG-AnyLAN interface |
| HP100VG | 100VG-AnyLAN PA driver |
| HUB | Cisco Ethernet hub |
| IBM2692 | IBM Token Ring chip set |
| IFS | IOS File System |
| IGRP | Interior Gateway Routing Protocol |
| ILACC | ILACC driver |
| INTERFACE_API | Binary API for the interface descriptor block |
| IP | Internet Protocol |
| IPC | Interprocess Communication |
| IPFAST | IP fast switching |
| IPRT | Internet Protocol routing |
| IPX | Internetwork Packet Exchange Protocol |
| IP-SNMP | Simple Network Management Protocol specific to IP |
| ISDN | Integrated Services Digital Network |
| LANCE | Local Area Network Controller Ethernet |
| LANE | LAN Emulation |
| LANMGR | IBM LAN Network Manager |
| LAPB | X.25 Link Access Procedure, Balanced |
| LAT | DEC Local Area Transport |
| LEX | LAN extension |
| LINEPROTO | Line Protocol |
| LINK | Data link |
| LLC2 | Logical Link Control type 2 |
| LNMC | LAN network manager |
| LPD | Line printer daemon |
| MAILBOX | ChipCom mailbox support |
| MBRI | Multi-BRI port module |
| MCI | Multiport Communications Interface |
| MK5 | MK5025 serial controller |
| MPA68360 | VIP Multi-channel Port Adapter |
| MROUTE | Multicast route |
| MUESLIX | Mx serial application-specific integrated circuit (ASIC) |
| NIC100 | NIC100 driver |
| NIM | Network interface module |
| OSPF | Open Shortest Path First |
| PA | Port adapter |
| PAD | X.25 packet assembler/disassembler |
| PARSER | Parser |
| PIM | Protocol-independent multicast |
| PPP | Point-to-Point Protocol |
| QA | Queue and accumulator |
| QLLC | Qualified Logical Link Control |
| QUICC | MC68360 Quad Integrated Communications Controller |
| RADIUS | Remote Access Dial-In User Service (RADIUS) facility |
| RADIX | Radix facility |
| RCMD | Remote commands |
| RIP | IP Routing Information Protocol |
| RSP | Route Switch Processor |
| RSRB | Remote source-route bridging |
| S4T68360 | Four port synchronous serial adapter based on the 68360 processor |
| SCHED | Scheduler |
| SDLC | Synchronous Data Link Control |
| SDLLC | SDLC/Logical Link Control type 2 (LLC2) translation |
| SEC | IP security |
| SERVICE_MODULE | Service Module |
| SLIP | Serial Line Internet Protocol |
| SMRP | Simple Multicast Routing Protocol |
| SNAPSHOT | Snapshot dial-on-demand routing |
| SNMP | Simple Network Management Protocol |
| SNMP_MGR | SNMP Proxy |
| SSE | Silicon switching engine |
| STANDBY | Hot Standby Router Protocol (HSRP) |
| STUN | Serial tunneling |
| SUBSYS | Software subsystems |
| SWITCH | Switch interface |
| SYS | Operating system |
| SYSMGT | System management |
| TAC | Terminal Access Controller Protocol Access Control System |
| TBRIDGE | Transparent bridging |
| TCP | Transmission Control Protocol |
| TMQ | Inbound terminal port queuing |
| TN | Telnet |
| TN3270 | TN3270 protocol |
| TR | Token Ring |
| TUN | Tunnel |
| UCODE | Microcode |
| UNIX | UNIX |
| UTIL | Utility |
| VINES | Banyan VINES |
| VIP | Versatile Interface Processor |
| VPN | Virtual Private Dialup Network |
| X25 | X.25 |
| Level | Description |
|---|---|
| 0 - emergency | System unusable |
| 1 - alert | Immediate action needed |
| 2 - critical | Critical condition |
| 3 - error | Error condition |
| 4 - warning | Warning condition |
| 5 - notification | Normal, but significant, condition |
| 6 - informational | Informational message only |
| 7 - debugging | Appears during debugging only |
Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default logs messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the appropriate Cisco IOS configuration guides and command reference publications.
| Representation | Type of Information |
|---|---|
| [atalk_address] | AppleTalk address |
| [atalk_net] | AppleTalk network, either 600 or 600-601 |
| [char] | Single character |
| [chars] | Character string |
| [dec] | Decimal number |
| [enet] | Ethernet address (for example, 0000.FEED.00C0) |
| [hex] | Hexadecimal number |
| [inet] | Internet address (for example, 12.128.2.16) |
| [int] | Integer number |
| [node] | Address or node name |
| [sci_notation] | Scientific notation |
| [t-line] | Terminal line number in octal (or decimal if the decimal-TTY service is enabled) |
| [v-name] | VINES name; or number (hex or decimal) |
This section lists error messages alphabetically by facility and mnemonic.
Explanation We tried to NVGEN a non-existent AAA 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 One of the AAA methods does not seem to have a list associated with it.
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 A AAA method list is neither default nor named.
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 send an accounting record to a server failed.
Recommended Action Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server.
Explanation One of the AAA methods lists has inconsistent settings.
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 Somehow, the periodic timer associated with this ustruct has been lost.
Recommended Action Re-allocate and restart a timer.
Explanation Failed to malloc a timer struct for periodic accounting.
Recommended Action Free up some memory and have the user re-authenticate.
Explanation You have reached the maximum number of possible authentication lists for this method.
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.
Explanation Failed to create the periodic accounting process.
Recommended Action Free up some memory.
Explanation We are trying to free a timer, and the method is PERIODIC, but no timer seems to exist.
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 We are trying to free a timer, but the update method is not PERIODIC, and so no timer should exist.
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 transmitter has been on the channel longer than the time taken to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Explanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
Explanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface.
Recommended Action Clear the interface. If the message recurs, call your technical support representative for assistance.
Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet the system should recover. No action is required.
Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Explanation The interface could not access system resources for a long time. This problem may occur under very heavy loads.
Recommended Action The system should recover. No action is required. If the message recurs, call your technical support representative for assistance.
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Explanation The MII transceiver was disconnected while the MII port was selected.
Recommended Action Connect the transceiver and enter the shutdown and no shutdown commands for the interface in the configuration menu.
Explanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
Explanation While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input 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 detected an error in descriptor ownership.
Recommended Action Try a later version of the software. If the message recurs, call your technical support representative for assistance.
Explanation An illegal condition indicating initialization done has occurred.
Recommended Action Clear the interface. If this message recurs, call your technical support representative for assistance.
Explanation While transmitting a frame, the 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 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 router received an invalid packet during ARA connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Explanation The router resent MNP4 packets the maximum number of times without receiving an acknowledgment.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Explanation This indicates that the router received a disconnect request from the remote Macintosh client.
Recommended Action No action is required.
Explanation This message indicates that the router received MNP4 connection request. MNP4 acknowledgment timer value is also indicated.
Explanation Memory not available for internal MNP4 logging.
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 software error occurred.
Recommended Action Report this error to your technical support representative.
Explanation The router received an oversized MNP4 frame.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Explanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Explanation ARAP connection was terminated without a known cause.
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 repeated resending of MNP4 packets as the Macintosh client failed to acknowledge previously resent packets.
Recommended Action If this error message persists for several ARAP connections, report it to your technical support representative.
Explanation The router is dropping the connection after doing maximum resends.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
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 router received an invalid packet during ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Explanation The router received an invalid packet during ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Explanation An addition to the radix trie could not be completed because of an error.
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 A BGP path could not be deleted because of an error.
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 A deletion from the radix trie could not be completed because of an error.
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 The number of parallel paths exceeds the configured limit.
Recommended Action Increase the number of parallel paths allowed.
Explanation A BRIMUX firmware problem may be present.
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 BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A BRIMUX board hardware problem may be present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A B-channel on the BRIMUX board changed state.
Recommended Action No action is required.
Explanation A BRIMUX board hardware or firmware problem may be present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A port on the BRIMUX board changed state.
Recommended Action No action is required.
Explanation A BRIMUX board changed state.
Recommended Action No action is required.
Explanation Your router is functional. However, there is an interface that the software does not recognize.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The operation might have failed because of a transient network problem.
Recommended Action Retry the operation. If the problem persists, call your technical support representative for assistance.
Explanation The Redundant Power System experienced an AC failure.
Recommended Action One of the AC inputs has failed on the Redundant Power Supply. The "AC Input" LED on the front of the Redundant Power Supply will identify which AC input has failed. Ensure that the AC circuit in your building is operational, verify that the power cord is plugged into the Redundant Power Supply, and ensure that the AC power switch on the Redundant Power Supply is on.
Explanation The Redundant Power System AC is normal.
Recommended Action This is an informational message only. No action is required.
Explanation The detected size of NVRAM is not one of the supported sizes. The NVRAM may be bad.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Redundant Power System experienced a DC failure.
Recommended Action One of the DC outputs has failed on the Redundant Power Supply. The "DC Status" LED on the front of the Redundant Power Supply will identify which DC output has failed. When there is a DC failure, you must replace the Redundant Power Supply.
Explanation The Redundant Power System DC is normal.
Recommended Action This is an informational message only. No action is required.
Explanation The Redundant Power System 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, which has now cleared. This is most likely because of a high ambient temperature where the router is located.
Explanation The Redundant Power System is operating normally.
Recommended Action This is an informational message only. No action is required.
Explanation The Redundant Power System experienced either a fan failure or an over-temperature condition.
Recommended Action Look at the "FAN" and "TEMP" LEDs on the front of the Redundant 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.
Explanation The Redundant Power System THERMAL is now normal.
Recommended Action The Redundant Power Supply previously detected an over-temperature condition, which has now cleared. This is most likely because of a high ambient temperature where the Redundant Power Supply is located. A Redundant Power System thermal failure can also be caused by a fan failure in the Redundant Power Supply.
Explanation A virtual LAN (VLAN) could not be reset with the proper bridging information.
Recommended Action To remedy the problem, configure the VLAN with or without bridging.
Explanation An attempt by the RSP to query the C5IP for the lot it is plugged into has failed.
Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problem persists, contact Cisco for replacement.
Explanation An unsolicited in-band IPC message was received by the router from the Network Management Processor (NMP).
Recommended Action No action is required.
Explanation An attempt by the RSP to query the C5IP for Vlan 0 IP address failed.
Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problems persist, contact Cisco for replacement.
Explanation An attempt by the RSP to query the C5IP for Vlan 0 MAC address failed.
Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problems persist, contact Cisco for replacement.
Explanation A hardware error has occurred on DMA channel 0.
Recommended Action Report this error to your technical support representative.
Explanation A hardware error has occurred on DMA channel 1.
Recommended Action Report this error to your technical support representative.
Explanation An attempt to create a virtual LAN (VLAN) of a media that is not supported has failed.
Recommended Action To remedy the problem, configure the VLAN with a different media type.
Explanation Cisco IOS is receiving bogus messages from the C5IP.
Recommended Action No action is required. If problems persists, contact your Cisco technical support representative.
Explanation The Vlan Router product can configure a maximum of 256 virtual LANs.
Recommended Action To remedy the problem, delete unused VLANs before configuring new ones.
Explanation An in-band IPC message to the Network Management Processor (NMP) from the router to delete a virtual LAN (VLAN) has failed.
Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP via the front-panel LED, and check the state of the NMP. Reset the router.
Explanation An in-band IPC router initialization message to the Network Management Processor (NMP) has failed.
Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP via the front-panel LED, and check the state of the NMP. Reset the router.
Explanation An in-band IPC message to the Network Management Processor (NMP) from the router to create a virtual LAN (VLAN) has failed.
Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP via the front-panel LED, and check the state of the NMP. Reset the router.
Explanation Internal data structure of the virtual LAN (VLAN) is missing.
Recommended Action Contact your Cisco technical support representative.
Explanation An unknown timer event has expired.
Recommended Action No action is required.
Explanation Internal information about the virtual LAN (VLAN) is missing.
Recommended Action Contact your Cisco technical support representative.
Explanation The specified address filter command sent to the specified interface failed with the displayed error code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An interface received a packet with bad VC encapsulation. This indicates either a software or hardware problem.
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 A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The ciscoBus ATM microcode rejected a command sent by the Route Processor (RP). The error code is the status value returned by the command.
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 A 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 A 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 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 Internal data structure is corrupted, which causes the love letter to drop.
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 system received a message from the Token Ring interface but does not recognize the message.
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 system is printing codes related to a previous love note error message.
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 system received an unsolicited message from the Token Ring interface. The system ignored the message and continued normal processing.
Recommended Action 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 A command sent from the system to the Token Ring interface failed to complete successfully.
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 A command sent from the system to the Token Ring interface failed to complete successfully.
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 Token Ring interface failed one of its internal self-tests.
Recommended Action Issue a clear interface command. 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 This command is not supported on this FDDI interface.
Recommended Action No action is required.
Explanation A 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 named interface is not an ATM Cable Interface Processor (ACIP) interface.
Recommended Action An ACIP is required to run the cable data modem (CDM) application. Check than an ACIP is installed in the system.
Explanation No ATM Cable Interface Processor (ACIP) is installed in the system.
Recommended Action An ACIP is required to run the cable data modem (CDM) application. Install ACIP.
Explanation The DTE/X.21 cable does not support loopback.
Recommended Action Use proper cable for loopback testing.
Explanation The software failed to initialize the network module.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation There is not enough memory for a per-channel control block of the CD2430 asynchronous driver.
Recommended Action Ensure that sufficient memory is available in the router. If the message recurs, copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The network module hardware reports that a non-low-speed port module was detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The network module is not compatible with the current platform into which it is being plugged.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP). An inconsistency was detected in an internal data structure related to tracking protocol/interface state, possibly related to enable/disable of the protocol on an interface.
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 error occurred in the application using the compression service adapter (CSA).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The compression service adapter (CSA) driver failed to initialize at the specified point.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The compression service adapter (CSA) driver, in its initialization phase, could not allocate memory for the specified data structure.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The compression service adapter (CSA) driver, in its initialization phase, encountered a communication failure with the CSA in the specified bay.
Recommended Action Consider reseating the specified CSA. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The specified compression service adapter (CSA) is shutting down. It may have been physically removed.
Recommended Action This is an informational message only and occurs in normal operation. No action is required.
Explanation The specified compression service adapter (CSA) has initialized successfully.
Recommended Action This is an informational message only and occurs in normal operation. No action is required.
Explanation One of the interface controller devices on the module did not initialize properly.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An interface controller device did not report the correct protocol control information (PCI) device ID.
Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, call your technical support representative for assistance.
Explanation An invalid operation was detected by the router.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The modem is no longer usable due to a runtime error.
Recommended Action The modem may become operational following a reset of the router. If not, copy the error message exactly as it appears and contact your technical support representative.
Explanation An invalid operation was detected by the router.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The modem signaling module failed initialization
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Modem calls cannot be processed.
Recommended Action Verify that the PRI network module is compatible with the modem network module. If not, copy the error message exactly as it appears and contact your technical support representative.
Explanation The modem may no longer be usable.
Recommended Action The amount of memory available in the router may not be sufficient. Copy the error message exactly as it appears and contact your technical support representative.
Explanation Unexpected message was received from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The CT3 hardware failed. Some components on the board failed to initialize.
Recommended Action Replace the CT3 port adapter.
Explanation CT3 firmware does not update the software watchdog.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An invalid TX accumulator is detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The CT3 hardware failed. Some components on the board failed to initialize.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Failed to download firmware into the CT3 port adapter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This is a general error information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This message indicates a CT3 firmware initialization failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This message indicates a CT3 initialization failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A love letter was not sent to the RSP.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A message was not received from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A message to configure the port was not received from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A message was not sent to CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A port related message was not sent from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This message indicates a failure to detect the HDLC controller on the CT3.
Recommended Action Replace the CT3 port adapter.
Explanation The PLX 9060 was not detected on the CT3.
Recommended Action Replace the CT3 port adapter.
Explanation An error was detected on the communication path between VIP and CT3.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The virtual channel encapsulation is corrupted.
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 CT3 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.
Explanation The restart failed to reset the interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The restart failed to enable the interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The shutdown failed to disable the interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation 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.
Explanation A data-link switching system 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 The Largest frame size configured in the DLSW remote peer definition, is being changed. This is due to the fact that the MTU size configured on the interface, used by DLSW, is less then the configured value of largest frame on DLSW remote peer definition. The largest frame size is being changed to that configured on the interface.
Recommended Action If you wish to use this largest frame size for DLSW, increase the MTU on the interface to a value larger then the configured largest frame size.
Explanation Can't allocate receive buffers since input queue is at its maximum, this indicates data is coming faster than the receiver can handle.
Recommended Action Reduce data goes into this channel and or increase the number of input queue.
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 hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A configuration error occurred.
Recommended Action Configure a Bridge-group on the interface.
Explanation A configuration error occurred.
Recommended Action Configure only the allowed number of Bridge-groups on the ethernet switch port adapter.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A 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 hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Trying to remove PVC DLCI while it is still being used.
Recommended Action Inform Cisco technical support representative
Explanation Output (sub)interface specified in packet is incorrect, broadcast packet is dropped
Recommended Action Inform Cisco technical support representative
Explanation Output interface is NULL, broadcast packet is dropped!
Recommended Action Inform Cisco technical support representative
Explanation The number of halfopen connections or the connection rate had gone back to below the low threshold.
Recommended Action This message is for informational purposes only.
Explanation The high threshold of halfopen connections or connection rate had been exceeded.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Explanation The inspect code detects a JAVA applet entering into secured area and its passage is denied.
Explanation The Inspect code was searching its database for information for a particular inspection session, but this information was not found.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation A audit trail of a session with address/port information and bytes sent counts.
Recommended Action This message is for informational purposed only, and can be used to collect the basic accounting for the inspected sessions.
Explanation The inspect code detects an invalid SMTP command.
Explanation Failed to bring up the processor on the digital modem card.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Digital modem failed to pass power on diagnostics. It will not be used.
Recommended Action If remaining Simm(s) passed diagnostics, remove or replace this problem Simm before continuing. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Modem failed to accept a new command. This may be a transient failure or the modem may remain unusable until a system reset.
Recommended Action You may try to reset the modem by issuing the clear modem slot/port command. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The router does not have enough memory to perform the function
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The router does not have enough I/O memory for buffers
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The router does not have enough I/O memory for buffers
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Unable to create tty line control block for the specified line This may be due to not having enough memory in the router
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation There are no modems installed on the network module.
Recommended Action Make sure the network module contains properly installed MICA-6DM Simm(s).
Explanation Failed to load modem firmware into the Simm.
Recommended Action If firmware successfully loaded into remaining Simm(s), remove or replace this problem Simm before continuing. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Portware running on the Simm was halted due a runtime error. The six modems contained on the Simm have been marked Bad and are no longer usable until the system is reloaded.
Recommended Action Copy the error message exactly as it appears, along with show modem and show modem log output, and report it to your technical support representative.
Explanation Digital Modem Card failed to send or receive PCM data in time to avoid data loss. This may cause the modems to speed shift, retrain, or hangup.
Recommended Action Verify that the DS1 interface(s) share a common clock source. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Network Module is not compatible with the current platform that it is plugged into.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Received unidentified message from modem. This is symptomatic of running with an incompatible version of modem firmware.
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 If either message recurs, call your technical support representative for assistance.
Explanation An 100VG cable or hub is faulty.
Recommended Action If either message recurs, and either the cable or hub appears to be good, repair or replace the router module.
Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the router.
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Explanation An 100VG cable is faulty.
Recommended Action If either message recurs, and either the cable or hub appears to be good, repair or replace the router module.
Explanation Access to the network is denied because of incompatible configuration.
Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.
Explanation An 100VG cable or hub is faulty.
Recommended Action Repair or replace the cable or hub. If the cable or hub appears to be good, repair or replace the VG PA interface module.
Explanation No VG interface detected.
Recommended Action Make sure 100VG PA is properly seated in the slot. Otherwise repair or replace the 100VG PA interface module
Explanation Two VG devices on the same LAN segment have the same MAC address.
Recommended Action Check router configuration to make sure that no duplicate MAC address is configured.
Explanation Unable to login to the hub.
Recommended Action Take action based on the following error messages.
Explanation Configuration of the router module is not compatible to the network
Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration
Explanation The VG controller detects link to the hub is down due to cable, hub or VG controller problem.
Recommended Action Repair or replace the cable or hub. If either the cable or hub appears to be good, repair or replace the VG PA interface module.
Explanation An 100VG cable is faulty.
Recommended Action Repair or replace the cable. If either the cable appears to be good, repair or replace the VG PA interface module.
Explanation Could not find Hardware CAM on the PA module
Recommended Action Repair or replace the 100VG PA interface module.
Explanation Could not find 100VG PCI device
Recommended Action Make sure 100VG PA is properly seated in the slot. Otherwise repair or replace the 100VG PA interface module.
Explanation A software or hardware error occurred. The HP100VG driver detected that the buffer 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.
Explanation One of the interface controller devices on the module did not initialize properly
Recommended Action Power down, reinsert Network Module and reboot. If message recurs, call your technical support representative for assistance.
Explanation The maximum number of commands that can be queued to the Token Ring port has been exceeded. 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 An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Explanation A id_get attempted at interrupt 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 An ID Manager 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 A malloc failure occurred in ID 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.
Explanation An Ethernet interface is malfunctioning.
Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fastswitching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.
Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal ILACC counter that counts the time (in "ticks" of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Explanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Explanation An Ethernet interface detected a hardware problem.
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.
Explanation An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Explanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.
Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
Explanation An entry in the ARP cache have a NULL MAC address
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The system attempted to add a cache entry for an invalid address.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation If IPX access violation logging is enabled, these messages are displayed when an access list logging event has occurred.
Recommended Action Verify that the host system is permitted or denied as defined in the access list.
Explanation The limit of connected IPX networks has been reached, and you cannot configure additional new IPX interfaces.
Recommended Action Do not configure IPX on any additional interfaces. Also, you might want to remove IPX configuration commands from interfaces that are not active.
Explanation The incoming ISDN call is ignored because the Called Party Number does not match the LDN numbers configured in the router.
Recommended Action Correct the LDN in the router to match the Called Party Number delivered in the incoming Setup message.
Explanation The incoming ISDN call is ignored because the EID delivered in the incoming Setup message cannot be matched.
Recommended Action If EID is delivered in the Setup message, use the isdn debugs and show isdn status commands to determine the current EID values. May have to consult the service provider.
Explanation The spid configured in the router has been rejected by the switch.
Recommended Action Determine correct spid, reenter spid and clear the BRI interface.
Explanation This is an informational message. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link.
Recommended Action No action is required.
Explanation This is an informational message. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link.
Recommended Action No action is required.
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 Ethernet cable is not connected.
Recommended Action Check Ethernet cable connection.
Explanation Incoming SDU size did not match the SDU size of the client.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.
Recommended Action If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router must be examined. The most likely cause is that ATM address being registered is not compatible with the parameters - for example, the ATM address prefix - configured in the switch. Correct the configuration.
Explanation BERT is completed for this interface.
Recommended Action This is a notification message only. No action is required.
Explanation The interface entered or exited loopback.
Recommended Action This is a notification message only. No action is required.
Explanation The MBRI network module failed to complete initialization.
Recommended Action Make sure there is sufficient memory available in the router. If you continue to get this message, copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The network module hardware reports that a non-MBRI port module was detected
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The MBRI driver detected an invalid layer1 condition
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This command is not supported on this FDDI interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The integrated modem Network Module hardware may be bad.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The integrated modem override file does not contain valid image(s).
Recommended Action The integrated modem Network Module will be loaded with the default software image(s). Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The integrated modem override file is not compatible with the version of integrated modem hardware.
Recommended Action The integrated modem Network Module will be loaded with the default software image(s). This override file can only be used with specified Network Module hardware versions.
Explanation The integrated modem override file is not compatible with the version of integrated modem hardware.
Recommended Action The integrated modem Network Module will be loaded with the default software image(s). This override file can only be used with specified Network Module hardware versions.
Explanation The integrated modem override file is not compatible with the version of Cisco IOS running on this router.
Recommended Action The integrated modem Network Module will be loaded with the default software image(s). This override file can only be used with specified Cisco IOS versions.
Explanation The integrated modem override file is not compatible with the version of Cisco IOS running on this router.
Recommended Action The integrated modem Network Module will be loaded with the default software image(s). If you wish to use this modem override image file, you must upgrade to the specified Cisco IOS version.
Explanation The integrated modem override file does not contain valid firmware image(s).
Recommended Action The integrated modem Network Module will be loaded with the default software image(s). Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This T1 or E1 network module cannot be used with digital modems.
Recommended Action Copy the error message exactly as it appears, and contact your technical support representative for upgrade information.
Explanation User has used COPY FLASH MODEM to download Microcom modems, but later erased the flash.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The download of the internal firmware to the MPA68360 failed to checksum correctly. This usually indicates a hardware failure of the MPA6836
Recommended Action Perform a power cycle. If the problem persists, the MPA68360 hardware may have a problem.
Explanation Failed to download f/w into the PRI Port Adapter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The PRI port adapter 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 MPA68360 has not responded to a message within a specified time.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The MPA68360 hardware has failed. It could not download its operational microcode.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The MPA68360 hardware failed. A non-MPA68360 device pointed at the software for the MPA68360 serial.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Error on the communication path between DRIVER and MPA68360
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The MPA68360 firmware detected an illegal or unexpected CPU exception or condition. This may be caused by a software error or by a hardware failure.
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 MPA68360 serial interface is not responding to commands used to initialize it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The PRI port adapter failed to respond to a request to disable an interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Mx serial hardware failed. Some interfaces on the board failed to come up.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Mx serial hardware has failed. It could not download its operational microcode.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Mx serial port adaptor driver failed to synchronize with the firmware on the port adaptor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Mx serial port adapter 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 Mx serial hardware failed. A non-Mx serial device pointed at the software for the Mx serial.
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 Mx serial driver detected that the transmit ring is an inconsistent and unrecoverable state.
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 Mx serial interface is not responding to commands used to initialize it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Mx serial port adapter failed to respond to a request to disable an 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 If either message recurs, call your technical support representative for assistance.
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.
Explanation An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if log-adjacency-changes command is configured for the OSPF process.
Recommended Action This message is for information only. No action is required.
Explanation OSPF has problem in locating the LSA; It would lead to memory leak
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation OSPF receive packet originated by itself
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation OSPF found inconsistency between its database and IP routing table
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The interface report its bandwidth as zero
Recommended Action This message is for information only. No action is required.
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, copy the error message exactly as it appears and report it to 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 show version and show cont cbus. Contact your technical support representative.
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 - for example, Revision A5.6 on, and C5.1 on the 3172. Probably 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 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 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 Software failed to initialize/restart a 1T serial card.
Recommended Action Clear the serial interface. If 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 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 A packet greater than the assigned MTU of this serial interface was queued up for transmission.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates an 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.
Explanation A small packet (less than 2 bytes) was queued up for transmission. The interface cannot handle such small packets for transmission.
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.
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.
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 see if it is supported in the version of Cisco IOS 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 along 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
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 To be filled in
Recommended Action To be filled in
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 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, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation Since the configuration has been modified, we can not save the unique accounting IDENT 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 A radius server, which previously was dead, has started responding again.
Recommended Action No action is required.
Explanation A wrong 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 micro reload can correct the error condition as a workaround.
Explanation Memory size mismatch between Master & Slave RSP.
Recommended Action Configure both Master and Slave RSPs to have an equal amount of memory.
Explanation HSA requires a minimum of 24mb of memory.
Recommended Action Upgrade your system to meet minimum memory requirements for HSA.
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 show tech-support.
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 show tech-support.
Explanation The quantity of RSP DRAM is below the recommended amount.
Recommended Action Add DRAM.
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 message indicates that a process_set_wakeup_reasons was attempted from an interrupt handler.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation A valid object identifier must contain at least two subidentifiers. An attempt was made to generate an object identifier whose size was less than two.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An SNMP trap contains some number of MIB objects, and the size of the instance identifier for these objects is restricted. This message indicates that an attempt was made to generate an SNMP trap containing a MIB object whose size exceeded this limit.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation SNMP took too much time processing a request
Recommended Action If feasible, use the debug snmp packet command to determine the contents of the SNMP request that is causing the message. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative.
Explanation An attempt was made to generate an SNMP trap. However, the trap could not be sent, because of the reason given in this message. Most likely, this message means that the SNMP traps process is not running.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Use the show process command to determine whether the SNMP traps process is running. If it is not running, reload the system. If, after reloading, the SNMP traps process is still not running, there may not be enough memory for it to run.
Explanation During the processing of an interrupt, the code attempted to generate an SNMP trap. This is not allowed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes. The network is large, requiring a lot 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 At least one informational or error message was printed by the boot loader.
Recommended Action If the system image was loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A 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.
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation VIP Ethernet-like interface uses an internal MAC address table to filter incoming packets. Once the table is full, additional address entries are rejected. Any incoming packet with destination address not in the table will be ignored.
Recommended Action The address table is consumed by various protocols, like PIM or HSRP. If too many HSRP is configured for one interface, the entry could be exhausted. The suggested solution would be to distribute some of those HSRP entries to other Ethernet interface.
|
|