LC through MBUS

LC Messages
LCB Messages
LCCEF Messages
LCCOREDUMP Messages
LCFE Messages
LCGE Messages
LCINFO Messages
LCLOG Messages
LCOC12_CH_DS3 Messages
LCPLIM Messages
LCPOS Messages
LES_FDDI Messages
LEX Messages
LIBT2F Messages
LIBTIFF Messages
LINECARD Messages
LINEPROTO Messages
LINK Messages
LLIST Messages
LNMC Messages
LPD Messages
LSS Messages
M32X Messages
MAILBOX Messages
MBRI Messages
MBUS Messages

LC Messages

The following are line card (LC ) error messages.

Error Message

%LC-3-BMA48ERR: [chars] BMA error: stat_reg [hex] adr [hex] data [hex] qm [hex] plim [hex] l3 [hex] ms [hex] sdram [hex]

Explanation An error has occurred in the buffer management ASIC (BMA).

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%LC-3-BMA48ERRS: [chars] BMA48 [chars] error [hex]

Explanation An error has occurred in the buffer management ASIC (BMA).

Error Message

%LC-3-BMA48FIM: [chars] BMA48 [chars] error fim_cf_status [hex]; fim_df0: adr [hex] data [hex]; fim_df1: adr [hex] data [hex]; fim_df2: adr [hex] data [hex]; fim_df3: adr [hex] data [hex]

Explanation An error has occurred in the buffer management ASIC (BMA).

Error Message

%LC-3-BMABUFF: [chars] BMA has [int] buffers in queue [int] when maximum of [int] are allowed

Explanation The number of buffers in one of the buffer management ASIC (BMA) queues has overflowed.

Error Message

%LC-3-BMACMDFTCH: Problem in BMA command fetching, status=[dec] [chars] BMA

Explanation The buffer management ASIC (BMA) has encountered problems while trying to fetch the given command. If this message appears more than once, it may indicate a hardware problem. The Gigabit Route Processor (GRP) should recognize that communication was lost with the line card and reload it.

Error Message

%LC-3-BMACMDLOST: [chars] BMA has lost a command

Explanation The specified buffer management ASIC (BMA) has lost a command. If this message appears more than once, it may indicate a hardware problem. The Gigabit Route Processor (GRP) should recognize that communication was lost with the line card and reload it.

Error Message

%LC-3-BMACMDRPLY: Problem in BMA reply to command type [dec] [chars] BMA sequence no=[dec]

Explanation There was a problem in the reply to the given buffer management ASIC (BMA) command. If this message appears more than once, it may indicate a hardware problem. The Gigabit Route Processor (GRP) should recognize that communication was lost with the line card and reload it.

Error Message

%LC-3-BMAERR: [chars] BMA error: msstat [hex] dma0 [hex] dma1 [hex] dma2 [hex] qm [hex] plim [hex] fia [hex] l3 [hex] ms [hex] sdram [hex]

Explanation There is an error in the buffer management ASIC (BMA).

Error Message

%LC-3-BMAERRS: [chars] BMA [chars] error [hex]

Explanation There is an error in the buffer management ASIC (BMA).

Error Message

%LC-3-BMAERRSS: [chars] BMA [chars] error [hex] [chars] [hex]

Explanation There is an error in the buffer management ASIC (BMA).

Error Message

%LC-3-BMASDRAM_BADCAS_LATENCY: [chars] DIMMs do not support CAS latency needed. got 0x[hex]

Explanation The synchronous DRAM (SDRAM) DIMM modules that are installed in the BMA SDRAM DIMM sockets do not support the channel associated signaling (CAS) latency required. CAS latency is specified in the DIMM EEPROM as a number. When converted to a binary number, each bit corresponds to one CAS latency. Bit 2 must be set to 1, indicating that a CAS latency of 3 is supported.

Error Message

%LC-3-BMASDRAM_BADSIZE: [chars] DIMMs are of unsupported size. Read this: rows [dec], cols [dec], DIMM banks [dec], SDRAM Device banks [dec]

Explanation The synchronous DRAM (SDRAM) DIMM modules that are installed in the BMA SDRAM DIMM sockets are of an unsupported size.

Error Message

%LC-3-BMASDRAM_BADWIDTH: [chars] DIMMs have unsupported data width, expected [dec], got [dec]

Explanation The synchronous DRAM (SDRAM) DIMM modules that are installed in the BMA SDRAM DIMM sockets have unsupported data width.

Error Message

%LC-3-BMASDRAM_NOTMATCH: [chars] SDRAM DIMMs do not match

Explanation The synchronous DRAM (SDRAM) DIMM modules that are installed in "to Fabric" or "from Fabric" buffer management ASIC (BMA) DIMM0 and DIMM1 sockets do not match. The DIMMs on one side (to Fabric) could be different from the DIMMs on the other side (from Fabric), but the two DIMMs on the same side have to be identical. Also, all four DIMMs must be mounted and making proper contact.

Error Message

%LC-3-BMAUCODE_GET: [chars] BMA: feature [chars], line card type [chars], could not get [chars] BMA microcode

Explanation When the bma microcode download command was issued, the given buffer management ASIC (BMA) microcode bundled in the image was not received.

Error Message

%LC-3-BMAUCODE_LCTYPE: [chars] BMA: feature [chars], specified linecard type(s) ([hex]) != current ([hex])

Explanation When the bma microcode download command was issued, there was a mismatch between what was specified in the buffer management ASIC (BMA) microcode file and the current type of line card.

Error Message

%LC-3-BMAUCODE_NULL: Null downloaded BMA microcode

Explanation When the bma microcode download command was issued, the specified buffer management ASIC (BMA) microcode bundled in the image was not retrieved because it is null.

Error Message

%LC-3-CARVE_BUFHDRS: [chars] BMA: out of SDRAM buffer headers

Explanation The system ran out of available synchronous DRAM (SDRAM) buffer headers while attempting to carve buffers. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-3-CARVE_BUFSIZE: [chars] BMA: illegal specified/real SDRAM buffer size(s) = ([unsigned long],[unsigned long]). Range=([dec],[dec])

Explanation The calculated synchronous DRAM (SDRAM) buffer size (in bytes and including the header and data portions) is not within the given range. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-3-CARVE_EXBUFS: [chars] BMA: [int] SDRAM buffers > max ([int])

Explanation The maximum number of synchronous DRAM (SDRAM) buffer headers has been exceeded. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-3-CARVE_EXFREEQS: [chars] BMA: [int] free queues > max ([int])

Explanation The number of free queues allowed for synchronous DRAM (SDRAM) buffer carving has been exceeded. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-3-CARVE_EXPCT: [chars] BMA: [int] sum SDRAM buffer percentages > 100

Explanation The sum of percentages per synchronous DRAM (SDRAM) buffer size has exceeded 100. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-3-CARVE_EXSDRAM: [chars] BMA: used SDRAM ([unsigned long long] bytes) > available for carve ([unsigned long] bytes)

Explanation The calculated sum of synchronous DRAM (SDRAM) to be carved is larger than the available SDRAM for carving. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-4-CARVE_JVMASK: [chars] BMA: suspect return value [dec] on quiesce-for-carve

Explanation The buffer management ASIC (BMA) quiesce-for-carve algorithm retrieved an invalid jump vector mask return value. This problem could indicate an error in the quiesce.

Error Message

%LC-3-CARVE_NOFREEQS: [chars] BMA: no more free queues

Explanation There are no more available free queues that can be used for the synchronous DRAM (SDRAM) buffer carve. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-3-CARVE_PARMS: [chars] BMA: >= 1 SDRAM bufmem parameters == 0

Explanation An internal parameter error has occurred with one or more of the following synchronous DRAM (SDRAM) buffer memory parameters: maximum buffer header count or SDRAM sizes (total, not available for carve, and available for carve).

Error Message

%LC-3-CARVE_QELEM: [chars] BMA: [int] Queue Manager SRAM elements > max ([int])

Explanation The system has run out of Queue Manager elements, which are used for synchronous DRAM (SDRAM) buffer carving. This problem may have been caused by an SDRAM buffer carve failure.

Error Message

