-
Cisco IOS System Error Messages, Volume 1 of 2
-
About Cisco IOS Software
-
System Error Messages Overview
-
AT through BERT
-
BGP through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBCONN
-
DBUS through DSCREDCLK
-
DSC_REDUNDANCY through ENT_API
-
ENVM through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFS through ISA
-
ISDN through LCCOREDUMP
-
LCFE through MBRI
-
MBUS through MODEM
-
MODEMCALLRECORD through NSP
-
Glossary of Acronyms
-
Table Of Contents
LCFE Messages
The following are Fast Ethernet line card (LC) error messages.
Error Message%LCFE-4-CAM_DONE_TIME : CAM [chars]: wait for DONE exceeded timeout ([dec] ms)
Explanation An LC Fast Ethernet Rx Translator content addressable memory (CAM) DONE bit was not reset to 1 on a write or read within the given timeout period.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCFE-6-CAM_INIT : HW MAC address filter (CAM) init failed: CAM disabled
Explanation The CAM hardware containing the MAC address filter has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCFE-3-FE_RX_MICE : [chars]
Explanation An attempt to load the line card Fast Ethernet Mice FPGA has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCFE-1-INITFAIL : LCFE([dec]/[dec]), initialization timeout failure
Explanation The line card Fast Ethernet hardware initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCFE-6-LINE_STATE : Line state [chars]
Explanation A line state error has been detected or fixed as specified in the message.
Recommended Action Check the cable connections. The local Rx cable must be connected to the remote Tx cable and vice versa.
Error Message%LCFE-4-OP : error: [chars]
Explanation Line card Fast Ethernet driver general operation errors have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCFE-4-RPCMD : [chars] command error: [chars]
Explanation RP command errors involving the line card Fast Ethernet driver have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCFE-6-RX_LOS : [chars] RX Loss of Signal
Explanation An Rx loss-of-signal error has been detected or fixed as specified in the message.
Recommended Action Check the cable connections. The local Rx cable must be connected to the remote Tx cable and vice versa.
Error Message%LCFE-3-RX_TX_TRANS : [chars]
Explanation The line card Fast Ethernet Rx/Tx translator FPGA could not be loaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCFE-6-SYNC_LOSS : [chars]
Explanation A loss-of-synchronization error has been detected, or a previous loss-of-synchronization error has been resolved.
Recommended Action Check the cable connections. The local Rx cable must be connected to the remote Tx cable and vice versa.
LCGE Messages
The following are Gigabit Ethernet line card (LC) error messages.
Error Message%LCGE-6-CAM_ADD : Failed to add address [enet] to CAM
Explanation An entry could not be added to the CAM MAC address filter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-4-CAM_DONE_ITER : CAM [chars]: wait for DONE exceeded [dec] iterations
Explanation The line card Gigabit Ethernet Rx GigaTranslator content addressable memory (CAM) DONE bit was not reset to 1 on a write or read within the number of iterations specified in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-6-CAM_EXCEEDED : [dec] entries to add > [dec] entries available
Explanation An entry could not be added to the CAM MAC address filter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-6-CAM_INIT : CAM MAC address filter init failed: CAM disabled
Explanation The system could not initialize the CAM MAC address filter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-6-CAM_REMOVE : Failed to remove address [enet] from CAM
Explanation An entry could not be removed from the CAM MAC address filter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-6-GBIC_OIR : [chars] [chars] [dec]
Explanation A GBIC OIR event has been detected as specified in the message.
Recommended Action No action is required.
Error Message%LCGE-6-GBIC_READ : Cannot read GBIC in port [dec], perhaps absent or faulty
Explanation The system could not read the GBIC in the specified port.
Recommended Action Ensure that the GBIC is inserted correctly. If it is inserted correctly and the problem persists, replace the GBIC.
Error Message%LCGE-6-GBIC_TX_FAULT : GBIC TX Fault [chars]
Explanation A GBIC Tx fault error was detected or fixed as specified in the message.
Recommended Action Check the GBIC and the cable connections. The local Rx cable must be connected to the remote Tx cable and vice versa.
Error Message%LCGE-1-INITFAIL : LCGE([dec]/[dec]), initialization timeout failure
Explanation The line card Gigabit Ethernet hardware initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-3-INTR : [chars]
Explanation The line card Gigabit Ethernet Rx GigaTranslator FPGA could not be loaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-6-LINE_STATE : Line state [chars]
Explanation A GBIC line state error was detected or fixed as specified in the message.
Recommended Action Check the GBIC and cable connections. The local Rx cable must be connected to the remote Tx cable and vice versa.
Error Message%LCGE-4-OP : error: [chars]
Explanation Line card Gigabit Ethernet driver general operation errors have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-4-RPCMD : [chars] command error: [chars]
Explanation RP command errors involving the line card Fast Ethernet driver have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-6-RX_LOS : [chars] RX Loss of Signal
Explanation A GBIC Rx loss-of-signal error was detected or fixed as specified in the message.
Recommended Action Check the GBIC and cable connections. The local Rx cable must be connected to the remote Tx cable and vice versa.
Error Message%LCGE-3-RX_TRANS : [chars]
Explanation The line card Gigabit Ethernet Rx GigaTranslator FPGA could not be loaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-3-RX_TRANS_PROG : [chars]
Explanation The line card Gigabit Ethernet Rx GigaTranslator FPGA has not been programmed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCGE-6-SYNC_LOSS : [chars]
Explanation A loss-of-synchronization error has been detected, or a previous loss-of-synchronization error has been resolved.
Recommended Action Check the GBIC and cable connections. The local Rx cable must be connected to the remote Tx cable and vice versa.
LCINFO Messages
The following are line card crash information subsystem error messages.
Error Message%LCINFO-3-CRASH : Line card in slot [int] crashed
Explanation The line card in the specified slot has crashed and sent a CRASH_START message to the RP. The RP is waiting for the rest of the crash information from the line card, including stack trace, context, and version, to be sent via the Mbus. This information should be sent a few milliseconds after the CRASH_START message is received. The RP software has not otherwise been notified of the line card crash. The RP software will receive notification of the line card crash after all the crash information has been sent to the RP. In the unlikely event that the subsequent crash information messages are not received by the RP within a reasonable time limit (perhaps 10 seconds), the RP will print a TIMEOUT error message and will report to the rest of the RP software that the line card has crashed.
Recommended Action Report this defect to your Cisco technical support representative. Report as much information about the line card in question as possible, including the output of the show context summary, show context slot n, and show tech-support n commands, as well as the show tech-support command from the RP.
Error Message%LCINFO-3-INVDEV : Invalid line card number in MBUS callback (LC=[int])
Explanation The line card crash information subsystem on the RP was called from the Mbus subsystem with an invalid device identifier. The device in this case should be the slot number of the line card, but the slot number was out of range. This condition indicates a software defect in the system.
Recommended Action Report this defect with as much information about the Mbus subsystem as possible to your Cisco technical support representative. There is no adverse effect to the RP because it ignores the invalid callback and continues. If this problem persists, reboot the router. It is unlikely but possible that this problem is due to defective Mbus hardware somewhere in the system, most likely within the RP Mbus module.
Error Message%LCINFO-3-INVSTATE : Line card crash server in bad state (LC=[int],state=[int])
Explanation The line card crash information subsystem for the specified line card is in an unknown state. This error is caused by a software defect in that subsystem.
Recommended Action Report this defect to your Cisco technical support representative providing as much information as possible about the Mbus subsystem and the line card crash information subsystem.
Error Message%LCINFO-3-NOBUF : Could not malloc line card crash structures on RP (size=[int])
Explanation The RP could not allocate memory for line card crash data structures at the time of startup. This condition is not serious, but the underlying memory shortage at time of startup will probably cause the router to run poorly or prevent the router from starting.
Recommended Action Research the memory shortage problem or add more memory.
Error Message%LCINFO-3-NOBUFLC : Could not malloc line card crash info buffer on RP (LC=[int],bufnum=[int],size=[int])
Explanation The RP could not allocate memory to one or more buffers to hold line card crash information at startup time. This condition is not serious, but the underlying memory shortage at time of startup will probably cause the router to run poorly or prevent the router from starting.
Recommended Action Research the memory shortage problem and, if necessary, add more memory.
Error Message%LCINFO-3-NOPROCESS : Failed creating line card complete process
Explanation When creating the "CRASH COMPLETE" process for the crash information subsystem, the create_process call has failed. This condition should not occur and is probably caused by a software defect or hardware failure. This error should happen only during initialization.
Recommended Action Reboot the system. If the condition persists on subsequent reloads of the system, report the problem to your Cisco technical support representative and reload the system with a different image.
Error Message%LCINFO-3-TIMEOUT : Timeout waiting for crash info from slot [int]
Explanation The "CRASH INFORMATION COMPLETE" timer has expired. When a line card crashes, it sends information to the RP for debugging and analysis. When the "START OF CRASH" message is received, a timer is set for approximately 10 seconds. The line card has 10 seconds to send all the crash information to the RP. This information is not a crash dump—this is a small amount of information that usually includes data such as context and stack trace. The crash information is less than 8K bytes in size. If an "END OF CRASH INFORMATION" message is not received before the timer goes off, the crash information record is closed (containing partial information), this message is displayed, and the rest of the system is notified that the line card has crashed (at which point it is probably reloaded). If the line card sends more crash information after the timer expires and before the system resets the line card, additional "UNXMSG" error messages might be displayed.
Recommended Action No action is required specifically because this message was displayed. Because the line card has crashed, there might be other defects to report. If this message is seen and a line card has not crashed, report this defect to your Cisco technical support representative along with the output of the usual commands, including the show tech-support command on the RP and on the line card that did not crash but was mentioned in this error message.
Error Message%LCINFO-4-TRUNC : Crash record ([int]=[chars]) truncated (expected=[int],actual=[int])
Explanation A line card has crashed and was sending crash information to the RP. The RP received a "CRASH RECORD START" message that indicated the data would be a certain number of bytes in length. Before the indicated number of bytes were received, the RP received another "CRASH RECORD START" message indicating the start of another record. The current record is marked as truncated, the next record is received, and the problem is noted in this error message. This should be noted as a problem, but might be only a symptom of another underlying problem, because this message was triggered by a line card that has crashed.
Recommended Action Report this defect, providing as much information as possible about the Mbus subsystem and the line card crash information subsystem to your Cisco technical support representative.
Error Message%LCINFO-4-UNXMSG : Unexpected crash info msg type ([chars]) in state [chars] (LC=[int])
Explanation The line card crash information subsystem has received a message that is unexpected for the state it is in. The state and message type are given in the error message. This occurrence does not have any adverse effect on the RP because it ignores the message and recovers from this occurrence. The sender of these messages is a line card that is crashing; therefore, the source of the crash on the line card is more significant. If this message occurs without a line card crash, it is due to a stray or errant Mbus message that warrants investigation. This condition could also be caused by a dropped Mbus message.
Recommended Action Find the source of the crash on the line card if one was crashing when the message has occurred. If no line card crashed, report this defect to your Cisco technical support representative, providing as much information as possible about the Mbus subsystem and the line card crash information subsystem. If this message persists, rebooting the router might help eliminate this message.
LCLOG Messages
The following are Internet router line card logger subsystem error messages.
Error Message%LCLOG-3-INVDEV : Invalid line card number in MBUS callback (LC=[int])
Explanation The line card crash info subsystem on the RP was called from the Mbus subsystem with an invalid device identifier. The device in this case should be the slot number of the line card, but the slot number was out of range. This condition indicates a software defect in the system.
Recommended Action Report this defect, providing as much information as possible about the Mbus subsystem to your Cisco technical support representative. There is no adverse effect to the RP because it ignores the defective callback and continues. If the problem is recurring, reboot the router. It is unlikely but possible that the problem is caused by malfunctioning Mbus hardware somewhere in the system, most likely within the RP Mbus module.
Error Message%LCLOG-3-INVSTATE : LC logger in bad state (LC=[int],state=[chars],msg=[chars])
Explanation The line card logger subsystem for the specified line card is not in the state expected for the message it received. This condition is probably caused by a software defect in that subsystem, although it could also be caused by a dropped Mbus message.
Recommended Action Report this defect to your Cisco technical support representative, providing as much information as possible about the Mbus subsystem and the line card logger subsystem.
Error Message%LCLOG-3-MSGGIANT : LC log msg larger than max allowed (LC=[int],length=[int])
Explanation The RP part of the line card logger server has received a log start message that is larger than the maximum size allowed by the log buffer. This condition is probably due to a software defect.
Recommended Action Report this defect to your Cisco technical support representative, providing as much information as possible about the Mbus subsystem and the line card logger subsystem.
Error Message%LCLOG-3-MSGTOOBIG : LC log msg longer than expected (LC=[int],len=[int],exp=[int])
Explanation The RP part of the line card logger server has received more text for a message than was indicated by the start message. This condition is probably due to a software defect.
Recommended Action Report this defect to your Cisco technical support representative, providing as much information as possible about the Mbus subsystem and the line card logger subsystem.
Error Message%LCLOG-3-OVERFLOW : LC log msg longer than msg buffer (LC=[int],len=[int],max=[int])
Explanation The RP part of the line card logger server has received more text for a message than the message log buffer can fit. This condition is probably due to a software defect.
Recommended Action Report this defect to your Cisco technical support representative, providing as much information as possible about the Mbus subsystem and the line card logger subsystem.
LCOC12_CH_DS3 Messages
The following are Internet router OC-12-channelized-to-D3 line card error messages.
Error Message%LCOC12_CH_DS3-1-ALLOCFAIL : OC12 [dec]/[dec][chars] allocation failure
Explanation An OC12-channelized-to-DS3 controller or channel memory allocation failure has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-3-BMAENG : [chars] HDLC, [chars] [chars][chars]. (src=[hex], det1=[hex], det2=[hex])
Explanation HDLC buffer management ASIC engine hardware errors have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-3-BMAPAR : [chars] HDLC, [chars]. BMA_DATA[3:0]=[hex]. (src=[hex], det1=[hex], det2=[hex])
Explanation A parity error has occurred on the HDLC buffer management ASIC engine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-3-CLOCKERR : Controller oc12 [dec]:[dec] clock out of reference.
PLIM interrupt count [dec], interrupt status [hex]Explanation The OC12-CH-DS3 controller clock is out of reference.
Recommended Action Verify the near-end and far-end clock source configuration for the OC12 controller. If, after verifying or correcting the clock configuration, the problem still exists, copy the error message exactly as it appears on the console or in the system log. Issue the show tech 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 command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-3-HDLCENG : [chars] HDLC, [chars]. [chars], port [dec]. (src=[hex], det1=[hex], det2=[hex])
Explanation HDLC engine hardware errors have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-1-INITFAIL : OC12 [dec]/[dec] hardware initialization failure
Explanation An OC12-channelized-to-DS3 line card hardware initialization failure has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, issue the execute-on slot number show controller oc12 all details command. If you cannot determine the nature of the error from the error message text or the execute-on slot number show controller oc12 all details command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-3-NOHWIDB : OC12 [dec]/[dec][chars] hardware IDB is missing
Explanation The OC12-channelized-to-DS3 controller or channel hardware IDB is missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-3-NOSUBBLOCK : OC12 [dec]/[dec][chars] sub-block is missing
Explanation The OC12-channelized-to-DS3 controller or channel hardware IDB associated subblock is missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-3-SRAMPAR : [chars] HDLC, [chars]. [chars]=[hex][chars]. (src=[hex], det1=[hex], det2=[hex])
Explanation A parity error has occurred on the HDLC ASIC SRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCOC12_CH_DS3-4-UNKNOWNPARAM : OC12 [dec]/[dec][chars] parameter value is unknown
Explanation An unknown command parameter was used for the OC12-channelized-to-DS3 controller or channel IPC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LCPLIM Messages
The following are line card physical layer interface module error messages.
Error Message%LCPLIM-2-BADIDB : PLIM interface idb incorrect, [hex]
Explanation A null POS line card instance has been found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the execute-on slot number show controller 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 execute-on slot number show controller command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPLIM-2-BADINTERFACE : Out of range LC interface, [dec] on slot [dec]
Explanation The number of interfaces has exceeded the maximum limit for this line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show version, show gsr, show diags, show interfaces, execute-on slot number show controller, and execute-on slot number show subsys commands 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 version, show gsr, show diags, show interfaces, execute-on slot number show controller, and execute-on slot number show subsys command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPLIM-3-UNDEFCMD : Interface [dec]: unsupported [chars] command =[hex]
Explanation An undefined command has been received for this interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPLIM-2-UNDEFPLIM : Undefined PLIM type [dec] in slot [dec]
Explanation An undefined GSR card type has been found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show version, show gsr, show diags, show interfaces, and execute-on slot number show subsys commands 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 version, show gsr, show diags, show interfaces, or execute-on slot number show subsys command output, contact your Cisco technical support representative and provide the representative with the gathered information.
LCPOS Messages
The following are Packet-over-SONET (POS) line card driver error messages.
Error Message%LCPOS-3-BMAENG : [chars] POS, [chars] [chars][chars]. (src=[hex], det1=[hex], det2=[hex])
Explanation POS buffer management ASIC engine hardware errors have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-BMAPAR : [chars] POS, [chars]. BMA_DATA[3:0]=[hex]. (src=[hex], det1=[hex], det2=[hex])
Explanation A parity error has occurred on the POS buffer management ASIC engine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-1-INITFAIL : LCPOS([dec]/[dec]), initialization timeout failure
Explanation The line card POS ASIC and framer initialization have failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCPOS-3-LINKBADEVT : Unexpected event woke up LC POS link process.
Explanation The line card POS link report process has received an unexpected event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys 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 subsys command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-LINKNOPRC : LCPOS, lcpos_add_process: Unable to create
lcpos_link_report processExplanation The line card POS link report process cannot be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys 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 subsys command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-LINKPROC : LCPOS, lcpos_link_report process: Could not get argument
Explanation The line card POS link report process has stopped working.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys and show memory summary commands 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 subsys or show memory summary command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-POSENG : [chars] POS, [chars]. [chars], port [dec]. (src=[hex], det1=[hex], det2=[hex])
Explanation POS engine hardware errors have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-RXPOSTO : LCPOS([dec]/[dec]), RX POS engine shutdown failed
Explanation The software is trying to shut down the Rx POS engine. The Rx POS engine did not shut down before the software timer expired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If the diagnostics pass, issue the execute-on slot number show controllers pos registers 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 execute-on slot number show controllers pos registers command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-SOP : [chars] SOP. (source=[hex], halt_minor0=[hex])
Explanation Second-generation POS hardware errors have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-SRAMPAR : [chars] POS, [chars]. [chars]=[hex][chars]. (src=[hex], det1=[hex], det2=[hex])
Explanation A parity error has occurred on the POS ASIC SRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform diagnostics on the line card in the specified slot. If the diagnostics pass, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCPOS-3-TXPOSTO : LCPOS([dec]/[dec]), TX POS engine shutdown failed
Explanation The software is trying to shut down the Tx POS engine. The Tx POS engine did not shut down before the software timer expired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the specified slot. If the diagnostics pass, issue the execute-on slot number show controllers pos registers 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 execute-on slot number show controllers pos registers command output, contact your Cisco technical support representative and provide the representative with the gathered information.
LES_FDDI Messages
The following are LAN Emulation Server and FDDI error messages.
Error Message%LES_FDDI-2-ILLEGAL : WARNING: Illegal FDDI Configuration
Explanation The router does not have enough I/O memory to support an FDDI interface. The FDDI interface requires at least 4 MB of I/O memory.
Recommended Action Install the required amount of I/O memory. For maximum performance, Cisco recommends installing 8 MB of I/O memory for a single FDDI NIM, and 16 MB of I/O memory if 2 FDDI NIMs are installed. With 4 MB of I/O memory, the system will create 256 FDDI buffers for one FDDI interface or 384 buffers for two FDDI interfaces. With 8 MB of I/O memory, the system will create 512 FDDI buffers for either one or two FDDI interfaces. With 16 MB of I/O memory, the system will create 512 FDDI buffers for one FDDI interface or 1024 buffers for two FDDI interfaces.
LEX Messages
The following are LAN Extension error messages.
Error Message%LEX-3-NOTSENT : Serial line down, [chars] : [chars] not sent
Explanation The serial line has gone down, and the specified command was not sent to the LAN Extender.
Recommended Action Determine why the serial line went down; for example, if the cable was pulled, or the LAN Extender was powered off. The command will automatically be resent when the serial interface is operational.
Error Message%LEX-3-RCMDNAK : [chars] : [chars] could not be processed by LAN Extender
Explanation The LAN Extender could not process the command from the host router. Possible causes are as follows:
•
The LAN Extender has run out of memory.
•
•
•
Recommended Action If the command was copy tftp lex number or copy flash lex number, ensure that the correct FLEX image file is specified. Only a single copy request can be handled at one time. If the problem was caused by a temporary out-of-memory condition on the LAN Extender, reenter the command.
Error Message%LEX-3-RCMDREJ : [chars] : [chars] could not be processed by LAN Extender
Explanation The LAN Extender did not recognize the code for the specified remote command. This condition might occur if the user is running old LAN Extender software with newer host router software that has support for new LEX remote commands.
Recommended Action Update the LAN Extender software.
Error Message%LEX-3-TIMEOUT : Retry count exceeded for [chars] : [chars]
Explanation The host router resent the given message as many times as specified in the lex retry-count command configuration variable, without receiving an acknowledgment from the LAN Extender. At this point, the host router gives up trying to send this particular remote command message.
Recommended Action Use the LEDs on the LAN Extender to determine if it is operational. Confirm that the lex timeout configuration command is set appropriately for the speed of the link.
LIBT2F Messages
The following are text to fax library error messages.
Error Message%LIBT2F-3-ENGINE_FAILED : The text2fax engine failed
Explanation The text to fax engine has failed. This error was most likely caused by a memory limitation or the passing of illegal data into the text to fax engine. The fax transmission will be aborted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBT2F-3-GETBUFFER_FAILED : Cannot allocate a packet
from shared memoryExplanation The system is running low on packet memory, and the fax cannot be sent correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBT2F-2-NEW_CONTEXT : A new text2fax context could not be created
Explanation An internal error has occurred in the initialization of the text to fax engine. The fax transmission will be aborted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBT2F-3-NULL_BUFFER : A text buffer is NULL
Explanation An internal error has occurred in the text buffer processing. The fax transmission be aborted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LIBTIFF Messages
The following are Tagged Image File Format (TIFF) library error messages.
Error Message%LIBTIFF-3-BAD_DIALPEER : Invalid dial peer tag [dec]
Explanation An invalid Media Mail over IP dial peer tag was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBTIFF-4-COPY_QUALITY : Bad copy quality on tty
[dec]Explanation An error was caused by noisy phone lines or a defective modem.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBTIFF-3-ENGINE_FAILED : The tiff engine failed
Explanation The TIFF engine has failed. This error was most likely caused by a memory limitation or the passing of illegal data into the TIFF engine. The fax transmission will be aborted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBTIFF-3-GETBUFFER_FAILED : Cannot allocate a packet
from shared memoryExplanation The system is running low on packet memory. The fax cannot be sent correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBTIFF-3-INVALID_BUFFER : A tiff buffer is invalid
Explanation An internal error has occurred in the TIFF buffer processing. The fax transmission will be aborted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBTIFF-3-NEW_CONTEXT : A new tiff context could not be created
Explanation An internal error has occurred in the initialization of the TIFF engine. The fax transmission will be aborted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LIBTIFF-3-NULL_BUFFER : A tiff buffer is NULL
Explanation An internal error has occurred in the TIFF buffer processing. The fax transmission will be aborted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LINECARD Messages
The following are Node Route Processor (NRP) line card error messages.
Error Message%LINECARD-3-NRP_BADSTATUS : NRP slot [dec] subslot [dec] invalid Mailbox status area contents or unreachable.
Explanation The mailbox status area contents are invalid or missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_CONFIG : NRP slot [dec] subslot [dec] invalid Mailbox config area contents or unreachable.
Explanation The mailbox configuration area contents are invalid or missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_CRASHING : NRP slot [dec] subslot [dec] crashing.
Explanation An NRP subslot on the line card has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_CRASHREBOOT : NRP slot [dec] subslot [dec] crashed and rebooted.
Explanation An NRP slot on the line card has failed, and the router has rebooted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_NONOP : NRP slot [dec] subslot [dec] non-operational.
Explanation An NRP slot on the line card has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_SECONDARYDEAD : NRP slot [dec] subslot [dec] reports EHSA secondary down.
Explanation The EHSA secondary has gone down.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_SECONDARY_TO_PRIMARY : NRP slot [dec] subslot [dec] EHSA secondary to primary cutover.
Explanation An EHSA secondary-to-primary cutover has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_SECONDARYUP : NRP slot [dec] subslot [dec] reports EHSA secondary up.
Explanation The EHSA secondary has gone up.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LINEPROTO Messages
The following are Line Protocol error messages.
Error Message%LINEPROTO-5-UPDOWN : Line protocol on Interface [chars], changed state to [chars]
Explanation The data link level line protocol has changed state.
Recommended Action No action is required.
LINK Messages
The following are data link error messages.
Error Message%LINK-3-BADENCAP : Interface [chars], Bad encapsulation code ([dec])
Explanation The lower-level software was unable to write a MAC header for a datagram. A configuration error has probably occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-3-BADMACREG : Interface [chars], non-existent MACADDR registry for link [dec]
Explanation An attempt to map a network level address to a MAC level address has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-4-BADQID : Interface [chars], bad output queue ID specified ([dec]). Packet dropped
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-2-BADVCALL : Interface [chars], undefined entry point
Explanation An internal software error has occurred. The high-level system code tried to use an unimplemented entry point with the virtual IDB driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-6-BERTSTATUS : Interface [chars], [chars]
Explanation BERT has been completed for this interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-3-BOGUSENCAP : Interface [chars], bad encapsulation in idb->enctype = [hex]
Explanation A serial interface has been configured with an unknown encapsulation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-5-BOOTP : [chars] address [IP_address], resolved by [IP_address]
Explanation An interface IP address was successfully learned dynamically through BOOTP. The first address specified in the message is the learned IP address. The second IP address specified in the message is the IP address of the BOOTP server that provided the information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-4-BRIDGECONFLICT : Interface [chars], encapsulated BPDU recvd from [enet]
Explanation An FCIT running in nonencapsulating transparent mode has detected an FDDI bridge running in encapsulation mode on the same fiber. This condition indicates an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in standard form.
Recommended Action Upgrade the specified interface to full transparent mode. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-5-CHANGED : Interface [chars], changed state to [chars]
Explanation The interface hardware has changed state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-3-COMPREG : Interface [chars], non-existent (de)compression registry. Packet dropped
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-3-EMPTYPAK : Interface [chars], empty packet dequeued; linktype [dec], queue [dec].
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-4-FDDISTAT : Interface [chars], FDDI state [chars] detected
Explanation A state change has occurred on the FDDI ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-3-IDBLISCRE : Unable to create [chars] interface list
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-3-IDBLISINS : Not able to insert interface [chars] into [chars] list
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-2-INTVULN : In critical region with interrupt level=[dec], intfc=[chars]
Explanation An internal software error has occurred. The high-level system code has attempted to call this routine with interrupts enabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-2-LINEST : No linestate vector for [chars]
Explanation An internal software inconsistency has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-5-LOOPSTATUS : Interface [chars], [chars]
Explanation The interface has entered or exited loopback.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-4-NOMAC : A random default MAC address of [enet] has
been chosen. Ensure that this address is unique, or specify MAC
addresses for commands (such as 'novell routing') that allow the
use of this address as a default.Explanation An addressing inconsistency has occurred.
Recommended Action Ensure that the specified address is unique, or specify MAC addresses for commands such as ipx routing that allow the use of this address as a default.
Error Message%LINK-2-NOSOURCE : Source idb not set
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-5-RARP : [chars] address [IP_address], resolved by [IP_address]
Explanation RARP has resolved an IP address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-0-REENTER : Fatal reentrancy, level=[dec], intfc=[chars]
Explanation An internal software error has occurred. The system code has attempted to access a critical data structure that was already in use.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-5-REMLOOP : Interface [chars], remote loop [chars] [chars]
Explanation The interface has entered or exited a remote loopback.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-5-SLARP : [chars] address [IP_address], resolved by [IP_address]
Explanation The SLARP has resolved an IP address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-4-TOOBIG : Interface [chars], Output packet size of [dec] bytes too big
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-3-TOOSMALL : Interface [chars], Output runt packet of [dec] bytes
Explanation An output packet has been detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.
Recommended Action This is an informational message only. No action is required.
Error Message%LINK-3-UPDOWN : Interface [chars], changed state to [chars]
Explanation The interface hardware has gone either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
LLC Messages
The following are Logical Link Control (LLC), type 2 error messages.
Error Message%LLC-2-UNEXPECT : LLC2: [chars] UNEXPECTED EVENT
Explanation An internal software error has been found. A software component is trying to use LLC2 structures that do not exist.
Recommended Action Record the configuration and any other information that would be useful in recreating the error. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LLIST Messages
The following are linked list facility error messages.
Error Message%LLIST-3-OFFLIST : [chars] from [hex], [hex] not on list
Explanation An internal inconsistency has been detected. An attempt was made to remove the specified item from a list, but the specified item was not on the list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LLIST-3-ONLIST : [chars] to [hex], [hex] on list
Explanation An internal inconsistency has been detected. An attempt was made to add the specified item to a list, but the specified item was already on the list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LNMC Messages
The following are LAN network manager error messages.
Error Message%LNMC-3-BADCLSI : [chars] primitive not valid for lnm [chars] [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSICNF : [chars] Invalid confirm [chars] [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIDATALEN : [chars] Bad data len = [dec] [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIHDRLEN : [chars] Bad header len = [hex] [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIIDTYPE : [chars] Invalid ID type = [hex] [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIIND : [chars] Invalid indication [chars], [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIPRIMTYPE : [chars] Invalid primitive type = [hex] [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIRET : [chars] Invalid ret code ([hex]) [chars], [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSISAP : [chars] Bad clsi SAP id = [hex] [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LPD Messages
The following are line printer daemon (LPD) error messages.
Error Message%LPD-3-MANYLF : Line [t-line], packet has too many newlines to convert
Explanation An internal buffer did not have enough room to add all the necessary carriage returns to a packet of LPD data that was destined for a printer configured with a newline-convert command. This message is unlikely to occur with a file that contains valid data.
Recommended Action Check the file that is being printed to see whether it contains valid, printable data.
LSS Messages
The following are LS Switching error message definition error messages.
Error Message%LSS-4-LSIPC : [chars] [dec]
Explanation The LSIPC has timed out. The microcode on the specified interface may not be responding. A possible cause of this condition is an EPAM not responding.
Recommended Action Check the status of the EPAM.
M32X Messages
The following are M32X Basic Rate Interface (BRI) trunk card error messages.
Error Message%M32X-1-AR_TIMEOUT : M32X controller [dec], channel [hex]: No Reponse from device. Action Request Timeout
Explanation The action request has failed after a retry and has timed out.
Recommended Action No action is required.
Error Message%M32X-1-DWNLDCKSM : M32X: Download checksum error (sent = [hex], received = [hex]
Explanation The download of the internal microcode to the M32X trunk card has failed to checksum correctly. This condition usually indicates a hardware failure of the M32X trunk card.
Recommended Action Perform a power cycle. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-1-DWNLDFL : M32X down load failed.
Explanation The M32X trunk card has failed. The M32X trunk card could not download its operational microcode.
Recommended Action Perform a power cycle. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-1-INITFAIL : M32X slot [dec]: Init Failed at [chars]
Explanation The M32X trunk card has failed to complete its hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-3-MBXREAD : M32X: Stale msg in [chars] - mbx0:[hex] mbx1:[hex] mbx2:[hex]
Explanation The M32X trunk card has not responded to a message within a specified time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-1-NOTCMPLT : M32X download failed to complete.
Explanation The M32X trunk card has failed. It could not download its operational microcode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-3-NOTM32X : Device reported [hex]
Explanation A hardware error has occurred involving the PCI interface for an M32X trunk card.
Recommended Action Either an M32X trunk card has malfunctioned or another PCI device may have been mistaken for an M32X. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-1-NOTREADY : Not ready for download.
Explanation The M32X trunk card did not respond when requested to download its operational microcode.
Recommended Action Perform a power cycle. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-3-PANIC : M32X: Exception [dec], trace [dec]
Explanation A software or hardware error has occurred in the M32X trunk card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-5-REMLOOP : M32X controller [dec], channel [dec]: remote loopback [chars], [chars]
Explanation The interface has entered or exited a remote loopback.
Recommended Action No action is required.
Error Message%M32X-1-STARTFAIL : [chars]: Channel enable failed
Explanation A software or hardware error has occurred. The M32X trunk card is not responding to commands that are used to initialize it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-1-STOPFAIL : [chars]: Channel disable failed
Explanation A software or hardware error has occurred. The M32X trunk card has failed to respond to a request to disable an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%M32X-3-TOOSMALL : M32X: [chars] - packet was less than two bytes
Explanation An output packet had been detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
MAILBOX Messages
The following are ChipCom mailbox support error messages.
Note
Error Message%MAILBOX-3-BADCHKSUM : Checksum failed. Expected = [hex], calculated = [hex]. Ignoring PDU.
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MAILBOX-3-BADECHO : Echo-response did not match echo-request!
Explanation The data received from an ECHO_RESPONSE PDU did not match the original data provided in the ECHO_REQUEST. Usually this message is seen during initialization and indicates a catastrophic failure of the mailbox interface. See the MAILBOX-3-INITFAIL error message for more information.
Recommended Action Verify the router module installation. Ensure that the software revision on the management module and the router module carrier card is up to date. If this message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MAILBOX-3-BADPDU : PDU of type [chars] received. Invalid or unsupported. Ignoring.
Explanation The PDU that the mailbox received was valid, but the type is not supported in the current software implementation and will be ignored.
Recommended Action This is an informational message only. No action is required.
Error Message%MAILBOX-3-INITFAIL : Mailbox initialization failure. [chars] Mailbox offline.
Explanation A catastrophic failure involving the initialization of the administrative mailbox has occurred. The mailbox will be taken offline and remain in that state until a router module reset or a system reload occurs. At that time, initialization will again be attempted. Note that the functionality of the router (its ability to receive and forward packets) is not affected by this error.
Recommended Action Verify the router module installation. Ensure that the software revision on the management module and the router module carrier card is up to date. If this message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MAILBOX-6-INITOK : Mailbox initialization successful.
Explanation After a router reloads, this message is generated to indicate that the mailbox was successfully initialized.
Recommended Action This is an informational message only. No action is required.
Error Message%MAILBOX-7-MBOXDEBUG : [chars]
Explanation This message header is paired with general debugging messages used to provide information about the functionality of the mailbox. To enable mailbox debugging, enter the debug mailbox command.
Recommended Action This is an advisory message only. No action is required.
Error Message%MAILBOX-3-NOECHO : Echo-request timed out. No response received. Mailbox offline.
Explanation An ECHO_RESPONSE was not received within the allotted time after the generation of an ECHO_REQUEST. This failure occurs only during mailbox initialization and indicates a problem between the communication path of the router module and its carrier card.
Recommended Action Verify the router module installation. Ensure that the software revision on the management module and the router module carrier card is up to date. If this message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MAILBOX-3-OFFLINE : [chars] mailbox is offline. Interrupt ignored.
Explanation This message is generated when an attempt has been made by the management module to communicate with an offline mailbox. An error exists between the perceived state of the mailbox from the router side and the perceived state of the mailbox from the management module side.
Recommended Action Issue a system-wide reset on the management module. If this message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MAILBOX-7-ONLINE : [chars] mailbox coming online.
Explanation This message is generated only when mailbox debugging is enabled. It provides information about the state of each incoming or outgoing mailbox.
Recommended Action This is an advisory message only. No action is required.
Error Message%MAILBOX-7-READ : Reading [hex] from carrier.
Explanation This message is generated only when mailbox debugging is enabled. It provides very low-level information about the incoming mailbox data stream.
Recommended Action This is an advisory message only. No action is required.
Error Message%MAILBOX-3-TIMEOUT : Intra-PDU timeout occurred on [chars] mailbox data.
Explanation A timeout has occurred while the characters of a PDU were being sent or received. The entire PDU will be ignored.
Recommended Action This is an informational message only. No action is required.
Error Message%MAILBOX-7-WRITE : Writing [hex] to carrier.
Explanation This message is generated only when mailbox debugging is enabled. It provides very low-level information about the outgoing mailbox data stream.
Recommended Action This is an advisory message only. No action is required.
MBRI Messages
The following are error messages relating to multi-BRI (MBRI) port modules.
Error Message%MBRI-1-CHANINITFAIL : [chars] [chars] failed
Explanation The MBRI network module has failed to complete its initialization.
Recommended Action Ensure that there is sufficient memory available in the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MBRI-1-INITFAIL : Port Adapter in bay [dec], shutting down PA
Explanation The MBRI network module has failed to complete its initialization.
Recommended Action Ensure that there is sufficient memory available in the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MBRI-3-NOTMBRI : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The network module hardware has reported that a non-MBRI port module was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MBRI-1-TIMERPOOL_EMPTY : [chars] could not get timer element
Explanation The requested operation could not be accomplished because the global pool of timer elements was empty. This error may have been caused by a transient system condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MBRI-3-UNKNOWN_STATE : [chars] layer1 state is [dec]
Explanation The MBRI driver has detected an invalid Layer 1 condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
