-
Cisco IOS Release 12.0S System Message Guide
-
System Messages Overview
-
AAAA through AUDIT messages
-
AUTORP through C10KSDCC messages
-
C10K_TOASTER through CBUS messages
-
CE3 through CPUIF messages
-
CRYPTO through ECC messages
-
EDGE through EE192 messages
-
EELC through ENV_MON messages
-
ESMP through FM messages
-
FR through GLCSPA messages
-
GRP through GRPSPA messages
-
GRP_CHOCX through GT96K_FE messages
-
HA through I82543 messages
-
ICC through IPV6FIB messages
-
IP_VRF through LC_CHOCX messages
-
LCCOREDUMP through LCINFO messages
-
LCLOG through MBUSFLASH messages
-
MCC192 through MPLS_TE_LM messages
-
MPLS_TE_PCALC through PM3386 messages
-
PM622 through PRP2 messages
-
PS through RSP messages
-
RSVP through SW_MGR messages
-
SYS through TCAM_MGR messages
-
TCATM through XCPA messages
-
Glossary of Acronyms
-
Table Of Contents
ESMP Messages
The following are Even Simpler Management Protocol (ESMP) messages.
Error Message%ESMP-4-BAD_RESPONSE_OPCODE : response code = [dec]
Explanation ESMP driver errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESMP-4-BAD_SEQ_NO : response id = [dec] cmd_id = [dec]
Explanation ESMP driver errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESMP-4-ESMP_TIMEOUT : [chars]
Explanation ESMP driver errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESMP-4-MEM_ALLOC_FAILURE : [chars]
Explanation ESMP driver errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ESMP-4-REQ_FAIL : [dec]
Explanation ESMP driver errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ET Messages
The following are ET messages.
Error Message%ET-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The ET RP driver running configuration is corrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show c10k and show ipc status commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show c10k and show ipc status command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%ET-3-ERROR : [chars]
Explanation This message provides general error information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ET-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation An ET initialization failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ET-2-NOVC : [chars]: packet received for unknown VC [dec]
Explanation The virtual channel encapsulation is corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ET-1-RESTARTFAIL : [chars] could not be reset by [chars]
Explanation The restart failed to reset the interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ET-1-STOPFAIL : [chars] could not be disabled by [chars]
Explanation The shutdown failed to disable the interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ET-1-UNSUPPORTED : \n[chars]
Explanation Unavailable.
Recommended Action Unavailable.
EVENT Messages
The following are Messages from the Event MIB.
Error Message%EVENT-3-INSERT_FAILURE : Failed to insert [chars]
Explanation The event MIB process failed to insert the newly created row in its linked list data structure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EVENT-3-NULL_ELEMENT : Null pointer in the watched queue for [chars] test
Explanation The process was activated with a NULL element.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EVENT-3-NULL_STRUCT : Null pointer to the [chars] structure
Explanation The process was activated with an element, which had a null pointer to the test structure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
EVENT_TRACE Messages
The following are Event Trace subsystem messages.
Error Message%EVENT_TRACE-3-CLOSE_FILE : Error closing file [chars]
Explanation The event trace subsystem cannot close the specified file.
Recommended Action No action is required. This error will not affect system functionality.
Error Message%EVENT_TRACE-3-CONTINUOUS : Enable trace before setting continuous display
Explanation The event trace specified in the error message must be enabled before continuous display can occur.
Recommended Action Enable the event trace specified in the error message.
Error Message%EVENT_TRACE-6-ENABLE : Trace already enabled.
Explanation The specified event trace has already been enabled.
Recommended Action This is a debug message only. No action is required.
Error Message%EVENT_TRACE-3-GROUP_ID : Duplicate registration of group-id [dec]
Explanation The software subsystem is attempting to register a group ID for an event trace that has already been used by another subsystem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EVENT_TRACE-3-NO_FILENAME : Dump file not specified.
Explanation No file name has been specified as an output file for the event trace.
Recommended Action You must specify the trace dump file name. To specify the trace dump file name, enter the monitor event-trace comp dump-file filename command, with filename being the name of the file, in global configuration mode
Error Message%EVENT_TRACE-6-NO_FORMATTER : [chars]: no formatter provided, binary dumping.
Explanation A formatter function was not provided during the initialization of the specified event trace.
Recommended Action No action is required.
Error Message%EVENT_TRACE-3-NO_MEM : Not enough memory for [dec] trace elements.
Explanation The system memory was insufficient for the number of trace elements specified.
Recommended Action Reduce the size of the event trace.
Error Message%EVENT_TRACE-3-NO_TRACE_NAME : Invalid trace name [chars]
Explanation No trace buffer is known by the name that was entered.
Recommended Action Check whether there is an event trace buffer configured by the name entered and enter the correct trace buffer name.
Error Message%EVENT_TRACE-3-NUM_ELEM : Number of trace element = [dec] is greater than number = [dec] allowed
Explanation The number of trace entries exceeded the allowed amount.
Recommended Action Reduce the number of trace entries.
Error Message%EVENT_TRACE-3-OPEN : [chars]: Trace failed to open
Explanation Initialization of the specified event trace has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%EVENT_TRACE-3-OPEN_FILE : Couldn't open [chars]...
Explanation The event trace subsystem could not open a file for the specified event trace dump.
Recommended Action If a file by the same name already exists, rename the dump file or remove the existing file from the file system.
Error Message%EVENT_TRACE-3-RESIZE : Enable trace before resizing
Explanation The specified event trace must be enabled before resizing occurs.
Recommended Action Enable the specified event trace.
Error Message%EVENT_TRACE-3-SIZE_ELEM : Size of trace element = [dec] is greater than size = [dec] allowed
Explanation The size of the specified individual trace entry was greater than the allowed size.
Recommended Action Reduce the individual trace entry size so that the maximum size is not exceeded while the event trace is being initialized.
Error Message%EVENT_TRACE-3-SIZE_FILENAME : Trace filename size = [dec] greater than size = [dec] allowed
Explanation The length of the specified event trace filename was greater than the allowed length.
Recommended Action Shorten the filename.
Error Message%EVENT_TRACE-3-WRITE_FILE : Error writing to file [chars]
Explanation The event trace was not able to write to the specified file system.
Recommended Action The file system might not be available. Try changing the destination file system and dumping the trace there. If this does not work, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered.
FABRIC Messages
The following are Fabric Interface ASIC (FIA) messages.
Error Message%FABRIC-3-CRC : Switch card [int]
Explanation An excessive number of crc16 errors have been detected from one of the fabric switch cards. This error usually indicates a hardware problem, either on the fabric card that is displayed in the error message or the line card/RP that is reporting the error.
Recommended Action Issue the show controller fia command on the RP and all line cards to determine if the problem is seen with all cards or with only one card. If the problem is seen with only one card, replace the line card/RP. If the problem is seen with more than one card, replace the switch card. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
The exact wording of the error.
•
•
•
Error Message%FABRIC-6-CSC_INFO : Slot [dec] - [chars]
Explanation A CSC of the type specified in the message has been installed in the specified slot.
Recommended Action No action is required.
Error Message%FABRIC-3-ERR_HANDLE : [chars] slot [dec]
Explanation The GRP and the line cards connect through a crossbar switch fabric, which provides a high-speed physical path for most inter-card communication. Among the messages passed between the GRP and the line cards over the switch fabric are included actual packets being routed and received, forwarding information, traffic statistics, and most management and control information. Thus, it is important for the GRP to ensure that this path is operating correctly. This message gives some information about the type of fabric errors, including CRC, LOS, CellDrop, Clock, FIA, or Halt, that have occurred.
Recommended Action Ensure that the fabric cards are seated properly. Then follow the troubleshooting steps, including capturing the required output of the show controller fia command from the GRP and from the line cards, as described in "Hardware Troubleshooting for the Cisco 12000 Series Internet router" at the URL /en/US/products/hw/routers/ps167/products_tech_note09186a00800949bb.shtml#ts_switchfabric.
Error Message%FABRIC-5-ERR_HANDLE_SWITCH : Fabric error handling is [chars]
Explanation This notification message provides information about the status of fabric error handling being either on or off.
Recommended Action No action is required.
Error Message%FABRIC-3-EXTPERRSRAM : Ext SRAM Chip [dec] has Parity Error
Explanation The external SRAM chip reported a parity error, which may indicate a bad SRAM on the line card or other problems with the line card.
Recommended Action If the problem persists, the card will automatically be reset. If the message persists, swap out the line card reporting the error message. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-3-EXTSRAMPERR : Ext SRAM Parity Error @ [hex] = [hex]
Explanation An external SRAM parity error has been detected by the FIA hardware, which may indicate a bad SRAM on the line card or other problems with the line card.
Recommended Action If the problem persists, the card will automatically be reset. If the message persists, swap out the line card reporting the error message. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-3-FIFOERR : [chars] FIFO Error was detected. [chars], Data = [hex].
Explanation A FIFO error has been detected by the FIA hardware. Usually the error is an overflow error, indicating that data is not flowing. This error should not happen under normal circumstances.
Recommended Action If the problem persists, the card will automatically be reset. If the message persists, swap out the line card reporting the error message. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-3-FIA_CONFIG : RP FIA config failed: [chars] [dec]
Explanation The Local RP FIA configuration has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FABRIC-4-FIFONODRAIN : [chars] FIFO failed to drain after applying backpressure.
Explanation After stopping traffic coming into the chip and waiting the maximum time for cells in the FIFOs to drain, the FIFOs are not yet empty.
Recommended Action No action is required unless this message is followed by a higher severity error message. If a higher severity error message follows, restart the Internet router. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-3-HALT : [chars]
Explanation The fabric hardware did not resume from a halt condition. After fabric parameters have been changed, the fabric is reset to allow the new settings to take effect. This error means the fabric did not come back after the reset. This error should not happen under normal circumstances.
Recommended Action Try reseating the boards and power-cycling the Internet router. If the condition persists, there may be a problem with the hardware. Try changing the card indicated by the message. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-0-INFORMATION : [chars]
Explanation This message provides fabric information.
Recommended Action Check to see that the fabric information is correct.
Error Message%FABRIC-0-INIT : Fabric init failed: [chars]
Explanation Fabric initialization has failed.
Recommended Action Ensure that the fabric cards are properly seated.
Error Message%FABRIC-3-INIT : Bad Configuration master_sca = [hex] csc_installed = [hex].
Explanation The clock scheduler cards and switch cards are in an invalid configuration. This error should not happen under normal circumstances.
Recommended Action Restart the Internet router. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-0-INVALID_FAB : Invalid combination of CSCs installed
Explanation The type of switch fabric that is installed cannot be determined.
Recommended Action Check the CSCs that are installed to ensure that they are of the same type.
Error Message%FABRIC-3-LOS : LOS for slot [int] was [chars].
Explanation A loss of synchronization between the line card and the switch card was detected or cleared. The message indicates which fabric card(s) have the error.
Recommended Action Reseat the boards. If that does not fix the problem, swap out the affected cards. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-0-OPERATIONAL : Fabric handling failed: [chars]
Explanation A fabric handler failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FABRIC-3-PAKERR : [chars] packet error was detected. [chars] Data = [hex].
Explanation A packet error was detected by the FIA hardware. Usually the error is the result of a packet with an incorrect length. The hardware state is inconsistent. This error should not happen under normal circumstances.
Recommended Action If the problem persists, the card will automatically be reset. If the message persists, swap out the line card reporting the error message. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-3-PARITYERR : [chars] parity error was detected. [chars] Data = [hex].
Explanation A parity error was detected by the FIA hardware. This message could indicate that a card was inserted incorrectly, or there is a hardware problem. The error indicates that problems exist with the connection between the line card and the fabric cards via the backplane.
Recommended Action If the problem persists, the card will automatically be reset. If the message persists, reseat either all cards in the chassis, or just the card reporting the error message. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-3-REQUESTERR : Request error was detected. Type = [dec]
Explanation A request error was detected by the FIA hardware. This is an inconsistent state that should not occur in normal operation.
Recommended Action Restart the Internet router. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-3-UNEXPECTED : Unexpected interrupt was detected from the [chars] FIA.
Explanation An unexpected interrupt was detected by the FIA hardware. This error should not happen under normal circumstances.
Recommended Action Restart the Internet router. If the message still persists, contact your Cisco technical support representative and provide the representative with the following information:
•
•
•
•
Error Message%FABRIC-0-WRONG_CARD_TYPE : Slot [dec] Cardtype: [chars] not supported on this chassis
Explanation A non-matching fabric card has been inserted.
Recommended Action Replace the fabric card that was just inserted.
FIA Messages
The following are Messages for the Fabric Interface ASIC (FIA).
Error Message%FIA-3-BADSYSCLK : Bad system clock for slot [int] was [chars].\n
Explanation A failed system clock has been detected. This condition could indicate a hardware fault.
Recommended Action Attempt to reseat the boards. If that does not fix the problem, try swapping out the affected cards. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-CRC : Switch card [int]
Explanation An excessive number of CRC16 errors have been detected from one of the fabric switch cards. This almost always points to a hardware problem, either on the fabric card that is displayed in the error message or the line card/RP that is reporting the error.
Recommended Action Enter the show controllers fia command on the RP and the execute-on all show controller fia command to determine if all cards see the problem or if only one card is seeing the problem. If it is only one, replace the line card or RP. If more than one card is seeing the problem, replace the switch card. If the message still persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-EXTPERRSRAM : Ext SRAM Chip [dec] has Parity Error
Explanation The external SRAM chip has reported a parity error. This condition could indicate a failed SRAM on the line card or other problems with the line card.
Recommended Action The device will be reset. If the problem persists, the card will be automatically reset. If the message persists, the line card reporting this error message should be swapped out. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-EXTSRAMPERR : Ext SRAM Parity Error @ [hex] = [hex], [hex], [hex], [hex], [hex], [hex], [hex], [hex]
Explanation An external SRAM parity error was detected by the FIA hardware. This could indicate a bad SRAM on the line card or other problems with the line card.
Explanation The device will be reset. If the problem persists, the card will be automatically reset. If the message persists, the line card reporting this error message should be swapped out. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-EXTSRAMPAR : Ext SRAM Chip [dec] has Parity Error [hex]
Explanation The external SRAM chip has reported a parity error. This condition could indicate a failed SRAM on the line card or other problems with the line card.
Recommended Action The device will be reset. If the problem persists, the card will be automatically reset. If the message persists, the line card reporting this error message should be swapped out. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-FIACONFG : Quarter Bandwidth mode will not work with PRP : [chars].\n
Explanation A quarter-bandwidth configuration has been applied to the Internet Router. The Internet Router performance route processor requires a full-bandwidth configuration to be able to operate correctly. Some of the line cards may not boot with a system in a quarter-bandwidth configuration that contains one clock scheduler card.
Recommended Action Consult the Cisco product documentation that pertains to your specific product and check the number of clock and scheduler cards and the number of switch fabric cards that are required for your particular chassis type. open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format:
–
–
–
–
–
–
Error Message%FIA-3-FIFOERR : [chars] FIFO Error was detected. \n[chars], Data = [hex].
Explanation A FIFO error has been detected by the FIA hardware, usually an overflow, indicating data is not flowing. This error should not happen under any normal circumstances.
Recommended Action The device will be reset. If the problem persists, the card will be automatically reset. If the message persists, the line card reporting this error message should be swapped out. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
•
•
•
•
Error Message%FIA-4-FIFONODRAIN : [chars] FIFO failed to drain after applying backpressure.
Explanation After stopping traffic into the chip and waiting the maximum time for cells in the FIFOs to drain, the FIFOs have not completely emptied.
Recommended Action No action is required, unless this message is followed by a higher severity error message. If a higher severity error message follows, restart the Internet router. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
Error Message%FIA-3-HALT : [chars]
Explanation The fabric hardware did not resume from a halt condition. The fabric is reset after fabric parameters have been changed to allow the new settings to take effect. This error means the fabric did not come back out of reset. It is an unusual condition that should never happen.
Recommended Action Try reseating the boards and power cycling the Internet router. If the condition persists, hardware the may be faulty. If the message persists, the line card reporting this error message should be swapped out. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-INIT : Bad Configuration master_sca = [hex] csc_installed = [hex].
Explanation The system has an invalid configuration of clock scheduler cards and switch cards. This is an unusual condition that should never occur.
Recommended Action Restart the Internet router. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-LOS : LOS for slot [int] was [chars].\n
Explanation A loss of synchronization between the line card and the switch card was detected and cleared. The data shows the fabric card or cards from where the errors were detected.
Recommended Action Try reseating the boards. Failing that, try swapping out the affected cards. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
–
–
–
–
Error Message%FIA-3-PAKERR : [chars] packet error was detected.
[chars] Data = [hex]Explanation A packet error was detected by the FIA hardware. The error is usually an incorrect packet length. The hardware state is inconsistent. This error should not happen in normal operation.
Recommended Action The device will be reset. If the problem persists, the card will be automatically reset. If the message persists, the line card reporting this error message should be swapped out. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
•
•
•
•
Error Message%FIA-3-PARITYERR : [chars] parity error was detected.
[chars] interrupt = [hex].Explanation A parity error was detected by the FIA hardware. This could indicate an incorrectly inserted card, or a hardware fault. The error indicates problems with the connection between the line card and the fabric cards via the backplane.
Recommended Action The device will be reset. If the problem persists, the card will be automatically reset. If the message persists, try reseating either the card with the failure, or all cards in the chassis. If the message still persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
•
•
•
•
Error Message%FIA-3-RAMECCERR : [chars] ECC error was detected
[chars] RAM[dec] status = [hex] Syndrome = [hex] addr = [hex] .Explanation A RAM ECC error was detected by the FIA hardware. This condition could indicate a hardware fault. If the problem persists, the card will be reset automatically.
Recommended Action If this message recurs, try swapping out the affected cards. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
•
•
•
•
Error Message%FIA-3-REQUESTERR : Request error was detected. Type = [dec]
Explanation A request error was detected by the FIA hardware. This is an inconsistent state that should not occur in normal operation.
Recommended Action Restart the Internet router. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
•
•
•
•
Error Message%FIA-3-SYNCPLUS : Frame sync moves after reset slot [int] was [chars].\n
Explanation An attempt to synchronize frames has moved after a reset operation was detected. This condition could indicate a hardware fault.
Recommended Action Attempt to reseat the boards. If that does not fix the problem, try swapping out the affected cards. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
•
•
•
•
Error Message%FIA-3-UNEXPECTED : Unexpected interrupt was detected from the [chars] FIA.
Explanation An unexpected interrupt was detected by the FIA hardware. This is an unusual condition that should never occur.
Recommended Action Restart the Internet router. If the message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the following information:
•
•
•
•
FIB Messages
The following are Forwarding Information Base (FIB) messages.
Error Message%FIB-3-ADJFIB_EXPORT : Internal Error - [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-AUTOREPAIR : CEF database auto-repair executed
Explanation The CEF consistency checkers have detected an inconsistent prefix in one of the CEF forwarding databases. The auto-repair function has been started and executed to repair the problem. Details of the prefix can be found by entering the show ip cef inconsistency command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log along with the output of the show ip cef inconsistency command, contact your Cisco technical support representative, and provide the representative with the information you have gathered.
Error Message%FIB-3-FIBBADXDRDATA : Invalid XDR data. [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRHWSBDECODE : HW subblock decode ([chars] / [dec]) - wrong length read.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRIPC : Invalid IPC/XDR. IPC len/XDRs len [dec]/[dec]. IPC at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRLEN : Invalid XDR length. Type/len [dec]/[dec]. XDR at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[dec]. XDR at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRSWSBDECODE : SW subblock decode ([chars] / [dec]) - wrong length read.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRTYPE : Invalid XDR type. Type [dec]. XDR at [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBCBLK : Missing cef table for tableid [dec] during [chars] event
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-4-FIBCBLK2 : Missing cef tableid [dec] during [chars] event for [IP_address][IP_netmask]
Explanation An internal software error has occurred.