%LC-3-CARVE_QMREAD: BMA address [hex]: Queue Manager SRAM [hex], read error(s)

Explanation An error has occurred during the Queue Manager SRAM initialization. Reading one or more zeroed Queue Manager SRAM locations gave a nonzero result. Errors are possible in the head, tail, length, length threshold, buffer address, next queue element, or scratch RAM locations.

Error Message

%LC-4-CARVE_TIME: [chars] BMA: quiesce-for-carve exceeded timeout ([dec] ms) in [chars] loop, [dec] times

Explanation The buffer management ASIC (BMA) quiesce-for-carve algorithm waits an allotted amount of time for line card queues to flush. One or more waits have exceeded this allotted time. These queues are specific to the ASICs of the line card. This error message might not actually indicate an error; the allotted time might not be sufficient and therefore might need to be increased.

Error Message

%LC-3-DOWNREV: BMA is an old version.

Explanation The system software has detected an old version of the buffer management ASIC (BMA).

Recommended Action Call your Cisco technical support for an upgraded version of the BMA.

Error Message

%LC-3-IICDEV_NOTACKADDR: IIC Device [dec] failed to ack address

Explanation The BMA synchronous DRAM (SDRAM) DIMM has failed to acknowledge an address. This message indicates an SDRAM IIC bus protocol error.

Error Message

%LC-3-IICDEV_NOTACKREAD: IIC Device [dec] failed to ack read command

Explanation The BMA synchronous DRAM (SDRAM) DIMM has failed to acknowledge the read command. This error indicates an SDRAM IIC bus protocol error.

Error Message

%LC-3-IICDEV_NOTRESPOND: IIC Device [dec] does not respond, perhaps absent

Explanation The BMA synchronous DRAM (SDRAM) DIMM does not respond and perhaps is missing.

Error Message

%LC-3-INIT_CARD_TYPE: Unknown card type (0x[hex])

Explanation A card either was manufactured improperly, has failed, or is newer than the software.

Recommended Action Replace the card or upgrade the software.

Error Message

%LC-3-INIT_MEM: Memory failure, addr [hex], read [hex][hex], not [hex][hex]

Explanation The initialization of the memory address has failed.

Error Message

%LC-3-INIT_READ: Error reading memory at 0x[hex]

Explanation The specified memory location could not be read.

Error Message

%LC-3-INIT_RESET: Failed to take line card out of reset

Explanation The initialization of the line card I/O registers has failed.

Error Message

%LC-3-INIT_ZERO: No bytes to write to location 0x[hex]

Explanation No bytes of data were written to the specified location.

Error Message

%LC-3-INVQ: Invalid local output queue: [hex] [hex] [hex] [hex] [hex] [hex]

Explanation The specified packet was routed to an invalid queue. The data shown in this message is the packet header.

Error Message

%LC-3-L3FEERR: L3FE error: rxbma [hex] addr [hex] txbma [hex] addr [hex] dram [hex] addr [hex] io [hex] addr [hex]

Explanation An error has occurred in L3FE ASIC of the line card.

Error Message

%LC-3-L3FEERRS: L3FE [chars] error [hex] address [hex]

Explanation An error has occurred in L3FE ASIC of the line card.

Error Message

%LC-3-LC_CODE_DLD_ALLOC: Failed buffer allocation for code download

Explanation The system could not allocate a data buffer to contain the contents of the given line card file that was downloaded. There may be insufficient DRAM.

Error Message

%LC-3-LC_CODE_DLD_CHKSUM: code download IPC data checksum error

Explanation The glc code download command has failed the checksum verification.

Error Message

%LC-3-LC_CODE_PROG: no downloaded code to program

Explanation The glc code download command has failed. There is no downloaded code to program.

Error Message

%LC-3-LC_FLASH_PROG_ALLOC: Can't allocate [chars]

Explanation When the glc flash program command was entered the watch queue, buffer, or process creation failed.

Error Message

%LC-3-LOOKUP_COMPL: Hardware assist lookup error 0x[hex] in memory encountered. hw 0x[hex] sw 0x[hex] ip 0x[hex] root 0x[hex] first 0x[hex] second 0x[hex] third 0x[hex] leaf 0x[hex]

Explanation An error has occurred in L3FE ASIC of the line card.

Error Message

%LC-3-LOOKUP_RANGE: Hardware assist lookup error 0x[hex] in memory encountered. hw 0x[hex] sw 0x[hex] ip 0x[hex] root 0x[hex] first 0x[hex] second 0x[hex] third 0x[hex] leaf 0x[hex]

Explanation An error has occurred in L3FE ASIC of the line card.

Error Message

%LC-3-MACSTR: Adj/midb ([chars]) incorrect macstring: length=[dec], macstr word=0x[hex]

Explanation The line card Cisco express forwarding (CEF) or MDS has received an adjacency or midb that contains an invalid MAC rewrite string. Packets forwarded to that adjacency or midb will be dropped.

Error Message

%LC-3-MLLC: Channel or Port [int]: [chars] malloc failure

Explanation A memory allocation failure has occurred on the line card.

Error Message

%LC-3-OUTINFO: Adj/midb([chars]): incorrect output_info=0x[hex] maclen=[dec]

Explanation The line card Cisco express forwarding (CEF) or MDS has received an adjacency or midb that contains an invalid OUTPU_INFO field. Packets forwarded to that adjacency or midb will be dropped.

Error Message

%LC-3-PARITYERRTTM48: Parity error in memory encountered

Explanation A one-bit memory corruption has occurred.

Error Message

%LC-3-SELECTOR: [dec]: unknown BMA selector value

Explanation An unknown buffer management ASIC (BMA) selector value has been encountered.

Error Message

%LC-1-TESTALERT: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

Error Message

%LC-2-TESTCRIT: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

Error Message

%LC-7-TESTDEBUG: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

Error Message

%LC-3-TESTERR: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

Error Message

%LC-0-TESTEMERG: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

Error Message

%LC-6-TESTINFO: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

Error Message

%LC-5-TESTNOTICE: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

Error Message

%LC-4-TESTWARNING: [chars]

Explanation This is a test message for a software test.

Recommended Action Stop issuing the test gsr logger command.

LCB Messages

The following are Line Control Block (LCB) event process error messages.

Error Message

%LCB-3-LOCKFAILURE: Multiple LCB event processes scheduled

Explanation The Line Control Block (LCB) event process has failed to lock the semaphore that is used to prevent multiple LCB processes from running. This message indicates that multiple LCB processes have been scheduled to run when they should not have been allowed to run at the same time.

Recommended Action Try executing the command again after a few minutes. If the problem persists call your Cisco technical support representative.

Error Message

%LCB-3-QUEUEFAILURE: LCB process unable to create event queue

Explanation The system could not create a Line Control Block (LCB) event queue, and the LCB process has quit. The operating system was unable to allocate adequate RAM space for the queue.

Recommended Action Try executing the command again after a few minutes. If the problem persists, it indicates a lack of RAM space. Most likely, the router image requires more system memory (RAM) than it currently contains.

LCCEF Messages

The following are ATM Cisco express forwarding (CEF) adjacency error messages.

Error Message

%LCCEF-3-MACSTR: adjacency ([chars]) has incorrect high word (0x[hex]) in its mac string

Explanation The Cisco express forwarding (CEF) line card has received an adjacency with an incorrect MAC rewrite string. Packets forwarded to that adjacency will be dropped.

Error Message

%LCCEF-3-OUTINFO: adjacency ([chars]) has incorrect output_info (0x[hex]) field

Explanation The Cisco express forwarding (CEF) line card has received an adjacency with an incorrect OUTPUT_INFO field. Packets forwarded to that adjacency will be dropped.

LCCOREDUMP Messages

The following are line card core dump subsystems error messages.

Error Message

%LCCOREDUMP-3-BADCLOSE: Can't close slave core socket for slot [dec]

Explanation The system has just finished dumping a core file from a line card. The system tried and failed to close the core file on the remote system.

Recommended Action Verify the network connections and user privileges.

Error Message

%LCCOREDUMP-3-BADOPEN: Can't open slave core socket for slot [dec]

Explanation The system wants to dump a core file to a remote sytem, but it is unable to open the remote file.

Recommended Action Ensure that the remote system is accessible and the protocol is set up correctly.

Error Message

%LCCOREDUMP-3-BADWRITE: Can't write [chars] to slave core socket for slot [dec]

Explanation The system is trying to write a core dump file to a remote sytem. The file was opened, and an error has occurred during a write to the file.

Recommended Action Verify that the network is functioning and that there is available disk space.

Error Message

%LCCOREDUMP-2-EOM: Cannot allocation memory for [chars]

Explanation The system cannot allocate memory for the core dump subsystem.

Recommended Action Add more memory.

Error Message

%LCCOREDUMP-3-ILLNVGEN: Illegal call to bflc_cfg_coredump_nvgen

Explanation The NVGEN routine was called, but the NVGEN was not set.

Recommended Action Gather information about the processes running on this Gigabit Switch Router (GSR), including the traceback, and contact your Cisco technical support representative.

Error Message

%LCCOREDUMP-3-ILLPAK: Coredump packet received from slot [dec] (not in dump state) 0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex]0x[hex] 0x[hex] 0x[hex] 0x[hex] 0x[hex]

Explanation The Route Processor (RP) has received a core dump packet from a line card that should not be dumping core.

Recommended Action Gather information about the state of the line cards and call your Cisco technical support representative.

Error Message

%LCCOREDUMP-3-ILLTD: Testdump only valid on line cards (not allowed on RPs)

Explanation You cannot run a line card core dump test for a Route Processor (RP).

Recommended Action Do not try to run a line card core dump test for an RP.

Error Message

%LCCOREDUMP-6-LERP: Cannot configure linecard exceptions for [chars] RP

Explanation The exception line card commands can be used only to configure exceptions on a line card. You cannot use an exception line card command to configure RP core dumps.

Recommended Action Use the exception command without a line card specified to configure RP core dumps.

Error Message

%LCCOREDUMP-3-NOMCP: Cannot malloc memory for mbus core dump message to slot [dec]

Explanation The system is trying to write a core dump file to a remote sytem. It could not allocate memory to create the message that starts the core dump process.

Recommended Action Add memory.

Error Message

%LCCOREDUMP-4-NOMDD: [chars] core dump for slot [dec] (Cannot modify during dump)

Explanation The system is currently dumping a core file for this line card. You cannot modify the core dump configuration during a dump.

Recommended Action Wait for the core dump to finish.

Error Message

%LCCOREDUMP-3-NOPAK: No packet on queue (0x[hex] [dec])

Explanation The Route Processor (RP) has received a core dump packet from a line card that should not be dumping core.

Recommended Action Gather information about the state of the line cards and call your Cisco technical representative.

Error Message

%LCCOREDUMP-3-NOPROC: Unable to create data handler process

Explanation The system is attempting to write a core dump file to a remote system, but it is unable to start a process to dump the file.

Recommended Action Gather information about the number of processes running, including the amount of memory in the system, and call your Cisco technical representative.

Error Message

%LCCOREDUMP-3-NOQUEUE: Cannot create queue to receive dump packets for slot [dec]

Explanation The system is trying to write a core dump file to a remote sytem. It could not create a queue to hold the dump data coming from the line cards.

Recommended Action Add memory.

Error Message

%LCCOREDUMP-4-TIMEOUT: [chars] (0x[hex] [dec])

Explanation The system is trying to write a core dump file, but the Route Processor (RP) timed out while it was waiting for the data from the line card.

Recommended Action Gather information about the line card and call your Cisco technical representative.

LCFE Messages

The following are Fast Ethernet line card (LC) driver 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.

Error Message

%LCFE-6-CAM_INIT: HW MAC address filter (CAM) init failed: CAM disabled

Explanation The content addressable memory (CAM) hardware containing the MAC address filter has failed.

Error Message

%LCFE-3-FE_RX_MICE: NULL

Explanation An attempt to load the line card Fast Ethernet Mice field-programmable gate array (FPGA) has failed.

Error Message

%LCFE-1-INITFAIL: LCFE([dec]/[dec]), initialization timeout failure

Explanation The line card Fast Ethernet hardware initialization has failed.

Error Message

%LCFE-6-LINE_STATE: Line state [chars]

Explanation A line state error was detected or fixed as specified in the message.

Recommended Action Check and cable connections. Local RX cable must be connected to remote TX cable and vice versa.

Error Message

%LCFE-4-OP: error: [chars]

Explanation Some general operation errors involving the Line card Fast Ethernet driver have occurred.

Error Message

%LCFE-4-RPCMD: [chars] command error: [chars]

Explanation A Route Processor (RP) command error that involves the line card Fast Ethernet driver has occurred.

Error Message

%LCFE-6-RX_LOS: [chars] RX Loss of Signal

Explanation An RX loss-of-signal error was detected or fixed as specified in the message.

Recommended Action Check cable connections. Local RX cable must be connected to remote TX cable and vice versa.

Error Message

%LCFE-3-RX_TX_TRANS: NULL

Explanation The line card Fast Ethernet RX/TX Translator field-programmable gate array (FPGA) could not be loaded.

Error Message

%LCFE-6-SYNC_LOSS: [chars]

Explanation A loss-of-synchronization error was detected or is gone as specified in the message.

Recommended Action Check cable connections. Local RX cable must be connected to remote TX cable and vice versa.

LCGE Messages

The following are Gigabit Ethernet line card (LC) driver error messages.

Error Message

%LCGE-6-CAM_ADD: Failed to add address [sci_notation] to CAM

Explanation An entry could not be added to the content addressable memory (CAM) MAC address filter.

Error Message

%LCGE-4-CAM_DONE_ITER: CAM [chars]: wait for DONE exceeded [dec] iterations

Explanation The LC Gigabit Ethernet RX GigaTranslator content addressable memory (CAM) DONE bit was not reset to 1 on a write or read within the given number of iterations.

Error Message

%LCGE-6-CAM_EXCEEDED: [dec] entries to add > [dec] entries available

Explanation An entry could not be added to the content addressable memory (CAM) MAC address filter.

Error Message

%LCGE-6-CAM_INIT: CAM MAC address filter init failed: CAM disabled

Explanation The system could not initialize the content addressable memory (CAM) MAC address filter.

Error Message

%LCGE-6-CAM_REMOVE: Failed to remove address [sci_notation] from CAM

Explanation An entry could not be removed from the content addressable memory (CAM) MAC address filter.

Error Message

%LCGE-6-GBIC_OIR: [chars] [chars] [dec]

Explanation A Gigabit Interface Converter (GBIC) online insertion and removal (OIR) event was 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 Gigabit Interface Converter (GBIC) in the specified port.

Recommended Action Ensure that the GBIC is inserted. If the GBIC is inserted and the problem persists, replace it.

Error Message

%LCGE-6-GBIC_TX_FAULT: GBIC TX Fault [chars]

Explanation A Gigabit Interface Converter (GBIC) TXFault error was detected and resolved as specified in the message.

Recommended Action Inspect the GBIC and cable connections. The local and remote RX cables must be connected to each other.

Error Message

%LCGE-1-INITFAIL: LCGE([dec]/[dec]), initialization timeout failure

Explanation The Gigabit Ethernet line card initialization has failed.

Error Message

%LCGE-3-INTR: [chars]

Explanation The Gigabit Ethernet line card RX GigaTranslator field-programmable gate array (FPGA) could not be loaded.

Error Message

%LCGE-6-LINE_STATE: Line state [chars]

Explanation A Gigabit Interface Converter (GBIC) line state error was detected or resolved as specified in the message.

Recommended Action Inspect the GBIC and cable connections. The local and remote RX cables must be connected to each other.

Error Message

%LCGE-4-OP: error: [chars]

Explanation Gigabit Ethernet line card driver general operation errors have occurred.

Error Message

%LCGE-6-RX_LOS: [chars] RX Loss of Signal

Explanation A Gigabit Interface Converter (GBIC) RX loss-of-signal error has been detected and resolved as specified in the message.

Recommended Action Inspect the GBIC and cable connections. The local and remote RX cables must be connected to each other.

Error Message

%LCGE-3-RX_TRANS: NULL

Explanation The Gigabit Ethernet line card RX GigaTranslator field-programmable gate array (FPGA) could not be loaded.

Error Message

%LCGE-3-RX_TRANS_PROG: NULL

Explanation The Gigabit Ethernet line card RX GigaTranslator field-programmable gate array (FPGA) has not been programmed.

Error Message

%LCGE-6-SYNC_LOSS: [chars]

Explanation A Gigabit Interface Converter (GBIC) loss-of-synchronization error has been detected and resolved as specified in the message.

Recommended Action Inspect the GBIC and cable connections. The local and remote RX cables must be connected to each other.

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 slot indicated has crashed and sent a CRASH_START message to the Route Processor (RP). The RP is now waiting for the rest of the crash information, including the stack trace, context, and version information, from the line card to be sent through the maintenance bus (MBus). This crash information should be sent a few milliseconds after you receive the CRASH_START message. 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 that confirms the TIMEOUT details and reports the line card crash to the rest of the RP software.

Recommended Action Report this defect to a Cisco technical support representative, along with all of the available information about the line card in question, including the output of the show context summary, show context slot and show tech-support commands, as well as the usual 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 Route Processor (RP) was called from the maintenance bus (MBus) subsystem with an invalid DEVICE identifier. The DEVICE in this case is supposed to be the slot number of the line card, but it was out of range. This message indicates a software defect in the system.

Recommended Action Report this defect with as much information about the MBus subsystem as possible. There is no adverse effect to the RP--- it ignores the invalid callback and continues. If the problem persists, reboot the router. It is unlikely but possible that the problem was caused by defective maintenance bus (MBus) hardware somewhere in the system, probably 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 line card indicates that it is in an unknown state. This error is caused by a software defect in that subsystem.

Recommended Action Report this defect to a Cisco technical support representative. Gather as much information as possible about the maintenance bus (MBus) subsystem and the line card crash information subsystem, and provide that information to the representative.

Error Message

%LCINFO-3-NOBUF: Could not malloc line card crash structures on RP (size=[int])

Explanation The Route Processor (RP) could not allocate memory for line card crash data structures at the startup time. This problem is not a serious one, but the underlying memory shortage at startup time will probably shut a router down or at least cause it to run poorly.

Recommended Action Research the memory shortage problem or consider adding 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 Route Processor (RP) could not allocate memory to one or more buffers to hold the line card crash information at startup time. By itself, this is not a serious problem, but the underlying memory shortage at startup time will probably prevent the router from running well, if at all.

Recommended Action Add more memory and resolve the memory shortage problem.

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 failure is probably caused by a software defect or hardware failure and should occur 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 Route Processor (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 is not a crash dump---it is a small amount of information that usually includes context, stack trace, and so forth. It is less than 8K bytes of information. If an "END OF CRASH INFORMATION" message is not received before the timer times out, 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 crashed (at which point it is probably reloaded). If the line card sends more crash information after the timer times out 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. However, because the line card crashed, there might be other defects to report. If this message is seen without a line card crash, call your Cisco technical support representative to report this defect with the output of 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 sent crash information to the Route Processor (RP). The RP received a "CRASH RECORD START" message that indicated the start of another record. The current record is marked as truncated, and the next record is received, but the anomaly is noted in this error message. This problem warrants investigation, because what started this process was a line card crashing, but this might only be a symptom of another underlying problem.

Recommended Action Report this defect to your Cisco technical support representative. Provide the representative with as much information as possible about the maintenance bus (MBus) subsystem and the line card crash information subsystem.

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 Route Processor (RP) since it ignores the message and recovers from this occurrence. The sender of these messages is a line card that is crashing. The source of the crash on the line card is more significant. If this message occurs without a line card crash, it is caused by a stray or errant maintenance bus (MBus) message that should be pursued. This 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 Gigabit Switch Router (GSR) line card logger subsystem error messages.

Error Message

%LCLOG-3-INVDEV: Invalid line card number in MBUS callback (LC=[int])

Recommended Action Report this defect to your Cisco Technical Support representative. Provide the representative with as much information as possible about the MBus subsystem. This defect has no adverse affect on the RP. The RP ignores the invalid callback and continues. If the problem keeps recurring, reboot the router. It is unlikely but possible that the problem is caused by malfunctioning MBus hardware somewhere in the system, probably 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. Provide the representative with 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 Route Processor (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 error is probably caused by a software defect.

Recommended Action Report this error to your Cisco technical support representative. Provide the representative with 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 Route Processor (RP) part of the line card logger server has received more text for a message than the start message indicated. This error is probably caused by a software defect.

Error Message

%LCLOG-3-OVERFLOW: LC log msg longer than msg buffer (LC=[int],len=[int],max=[int])

Explanation The Route Processor (RP) part of the line card logger server has received more text for a message than will fit in the message log buffer. This error is probably caused by a software defect.

LCOC12_CH_DS3 Messages

The following are Gigabit Switch Router (GSR) 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. If you cannot determine the nature of the error from the error message text, call 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=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation High-Level Data Link Control (HDLC) buffer management ASIC (BMA) engine hardware errors have occurred.

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 slot specified. If the diagnostics pass, enter the execute-on slot show controller oc12 all details command. If you cannot determine the nature of the error from the error message text or the output from the show controller command, call 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]=0x[hex]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation A parity error has occurred on High-Level Data Link Control (HDLC) buffer management ASIC (BMA) engine.

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 the problem still exists after correcting the clock configuration, 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, call 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=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation High-Level Data Link Control (HDLC) engine hardware errors have occurred.

Error Message

%LCOC12_CH_DS3-1-INITFAIL: OC12 [dec]/[dec] hardware initialization failure

Explanation An OC12-channelized-to-DS3 line card initialization failure has occurred.

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 interface descriptor block (IDB) is missing.

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 interface descriptor block (IDB) associated subblock is missing.

Error Message

%LCOC12_CH_DS3-3-SRAMPAR: [chars] HDLC, [chars]. [chars]=0x[hex][chars]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation A parity error has occurred on High-Level Data Link Control (HDLC) ASIC SRAM.

Error Message

%LCOC12_CH_DS3-4-UNKNOWNPARAM: OC12 [dec]/[dec][chars] parameter value is unknown

Explanation An unknown parameter was used for the oc12-channelized-to-ds3 controller or channel ipc command.

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 Packet-over-SONET (POS) line card instance was 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, call 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 exceeds 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 output of these commands, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%LCPLIM-3-UNDEFCMD: Interface [dec]: unsupported [chars] command =0x[hex]

Explanation An undefined command was received on 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, call 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 was 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 output of these commands, call 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=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation Packet-over-SONET (POS) buffer management ASIC (BMA) engine hardware errors have occurred.

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, call 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]=0x[hex]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation A parity error has occurred on the Packet-over-SONET (POS) asic buffer management (BMA) engine.

Error Message

%LCPOS-1-INITFAIL: LCPOS([dec]/[dec]), initialization timeout failure

Explanation The line card Packet-over-SONET (POS) ASIC and framer initialization have failed.

Error Message

%LCPOS-3-LINKBADEVT: Unexpected event woke up LC POS link process.

Explanation A line card Packet-over-SONET (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, call 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 process

Explanation The line card Packet-over-SONET (POS) link report process cannot be created.

Error Message

%LCPOS-3-LINKPROC: LCPOS, lcpos_link_report process: Could not get argument

Explanation The line card Packet-over-SONET (POS) link report process has failed.

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 and show memory summary command output, call 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=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation Packet-over-SONET (POS) engine hardware errors have occurred.

Error Message

%LCPOS-3-RXPOSTO: LCPOS([dec]/[dec]), RX POS engine shutdown failed

Explanation The software is trying to shut down the RX Packet-over-SONET (POS) engine. The RX POS engine did not shut down the software timed out.

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 slot specified. If the diagnostics pass, issue the execute-on slot number show controller 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 controller pos registers command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%LCPOS-3-SOP: [chars] SOP. (source=0x[hex], halt_minor0=0x[hex])

Explanation Second-Generation Packet-over-SONET (SOP) hardware errors have occurred.

Error Message

%LCPOS-3-SRAMPAR: [chars] POS, [chars]. [chars]=0x[hex][chars]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation A parity error has occurred on the Packet-over-SONET (POS) ASIC SRAM.

Error Message

%LCPOS-3-TXPOSTO: LCPOS([dec]/[dec]), TX POS engine shutdown failed

Explanation The software is trying to shut down the TX Packet-over-SONET (POS) engine. The POS engine did not shut down and the software timed out.

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 slot specified. If the diagnostics pass, issue the execute-on slot number show controller 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 controller pos registers command output, call 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: msgtxt_fddi_illegal

Explanation The router does not have enough I/O memory to support a 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 two 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 went 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 powered off. The command will automatically be resent once 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 received from the host router. Possible causes are as follows:

The LAN Extender ran out of memory.
The message from the host router is malformed.
A request to write Flash memory occurred while the LAN Extender was busy writing Flash memory for a previous request.
The size of a file to be downloaded is greater than the amount of Flash memory available.

Recommended Action If the command was copy tftp lex unit-number or copy flash lex unit-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 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 This error was probably caused by a memory limitation or the passing of illegal data into the text to fax engine. The fax transmission will be aborted.

Error Message

%LIBT2F-3-GETBUFFER_FAILED: Cannot allocate a packet rom shared memory

Explanation The system is running low on packet memory. The fax cannot be sent correctly.

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.

Error Message

%LIBT2F-3-NULL_BUFFER: A text buffer is NULL

Explanation An internal error has occurred within the text buffer process. The fax transmission will be aborted.

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 dial peer tag was received.

Error Message

%LIBTIFF-4-COPY_QUALITY: Bad copy quality on tty d

Explanation Noisy phone lines or a bad modem caused this error.

Error Message

%LIBTIFF-3-ENGINE_FAILED: The tiff engine failed

Explanation This error was probably caused by a memory limitation or the passage of illegal data into the Tagged Image File Format (TIFF) engine. The fax transmission will be aborted.

Error Message

%LIBTIFF-3-GETBUFFER_FAILED: Cannot allocate a packet rom shared memory

Explanation The system is running low on packet memory. The fax cannot be sent correctly.

Error Message

%LIBTIFF-3-INVALID_BUFFER: A tiff buffer is invalid

Explanation An internal error has occurred within the Tagged Image File Format (TIFF) buffer process. The fax transmission will be aborted.

Error Message

%LIBTIFF-3-NEW_CONTEXT: A new tiff context could not be created

Explanation An internal error has occurred during the initialization of the Tagged Image File Format (TIFF) engine. The fax transmission will be aborted.

Error Message

%LIBTIFF-3-NULL_BUFFER: A tiff buffer is NULL

Explanation An internal error has occurred in the Tagged Image File Format (TIFF) buffer processing. The fax transmission will be aborted.

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.

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.

Error Message

%LINECARD-3-NRP_CRASHING: NRP slot [dec] subslot [dec] crashing

Explanation An Node Route Processor (NRP) subslot on the line card has failed.

Error Message

%LINECARD-3-NRP_CRASHREBOOT: NRP slot [dec] subslot [dec] crashed and rebooted

Explanation An Node Route Processor (NRP) slot on the line card has failed, and the router has rebooted.

Error Message

%LINECARD-3-NRP_NONOP: NRP slot [dec] subslot [dec] non-operational

Explanation An Node Route Processor (NRP) slot on the line card has failed.

Error Message

%LINECARD-3-NRP_SECONDARYDEAD: NRP slot [dec] subslot [dec] reports EHSA secondary down

Explanation The EHSA secondary has gone down.

Error Message

%LINECARD-3-NRP_SECONDARYUP: NRP slot [dec] subslot [dec] reports EHSA secondary up

Explanation The EHSA secondary has gone up.

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.

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. This message may indicate a configuration error.

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.

Error Message

%LINK-4-BADQID: Interface [chars], bad output queue ID specified ([dec]). Packet dropped

Explanation An internal software error has occurred.

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 undefined entry point with the virtual interface descriptor block (IDB) driver.

Error Message

%LINK-6-BERTSTATUS: Interface [chars], [chars]

Explanation BERT is completed for this interface.

Error Message

%LINK-3-BOGUSENCAP: msgtxt_badencap

Explanation A serial interface has been configured with an unknown encapsulation.

Error Message

%LINK-5-BOOTP: [chars] address [int], resolved by [int]

Explanation The IP address of an interface was successfully learned dynamically through BOOTP. The first address is the learned IP address. The second IP address is the IP address of the BOOTP server that provided the information.

Recommended Action No action is required.

Error Message

%LINK-4-BRIDGECONFLICT: Interface [chars], encapsulated BPDU recvd from [sci_notation]

Explanation An FCIT running in nonencapsulating transparent mode has detected a FDDI bridge running in encapsulation mode on the same fiber. This error indicates an unstable situation and it should be corrected. The incoming interface is displayed, along with the FDDI MAC address in standard form.

Recommended Action Upgrade the errant interface to full transparent mode. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.

Error Message

%LINK-5-CHANGED: Interface [chars], changed state to [chars]

Explanation The interface hardware has changed state.

Error Message

%LINK-3-COMPREG: Interface [chars], non-existent (de)compression registry. Packet dropped

Explanation A software or hardware error has occurred.

Error Message

%LINK-3-EMPTYPAK: Interface [chars], empty packet dequeued; linktype [dec], queue [dec]

Explanation An internal software error has occurred.

Error Message

%LINK-4-FDDISTAT: Interface [chars], FDDI state [chars] detected

Explanation There was a state change on the FDDI ring.

Error Message

%LINK-3-IDBLISCRE: Unable to create [chars] interface list

Explanation An internal software error has occurred.

Error Message

%LINK-3-IDBLISINS: Not able to insert interface [chars] into [chars] list

Explanation An internal software error has occurred.

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 tried to call this routine with interrupts enabled.

Error Message Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information

Error Message

%LINK-2-LINEST: No linestate vector for [chars]

Explanation An internal software inconsistency has been detected.

Error Message

%LINK-5-LOOPSTATUS: Interface [chars], [chars]

Explanation The interface has entered or exited loopback.

Error Message

%LINK-4-NOMAC: A random default MAC address of [sci_notation] 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 Make sure that the address referenced in the error message text is unique, or specify MAC addresses for commands such as novell 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 provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%LINK-5-RARP: [chars] address [int], resolved by [int]

Explanation The Reverse Address Resolution Protocol (RARP) has resolved an IP address.

Error Message

%LINK-0-REENTER: Fatal reentrancy, level=[dec], intfc=[chars]

Explanation An internal software error has occurred. The system code tried to access a critical data structure that was already in use.

Error Message

%LINK-5-REMLOOP: Interface [chars], remote loop [chars] [chars]

Explanation The interface has entered or exited a remote loopback.

Error Message

%LINK-5-SLARP: [chars] address [int], resolved by [int]

Explanation The Serial Line Address Resolution Protocol (SLARP) has resolved an IP address.

Error Message

%LINK-4-TOOBIG: Interface [chars], Output packet size of [dec] bytes too big

Explanation An internal software error has occurred.

Error Message

%LINK-3-TOOSMALL: Interface [chars], Output runt packet of [dec] bytes

Explanation An output packet was 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.

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.

LLIST Messages

The following are linked list facility error messages.

Error Message

%LLIST-3-OFFLIST: [chars] from 0x[hex], 0x[hex] not on list

Explanation An internal inconsistency was detected during an attempt to remove an item from a list when that item was not really on the list.

Error Message

%LLIST-3-ONLIST: [chars] to 0x[hex], 0x[hex] on list

Explanation An internal inconsistency was detected during an attempt to add an item to a list when that item was already on the list.

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.

Error Message

%LNMC-3-BADCLSICNF: [chars] Invalid confirm [chars] [chars]

Explanation A LAN network manager system error has occurred.

Error Message

%LNMC-3-BADCLSIDATALEN: [chars] Bad data len = [dec] [chars]

Explanation A LAN network manager system error has occurred.

Error Message

%LNMC-3-BADCLSIHDRLEN: [chars] Bad header len = 0x[hex] [chars]

Explanation A LAN network manager system error has occurred.

Error Message

%LNMC-3-BADCLSIIDTYPE: [chars] Invalid ID type = 0x[hex] [chars]

Explanation A LAN network manager system error has occurred.

Error Message

%LNMC-3-BADCLSIIND: [chars] Invalid indication [chars], [chars]

Explanation A LAN network manager system error has occurred.

Error Message

%LNMC-3-BADCLSIPRIMTYPE: [chars] Invalid primitive type = 0x[hex] [chars]

Explanation A LAN network manager system error has occurred.

Error Message

%LNMC-3-BADCLSIRET: [chars] Invalid ret code (0x[hex]) [chars], [chars]

Explanation A LAN network manager system error has occurred.

Error Message

%LNMC-3-BADCLSISAP: [chars] Bad clsi SAP id = [hex] [chars]

Explanation A LAN network manager system error has occurred.

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 line printer daemon (LPD) data destined for a printer configured with a newline-convert command. This message is unlikely to occur with a file containing valid data.

Recommended Action Check the file being printed to see whether it contains valid, printable data.

LSS Messages

The following are LS1010 Switching Control Layer error messages.

Error Message

%LSS-4-INTERFACE: (Interface [chars]) [chars]

Explanation An internal software error has occurred.

Error Message

%LSS-1-INTERNAL_ALERT: [chars]

Explanation This message reports an internal alert regarding a condition that should be corrected immediately.

Error Message

%LSS-7-INTERNAL_ASSERT: [chars]: [chars] Assertion Failure - File [chars] Line [dec]

Explanation An internal software error has occurred.

Error Message

%LSS-2-INTERNAL_CRITICAL: [chars]

Explanation This message reports an internal alert regarding a condition that should be corrected immediately.

Error Message

%LSS-3-INTERNAL_ERROR: [chars]

Explanation An internal software error has occurred.

Error Message

%LSS-6-INTERNAL_EVENT: [chars]

Explanation This message provides information on an internal event.

Recommended Action No action is required.

Error Message

%LSS-0-INTERNAL_PANIC: [chars]

Explanation An internal software error has occurred.

Error Message

%LSS-4-INTERNAL_WARNING: [chars]

Explanation An internal software error has occurred.

Error Message

%LSS-4-LSIPC: [chars] [dec]

Explanation This message indicates an LSIPC warning; the LSIPC is timing out, and the EPAM may not be responding.

M32X Messages

The following are M32X Basic Rate Interface (BRI) Trunk Card error messages.

Error Message

%M32X-1-AR_TIMEOUT: M32X controller [dec], channel 0x[hex]: No Reponse from device. Action Request Timeout

Explanation An 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 = 0x[hex], received = 0x[hex]

Explanation The download of the internal microcode to the M32X failed to checksum correctly. This message usually indicates an M32X hardware failure.

Recommended Action Perform a power cycle. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%M32X-1-DWNLDFL: M32X down load failed

Explanation The M32X trunk card has failed. It could not download its operational microcode.

Error Message

%M32X-1-INITFAIL: M32X slot [dec]: Init Failed at [chars]

Explanation The M32X trunk card has failed to complete a hardware initialization.

Error Message

%M32X-3-MBXREAD: M32X: Stale msg in [chars] - mbx0:%lx mbx1:%lx mbx2:%lx

Explanation The M32X trunk card has not responded to a message within a specified time.

Error Message

%M32X-1-NOTCMPLT: M32X download failed to complete

Explanation The M32X trunk card has failed. It could not download its operational microcode.

Error Message

%M32X-3-NOTM32X: Device reported [hex]

Explanation A hardware error has occurred involving the protocol control information (PCI) interface for an M32X trunk card.

Recommended Action Either an M32X trunk card is defective or another PCI device has been mistaken for an M32X. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%M32X-1-NOTREADY: Not ready for download

Explanation The M32X trunk card did not respond when commanded to download its operational microcode.

Error Message

%M32X-3-PANIC: M32X: Exception [dec], trace [dec]

Explanation A software or hardware error has occurred in the M32X trunk card.

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 the commands used to initialize it.

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.

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.

MAILBOX Messages

The following are ChipCom mailbox support error messages.

Note All MAILBOX-class messages are generated in response to various conditions arising from the use of a mailbox implemented on a partner port of the Cisco 2500. The mailbox is used to pass administrative information between the router and the main management module of the platform of the partner.

Error Message

%MAILBOX-3-BADCHKSUM: Checksum failed. Expected = 0x[hex], calculated = 0x[hex]. Ignoring PDU

Explanation A hardware or software error has occurred.

Error Message

%MAILBOX-3-BADECHO: Echo-response did not match echo-request

Explanation The data received from an ECHO_RESPONSE protocol data unit (PDU) does 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 MAILBOX-3-INITFAIL for more information.

Recommended Action Verify the router module installation. Make ensure that the software revision on the management module and the router module carrier card is up to date. If the error persists, call your Cisco technical support representative for assistance.

Error Message

%MAILBOX-3-BADPDU: PDU of type [chars] received. Invalid or unsupported. Ignoring

Explanation The protocol data unit (PDU) that the mailbox received was valid, but the type is not supported in the current software implementation. The PDU will be ignored.

Recommended Action 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 off line 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 version on the management module and on the router module carrier card is up to date. If the error persists, call your Cisco technical support representative for assistance.

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 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, use the debug mailbox command.

Recommended Action 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 in the communication path between the router module and its carrier card.

Recommended Action Verify the router module installation. Make sure the software version on the management module and the router module carrier card is up to date. If the error persists, call your Cisco technical support representative for assistance.

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. The message indicates that a problem exists between the perceived state of the mailbox from the side of the router and the perceived state from the side of the management module.

Recommended Action Issue a system-wide reset on the management module. If the error persists, call your Cisco technical support representative for assistance.

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 No action is required.

Error Message

%MAILBOX-7-READ: Reading 0x[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 No action is required.

Error Message

%MAILBOX-3-TIMEOUT: Intra-PDU timeout occurred on [chars] mailbox data

Explanation A timeout occurred while the characters of a protocol data unit (PDU) were being sent or received. The entire PDU will be ignored.

Recommended Action No action is required.

Error Message

%MAILBOX-7-WRITE: Writing 0x[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 No action is required.

MBRI Messages

The following are Multi-BRI (MBRI) port module error messages.

Error Message

%MBRI-1-CHANINITFAIL: [chars] [chars] failed

Explanation The Multi-BRI (MBRI) network module has failed to complete 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, call 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 Multi-BRI (MBRI) network module has failed to complete initialization.

Error Message

%MBRI-3-NOTMBRI: Bay [dec] device ID seen as [hex], expected [hex]

Explanation The network module hardware reports that a non-MBRI port module was detected.

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 condition.

Error Message

%MBRI-3-UNKNOWN_STATE: [chars] layer1 state is [dec]

Explanation The Multi-BRI (MBRI) driver has detected an invalid Layer 1 condition.

MBUS Messages

The following are maintenance bus (MBus) error messages.

Error Message

%MBUS-3-BADCLK: Slot [dec] does not see fabric clock from [chars] Card will not operate on fabric using this clock

Explanation The slot must see the fabric clock from at least one of the clock switch cards (CSCs). If just one CSC is present, the card must synchronize to that clock to operate on the fabric. If two CSCs are present, the following cases are possible. If the CSCs were configured to be redundant, the card will function if it can synchronize to at least one of the clocks. The card will be configured to use that clock in the nonredundant mode. If the CSCs are not redundant (when one CSC is defective), the whole chassis will be configured for one of the two CSCs and all the cards must synchronize to this (primary) CSC. A card that has failed to synchronize to the selected primary CSC will not operate over the fabric. Note that if two CSCs are present, they will be configured as redundant unless the clocks fail to lock. That error message should have been reported earlier in the process.

Recommended Action Verify that the card is seated correctly. Try to reset or power-cycle the card. Run diagnostics for the card if possible. If the condition persists, copy the error message exactly as it appears along with previous error messages and report it to your Cisco technical support representative.

Error Message

%MBUS-0-CLKFAIL: Switched Primary Clock to [chars] ; FS error in slot [int]

Explanation A hardware failure has occurred. The primary clock for the system had to be changed because frame synchronization errors were detected in the specified slot. The switch will take place under the conditions described below. Note that when the switch to a new clock is made, the Route Processor (RP) and clock switch card (CSC) combination is not known to have failed previously. The switch is made when

The Gigabit Route Processor (GRP)/Primary CSC detects frame synchronization failures.
the GLC/SFC/Secondary CSC detects frame synchronization failures. These switchovers are rate-limited to once every 10 minutes.

A card can cause only one switchover. Note that the inability of the card to detect frame synchronizations from the primary clock is a catastrophic failure that makes it inoperable on the fabric. The condition will usually manifest itself as a CRC error in the FIA, resulting in transfer errors over the fabric.

Recommended Action Run diagnostics on the specified card and the original primary CSC if possible. If fabric errors persist, remove the CSC, copy the error message exactly as it appears (as well as the preceding error messages), and report it to your Cisco technical support representative.

Error Message

%MBUS-2-CLKSTATUS: Slot [dec] [chars]

Explanation The slot clock has changed its redundancy state. If the card has lost its redundancy state, it can still operate with the other clock. This problem may be localized to the line card or may be a global event caused by a malfunctioning clock switch card (CSC) card. In the latter case, multiple line cards (all) will show this condition.

Recommended Action Verify that the other clock is seen correctly using the show controller clock command.

Error Message

%MBUS-3-CSCCLK: Fab CLOCK FPGA in Slot [dec] did not see all Fabric Clocks. FAB_CLK_FPGA_fabClkSts Register = [hex] If bit 0 of the register is set implies clk_0 is bad if bit 1 of the register is set implies clk_1 is bad Fabric Clocks could not be configured as redundant.

Explanation There are two clock switch cards (CSCs) in the system, but they cannot synchronize with each other. They are therefore configured as nonredundant.

Recommended Action Copy the error message exactly as it appears along with the preceding error messages and report it to your Cisco technical support representative.

%MBUS-2-CLKSYNC: [chars] could not lock to [chars].Clocks could not be configured as redundant

Explanation An attempt to lock the fabric clocks has failed. A hardware failure has occurred. This message indicates that the clock or scheduler redundancy cannot be achieved (in this configuration). If this failure occurs during the boot process, the system primary clock will be chosen by a majority rule; that is, the primary clock will be the clock to which the majority of the cards are synchronized. If this failure occurs during an online insertion and removal (OIR) event, the initial primary clock will be maintained. Cards that do not synchronize to the selected primary clock will not operate over the fabric. Use the show controller clock command to check the clock configuration for the individual cards.

Recommended Action Replace or reinsert the clock switch cards (CSCs) and try again. If the condition persists, copy the error message exactly as it appears along with previous error messages and report it to your Cisco technical support representative.

Error Message

%MBUS-3-CSC_ONLY: Slot [dec] can only have CSC cards

Explanation Slots 16 and 17 can contain only clock switch cards (CSCs).

Recommended Action Remove any card that is not a CSC from the specified slot. If you are sure it is a CSC card, verify that the EEPROM is programmed correctly. To read the EEPROM contents, use the show diags details command and report the output to your Cisco technical support representative.

Error Message

%MBUS-6-CSC_OVER_BKPL: [chars] overriding backplane nvram chassis type [chars]

Explanation The clock switch card (CSC) represents a different chassis type from the chassis type that is programmed into the chassis backplane NVRAM.

Error Message

%MBUS-6-DISCOVERED_CARDS: [dec] [chars] present in 0x[hex] (bitmask)

Explanation This message reports the list of discovered cards.

Recommended Action No action is required.

Error Message

%MBUS-2-DNLDFAIL: [chars] download to slot [dec]

Explanation The specified image could not be downloaded to the card. The card will be automatically reset and the download retried.

Recommended Action Try resetting, power-cycling, or reinserting the card. If the condition persists, copy the error message exactly as it appears, along with previous error messages, and report it to your Cisco technical support representative.

Error Message

%MBUS-0-DOWNREV: [chars] [dec] [chars]

Explanation The specified module is an old version.

Recommended Action Obtain the new version from your Cisco technical support representative.

Error Message

%MBUS-3-EEPROM: Failed read EEPROM location [hex] in slot [dec] [chars]

Explanation An attempt to read the EEPROM contents in the specified slot has failed.

Recommended Action Check other following error messages.

Error Message

%MBUS-6-FABCONFIG: Switch Cards 0x[hex] (bitmask)Primary Clock is [chars] Fabric Clock is [chars] Bandwidth Mode : [chars]

Explanation The switch fabric card (SFC) is configured as specified in this message.

Recommended Action No action is required.

Error Message

%MBUS-0-FABINIT: Failed to initialize switch fabric infrastructure

Explanation This message indicates that at least one clock switch card (CSC) must be detected and configured.

Recommended Action Insert a CSC. If a CSC is present, verify it is seated correctly and power cycle or reboot the GSR. If the condition persists, copy the error message exactly as it appears (as well as the previous error messages) and report it to your Cisco technical support representative.

Error Message

%MBUS-0-FAB_FAILURE: Unrecoverable fabric error detected on switch card [int]

Explanation Errors have been detected by the line card or Route Processor (RP) from the specified switch card. However, because of the lack of redundancy in the fabric, this card cannot be removed.

Recommended Action Replace this switch card and contact your Cisco technical support representative.

Error Message

%MBUS-6-FIA_CONFIG: Switch Cards 0x[hex] (bit mask Primary Clock [chars]

Explanation The FIA was configured as specified in this message.

Recommended Action No action is required.

Error Message

%MBUS-6-FIA_STATE: [chars]

Explanation The FIA has been halted.

Recommended Action No action is required.

Error Message

%MBUS-3-GETMSGFAIL: Failed getting process message from MBUS device [int] -- [chars]

Explanation A maintenance bus (MBus) message and an error message were sent back. An internal software error has occurred.

Error Message

%MBUS-0-FAB_FAILURE: Unrecoverable fabric error detected on switch card [int]

Recommended Action Replace this switch card and contact your Cisco technical support representative.

Explanation has not seen the frame synchronizations within the required intervals. The GRP must see frame synchronizations every 1.04 milliseconds.

Recommended Action Power-cycle the Gigabit Switch Router (GSR). If the condition persists, contact your Cisco technical support representative.

Error Message

%MBUS-6-GRP_STATUS: [chars] [dec] [chars]

Explanation This message provides Gigabit Route Processor (GRP) Master or Slave status information.

Recommended Action No action is required.

Error Message

%MBUS-3-INSUFF_BW: Insufficient fabric bandwidth to launch and operate card in slot [dec]

Explanation Some line cards (for example, 4 Port E.D. Packet Over SONET OC-12c/STM-4 and 1 Port E.D. Packet Over SONET OC-48c/STM-16) cannot operate in quarter-bandwidth mode. Full fabric bandwidth must be available to launch and operate these line cards. Full fabric bandwidth is typically achieved either by one clock switch card (CSC) and three switch fabric cards (SFCs), or two CSCs and two SFCs. To obtain fully redundant, full fabric bandwidth, you must use a configuration of two CSCs and three SFCs. In any case a minimum of one CSC and three or more additional switch cards (CSC or SFC) are required for full fabric bandwidth.

Recommended Action Make sure the CSCs and SFCs are properly inserted and in good working condition. Ensure that there is a total of four working switch cards and that at least one switch card is a CSC. If any switch card is missing or nonoperational, contact your Cisco technical support representative.

Error Message

%MBUS-3-IOSCRASH: Slot [dec]

Explanation The ROM monitor reports that the Cisco IOS software on the line card has crashed.

Recommended Action The line card is automatically reset by the Gigabit Route Processor (GRP). If the problem persists, try reinserting the line card. If this error message recurs, run diagnostics on the line card.

Error Message

%MBUS-2-LAUNCHERR: [chars] for Slot [dec] status [hex]

Explanation The specified module could not be successfully launched.

Recommended Action Reset the line card. If the condition persists, copy the error message exactly as it appears, along with previous error messages, and report it to your Cisco technical support representative.

Error Message

%MBUS-3-MISMATCHED_FABCONF: Master GRP Fabric Config: Switch Cards [hex] Master Clock [hex] Line Card [dec] Fabric Config: Switch Cards [hex] Master Clock [hex]

Explanation The fabric configurations for the cards are assigned by the master Gigabit Route Processor (GRP). The configurations may be temporarily different during the reconfiguration of the fabric (such as the insertion, removal, or malfunction of the switch cards) because the GRP has changed its configuration but has not yet notified the line card. The line card may modify its FIA configuration without changing its bandwidth mode. In addition, it is permissible for the line card to have a different primary clock if there are two clock switch cards (CSCs) that are configured as redundant.

Recommended Action No action is required.

Error Message

%MBUS-6-MODEL_INVALID: Chassis Model invalid [dec] (CSC types(0x[hex],0x[hex]) invalid for overide)

Explanation The model type programmed into the backplane NVRAM was invalid. The clock switch cards (CSCs) in the chassis also contained invalid model types.

Error Message

%MBUS-3-MSGTOOBIG: MBUS message length too big (dev=[int],type=[int],len=[int])

Explanation An MBus message received exceeds the maximum size of 254 bytes. This error indicates a software defect.

Error Message

%MBUS-0-NOCARDS: No Cards detected in slots 1 - [dec]

Explanation No cards were detected. At least the Gigabit Route Processor (GRP) must be discovered by the MBus.

Recommended Action Power-cycle the Gigabit Switch Router (GSR) and retry. If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MBUS-0-NOCSC: [chars]

Explanation At least one clock switch card (CSC) must be present in the system.

Recommended Action If necessary, insert a CSC in slot 16 or 17 and reboot the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MBUS-0-NOFABCARD: There must at least be a CSC card in slot 16 or 17

Explanation No fabric card was detected in the system.

Recommended Action If necessary, insert a clock switch card (CSC) in slot 16 or 17 and reboot the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MBUS-3-NOFABCLK: Slot [dec] does not see any fabric clock Card will not operate on

Explanation The slot must see the fabric clock from at least one of the clock switch card (CSCs).

Recommended Action Reset, power-cycle or reinsert the CSC. If the error persists, copy the error message exactly as it appears, along with previous error messages, and report the information to your Cisco technical support representative.

Error Message

%MBUS-0-NOIMAGE: [chars]

Explanation The image was missing in the bundle linked with this Cisco IOS image. The image is required for downloading. A missing image usually signifies a build problem.

Error Message

%MBUS-3-NOPROCESS: Failed creating User LED Process

Explanation The call to process_create has failed when creating the process used to handle the timers for the user commands to write to the LEDs. The only effect of this failure is that the user commands to write LED messages will not work, but there may be more serious problems if the Cisco IOS software is having trouble creating processes during initialization.

Recommended Action Reboot the router. If the condition persists and is confined to this process, ignore the problem and continue.

Error Message

%MBUS-0-OLD_SCA: Old SCA found on clock switch card (CSC) in slot [dec]

Explanation The clock switch card (CSC) is an old or nonproduction card.

Recommended Action Obtain a new CSC from your Cisco technical support representative.

Error Message

%MBUS-6-OIR: [chars] [chars] [dec]

Explanation An an online insertion and removal (OIR) event was detected as specified in the message.

Recommended Action No action is required.

Error Message

%MBUS-3-READREG: Failed to read register [hex] in slot [dec] [chars]

Explanation An attempt to read the register in the specified slot has failed

Recommended Action Check other error messages that follow.

Error Message

%MBUS-5-REBOOT: [chars] [dec] [chars]

Explanation The line card is being reset because it was not downloaded or configured by this GRP. The GRP must be able to synchronize with the line card state in order to prevent a reset of the entire chassis on every boot of the GRP. This condition will also occur when the GRP is booted with a newer (potentially incompatible) version of Cisco IOS software. The line card will be reset and a compatible image downloaded.

Recommended Action Avoid a reboot of the GRP when the line cards are configured and running.

Error Message

%MBUS-3-REGISTER: Status change from unknown register [hex] in slot [dec] Value = [hex]

Explanation A register that was not being monitored has indicated a status change. This is probably a software error.

Recommended Action If the condition persists, contact your Cisco technical support representative.

Error Message

%MBUS-0-REGISTRY: Failed to create registry [chars][chars]

Explanation The specified registry could not be created. This is a catastrophic error for this feature. This condition requires the intervention of a developer for a solution.

Error Message

%MBUS-3-SC_REMOVED: Switch card [int] being removed from fabric configuration.

Explanation Errors have been detected by the line card or the Route Processor (RP) from the switch card specified in this log message. This card has been removed from the fabric configuration and has been powered down.

Recommended Action Remove or replace this clock switch card and contact your Cisco technical support representative.

Error Message

%MBUS-0-SELFDISCOVER: Unknown GRP slot number. Power cycle the GSR and retry

Explanation At least the local Gigabit Route Processor (GRP) must be discovered via the MBus.

Recommended Action Power-cycle the Gigabit Switch Router (GSR) and retry.

Error Message

%MBUS-3-SFC_ONLY: Slot [dec] can only have SFC cards

Explanation Slots 18 through 20 can contain only switch fabric cards (FSCs).

Recommended Action Remove cards that are not FSCs from specified slot. If you are sure it is an SFC, verify that the EEPROM is programmed correctly. Use the show diags details command to read the EEPROM contents and report it to your Cisco technical support representative.

Error Message

%MBUS-3-SFLOCK: CSC in Slot [dec] failed to phase lock CSC_FPGA_MCLK = [hex] bit 5 of the register is set Fabric Clocks could not be configured as redundant

Explanation The specified clock switch card (CSC) was to be designated as the secondary clock, but it failed to phase-lock with the primary clock. The primary and secondary clocks are therefore not configured in the redundant mode.

Recommended Action Copy the error message exactly as it appears, along with previous error messages, and report it to your Cisco technical support representative.

Error Message

%MBUS-6-SWITCHED_FABCLK: Slot [dec] switched to [chars]

Explanation The selected clock has changed on the card. If the slot was configured with a redundant clock, then this is the new clock for this card. It should continue functioning in nonredundant mode. If the redundancy mode is maintained, the clock should not switch (unless there is an external user specification or command forcing it to do so).

Recommended Action No action is required.

Error Message

%MBUS-3-TIMEOUT: Timed out waiting for MBUS response from device [int] -- [chars]

Explanation A maintenance bus (MBus) message sent has timed out while waiting for a response. This error could be caused by possible hardware or software problems. Some of the hardware that could cause this problem are the MBus module on the Route Processor (RP), the slot it was sending the message to, and the Gigabit Route Processor (GRP).

Recommended Action For an occasional problem, just ignore the message. For a persistent problem or one involving frequent timeouts, you should send e-mail to the appropriate cs- mailing list. If the problem always is associated with a single slot or MBus device, Cisco recommends that you replace the MBus module or the whole FRU (such as the line card, or power supply). If the problem is associated with many different slots or MBus devices, it is recommended that you replace the RP MBus module or the whole GRP. If replacing hardware does not solve the problem, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%MBUS-6-UNUSED_SFC: In slot [dec]

Explanation The set bandwidth mode does not require the specified switch fabric card (SFC). The switch fabric card will be ignored for the configuration. Removing the SFC will not alter the system performance.

Recommended Action Ensure that the bandwidth mode of the fabric is the expected bandwidth. No action is required.

Error Message

%MBUS-3-WAKEUP: Could not set wake up reason (pid=[int]) -- [chars]

Explanation When sending a maintenance bus (MBus) message and waiting for a response, the process wakeup reason was changed. An error has occurred in getting the current wakeup reason for the process. This problem was caused by an error in the scheduler or some other software bug in the MBus code.

Recommended Action Report this problem to a Cisco technical support representative, providing the exact error message text in addition to the traceback that accompanies it. If the problem recurs frequently, reload the router.

Table of Contents