-
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
LCGE Messages
The following are Gigabit Ethernet line card (LC) error messages.
Error Message%LCGE-3-SOP_BAD_PACKET : [chars]
Explanation A bad packet caused the TBM to be unstable. The data path was reset.
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.
LCLOG Messages
The following are error messages containing crash information from the logger subsystem for the Internet Router line card.
Error Message%LCLOG-3-BADSTATE : LC logger in bad state (LC=[int],state=[chars],msg=[chars])
Explanation The line card logger subsystem for the line card indicated is not in the state expected for the message it received. This is an unusual condition that should not normally happen. This condition could be due to a dropped MBus message.
Recommended Action Report this defect to your Cisco technical support representative with as much information about the MBus subsystem and the line card logger subsystem as possible, including the output of the show version, show context summary, show context slot n and show tech-support n commands as well as the output of the show tech-support command from the RP.
Error Message%LCLOG-3-BUFSIZEFAIL : Slot [dec], failed buffer size request for [dec] bytes
Explanation There in no buffer left to meet the requested size, or the buffer size requested is greater than the maximum buffer that can be allocated to a LC.
Recommended Action Report this defect to your Cisco technical support representative with as much information about the MBus subsystem and the line card logger subsystem as possible, including the output of the show version, show context summary, show context slot n and show tech-support n commands as well as the output of the show tech-support command from the RP.
Error Message%LCLOG-6-CORRUPT : Logging software on RP has detected a corrupt data
Explanation This is an unusual condition that should never happen.
Recommended Action Report this defect to your Cisco technical support representative with as much information about the MBus subsystem and the line card logger subsystem as possible, including the output of the show version, show context summary, show context slot n and show tech-support n commands as well as the output of the show tech-support command from the RP.
Error Message%LCLOG-3-INVDEV : Invalid line card number in MBUS callback (LC=[int])
Explanation The line card crash information (crashinfo) subsystem on the RP was called from the MBus subsystem with an invalid DEVICE identifier. The DEVICE in this case should be the slot number of the line card, but it was out of range. This is an unusual condition that should not normally happen. It is possible but not likely that the problem is caused by bad MBus hardware somewhere in the system, most likely the RP MBus module.
Recommended Action Report this defect with as much information about the MBus subsystem as possible. Include output from the show version, show context summary, show context slot, and show tech-support commands, as well as output from the show tech-support command from the RP. There is no adverse effect to the RP—it ignores the bad callback and continues. If the problem recurs, reboot the router.
Error Message%LCLOG-3-INVSTATE : LC logger in bad state (LC=[int],state=[chars],msg=[chars])
Explanation The line card logger subsystem for the indicated line card is not in the state expected for the message it received. This is an unusual condition that should not normally happen. It could be caused by a dropped MBus message.
Recommended Action Report this defect with as much information about the MBus subsystem and the line card logger subsystem as possible. Include output from the show version, show context summary, show context slot, and show tech-support commands, as well as output from the show tech-support command from the RP.
Error Message%LCLOG-6-IPCLOG : Logging method via IPC minimum severity changed to [int]
Explanation This is an informational message only. The logging method via IPC minimum severity level was changed.
Recommended Action Informational messages can be disabled by changing logging level.
Error Message%LCLOG-6-LOST : LC logger lost mbus message (LC=[int],state=[chars],msg=[chars])
Explanation The line card logger subsystem for the line card indicated is not in the state expected for the message it received. This condition might be cause by a dropped MBUS message.
Recommended Action Report this defect to your Cisco technical support representative. Provide as much information about the MBUS subsystem and the line card logger subsystem as possible, including the output of a show version, show context summary, show context slot slot-number and show tech-support slot-number commands, as well as the output of the show tech-support command from the RP.
Error Message%LCLOG-3-MSGGIANT : LC log msg larger than max allowed (LC=[int],length=[int])
Explanation The RP part of the line card logger server has received a log start message that is larger than the maximum log buffer allows. This is an unusual condition that should not normally happen.
Recommended Action Report this defect with as much information about the MBus subsystem and the line card logger subsystem as possible. Include output from the show version, show context summary, show context slot, and show tech-support commands, as well as output from the show tech-support command from the RP.
Error Message%LCLOG-3-MSGSEVERITYBAD : Log msg received via IPC has a bad severity (Card=[int],severity=[int])
Explanation The RP part of the logger server has received a log via IPC with a bad severity level This is an unusual condition that should not normally happen.
Recommended Action Report this defect to your Cisco technical support representative with as much information about the MBus subsystem and the line card logger subsystem as possible, including the output of the show version, show context summary, show context slot n and show tech-support n commands as well as the output of the show tech-support command from the RP.
Error Message%LCLOG-3-MSGTOOBIG : LC log msg longer than expected (LC=[int],len=[int],exp=[int])
Explanation The RP part of the line card logger server has received more text for a message than the start message indicated. This is an unusual condition that should not normally happen.
Recommended Action Report this defect with as much information about the MBus subsystem and the line card logger subsystem as possible. Include output from the show version, show context summary, show context slot, and show tech-support commands, as well as output from the show tech-support command from the RP.
Error Message%LCLOG-3-OVERFLOW : LC log msg longer than msg buffer (LC=[int],len=[int],max=[int])
Explanation The RP part of the line card logger server has received more text for a message than will fit in the message log buffer. This is an unusual condition that should not normally happen.
Recommended Action Report this defect with as much information about the MBus subsystem and the line card logger subsystem as possible. Include output from the show version, show context summary, show context slot, and show tech-support commands, as well as output from the show tech-support command from the RP.
Error Message%LCLOG-3-SLOTRESET : LC log msg truncated due to card removed/reset/reloaded (LC=[int])
Explanation The RP part of the line card logger server had received only part of the text for a message when the sender became nonoperational. The partial message will be displayed. This message is informational. Display of a partial message when the sender is no longer operational gives some extra diagnostic information.
Recommended Action Look at any other messages and assess the situation that caused the reset or reload of the card. If the problem persists, report this defect with as much information about the line card logger subsystem as possible. Include output from the show version, show context summary, show context slot, and show tech-support commands, as well as output from the show tech-support command from the RP.
Error Message%LCLOG-3-UNKNOWNSTATE : LC logger in unknown state (LC=[int],state=[chars],msg=[chars])
Explanation The line card logger subsystem for the line card specified in the error message is not in the state expected for the message it received. This is an unusual condition that should not normally happen. It could be due to a dropped MBus message.
Recommended Action Report this defect to your Cisco technical support representative with as much information about the MBus subsystem and the line card logger subsystem as possible, including the output of the show version, show context summary, show context slot n and show tech-support n commands as well as the output of the show tech-support command from the RP.
LCOC12_CH_DS3 Messages
The following are Internet Router OC12-channelized-to-D3 line card messages.
Error Message%LCOC12_CH_DS3-1-ALLOCFAIL : OC12 [dec]/[dec][chars] allocation failure
Explanation Memory could not be allocated for the OC12-channelized-to-DS3 controller or channel.
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%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 correct clock configuration copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative, and provide the representative with the information you have gathered.
Error Message%LCOC12_CH_DS3-3-FPGAINIT : Error initializing FPGA; [chars]
Explanation A failure occurred while the line card hardware was being initialized.
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%LCOC12_CH_DS3-1-INITFAIL : OC12 [dec]/[dec] hardware initialization failure
Explanation The OC12-channelized-to-DS3 line card hardware initialization has failed.
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%LCOC12_CH_DS3-3-NOHWIDB : OC12 [dec]/[dec][chars] hardware IDB is missing
Explanation The OC12-channelized-to-DS3 controller or channel hardware IDB is missing.
Recommended Action Copy the 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%LCOC12_CH_DS3-3-NOSUBBLOCK : OC12 [dec]/[dec][chars] sub-block is missing
Explanation The OC12-channelized-to-DS3 controller or channel hardware IDB associated sub-block is missing.
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.
LCPLIM Messages
The following are physical layer interface module messages.
Error Message%LCPLIM-2-BADSSB : NULL Sonet Block Is found, idb incorrect or Null, [hex]
Explanation A null Sonet block was found, possibly because of an incorrect or null IDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the execute-on slot (x) show controller 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.
LCPOS Messages
The following are Packet over SONET (PoS) line card messages.
Error Message%LCPOS-3-4302 : Runaway Skystone 4302 framer [dec] Tx [chars] counter, byte=[dec], pkt=[dec].
Explanation 4302 hardware errors have 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%LCPOS-3-APS : APS([dec]) [chars]
Explanation The RP dead man timer has expired on the line card causing the line card to send LAIS to the far-end.
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%LCPOS-3-COAPSTHROTTLE : POS interface [dec]/[dec]: [chars]
Explanation Excessive COAPS interrupts have been ignored.
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%LCPOS-3-OC192_SURF : SURF Int:[chars]
Explanation An OC-192 line card SURF operational 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%LCPOS-3-OC192_U2 : U2 Int:[chars]
Explanation An OC-192 line card U2 operational 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%LCPOS-3-OC48_SURF : SURF Int:[chars]
Explanation An OC-48 line card Framer operational 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%LCPOS-3-PHAD : Phad asic error: [chars] [chars]=[hex], status:[chars]=[hex]
Explanation Phad hardware errors have 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%LCPOS-3-SOP : [chars]. Source=[hex] [chars], halt_minor0=[hex] [chars]
Explanation SOP hardware errors have 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%LCPOS-3-ZEUS_FRAMER : Zeus ASIC framer error: [chars] [chars]=[hex], status:[chars]=[hex]
Explanation Hardware errors have occurred on the Zeus ASIC framer hardware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the slot where the Zeus ASIC resides. 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%LCPOS-3-ZEUS_PHAD : Zeus ASIC PHAD error: [chars], [chars], intr=[hex]
Explanation Hardware errors have occurred on the Zeus ASIC PHAD.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the slot where the Zeus ASIC resides. 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.
LCSDCC Messages
The following are line card SDCC messages.
Error Message%LCSDCC-3-NOMEMORY : [chars]
Explanation The line card was unable to obtain memory to receive or transmit packets.
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.
LC_MOD48 Messages
Error Message%LC_MOD48-1-FPGA : FPGA [chars] [chars]
Explanation Load FPGA failed. This is the problem of hardware or version of software may be wrong.
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.
Error Message%LC_MOD48-1-FPGA_FILE : FPGA [chars] ID in file is wrong: [hex] instead of [hex]
Explanation Load FPGA failed. The software bundle is wrong.
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.
Error Message%LC_MOD48-1-FPGA_IMAGE_DOWNLOAD_FAILURE : [chars] FPGA image download failed
Explanation downloading the image that should be used to program the fpga 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.
Error Message%LC_MOD48-1-FPGA_VER : FPGA [chars]: version is wrong ([hex] [hex] / * [hex])
Explanation Load FPGA failed. Software or hardware problem.
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.
Error Message%LC_MOD48-3-MOD48_ERROR_INTERRUPT : Interrupt from [chars][dec], int_stat=[hex], int_mask=[hex]
Explanation Mod48 got interrupt from a HW module.
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.
Error Message%LC_MOD48-3-MOD48_INVALID_PARAMETER : Mod48 invalid parameter. Name:[chars] , value:[dec]
Explanation Mod48 invalid parameter.
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.
Error Message%LC_MOD48-3-MOD48_RESOURCE_ALLOC_ERROR : Failed to allocate [chars].
Explanation Could not allocate the required resource.
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.
Error Message%LC_MOD48-3-MOD48_RESOURCE_ALREADY_IN_USE : Requested resource is already in use: [chars] , [dec]
Explanation Could not allocate the required resource because it was already used.
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.
Error Message%LC_MOD48-3-MOD48_UNEXPECTED_VALUE : Mod48 unexpected value. Name:[chars] , value:[dec]
Explanation Mod48 unexpected parameter.
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.
Error Message%LC_MOD48-3-SPAB_CORE_INT_ERR : Spab raised an interrupt for bay [dec] SPI core, int_status=[hex]
Explanation Mod48 Spab fpga raised an interrupt indicating an errornous state in one of the SPI cores.
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.
Error Message%LC_MOD48-3-SPAB_INIT_FAILURE : Mod48 Spab ([dec]) fpga failed to initialize ([chars])
Explanation Mod48 Spab fpga failed to initialize.
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.
Error Message%LC_MOD48-3-SPAB_INT_ERR : Spab ([dec]) raised an interrupt, int_status=[hex]
Explanation Mod48 Spab fpga raised an interrupt indicating an errornous state
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.
Error Message%LC_MOD48-3-SPAB_INVALID_PARAMETER : Mod48 Spab fpga invalid parameter. Name:[chars] , value:[dec]
Explanation Mod48 Spab invalid parameter.
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.
Error Message%LC_MOD48-3-SPAB_RESET_FAILURE : Mod48 Spab fpga failed to reset
Explanation Mod48 Spab fpga failed to reset.
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.
Error Message%LC_MOD48-3-SPAB_SPI_INIT_FAILURE : Mod48 Spab fpga failed to initialize SPI channel on bay [dec]:
Explanation Mod48 Spab fpga failed to initialize SPI channel.
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.
Error Message%LC_MOD48-3-SPAB_SPI_SYNC_FAILURE : Mod48 Spab fpga failed sync SPI bus. bay [dec] [chars]
Explanation Mod48 Spab fpga failed sync SPI bus.
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.
Error Message%LC_MOD48-3-SPAG_BUSY : Mod48 Spaghetti fpga busy. Module:[dec]
Explanation Mod48 Spaghetti indirect access busy flag doesnt reset.
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.
Error Message%LC_MOD48-3-SPAG_INIT_FAILURE : Mod48 Spaghetti fpga failed to initialize ([chars])
Explanation Mod48 Spaghetti fpga failed to initialize.
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.
Error Message%LC_MOD48-3-SPAG_INT_ERR : Spaghetti raised an interrupt block:[chars], int_status=[hex]
Explanation Mod48 Spaghetti fpga raised an interrupt indicating an error.
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.
Error Message%LC_MOD48-3-SPAG_INVALID_PARAMETER : Mod48 Spaghetti fpga invalid parameter. Name:[chars] , value:[dec]
Explanation Mod48 Spaghetti invalid parameter.
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.
Error Message%LC_MOD48-3-SPAG_MULTIPLE_BAY_EFC_BP_MAPPED_TO_CONGA_PORT : Found EFC channels from 2 different bays mapped to the same Conga port. existing map {bay=[dec], efc_chn=[dec]}, requested map {bay=[dec], efc_chn=[dec]}
Explanation Found EFC channels from 2 different bays mapped to the same Conga port.
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. .
Error Message%LC_MOD48-3-SPAG_QDR_PHASE_SHIFT : [chars]
Explanation Shows the Phase shift of SPAGHETTI fpga.
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.
LC_SFP Messages
The following are Cisco LC SFP diagnostics messages.
Error Message%LC_SFP-4-SFP_BAD_MODULE : Bad SFP module in port [int][chars]
Explanation The SFP module is faulty.
Recommended Action Check the SFP module.
Error Message%LC_SFP-4-SFP_DUP_MODULE : Duplicate S/N of SFP module detected in port [int][chars]
Explanation The SFP module is faulty.
Recommended Action Check the SFP module.
Error Message%LC_SFP-4-SFP_EVENT_INS : SFP Module Inserted: port [int]
Explanation An SFP module has been inserted.
Recommended Action If an SFP module has been inserted, no action is required. Otherwise, check the SFP module.
Error Message%LC_SFP-4-SFP_EVENT_MISSING : SFP Module Missing: port [int]
Explanation The system is reporting that the SFP module is missing.
Recommended Action Check the SFP module.
Error Message%LC_SFP-4-SFP_EVENT_REM : SFP Module Removed: port [int]
Explanation The SFP module has been removed.
Recommended Action If the SFP module was removed, no action is required. Otherwise, check the SFP module.
Error Message%LC_SFP-4-SFP_EVENT_TX_FAULT : TX FAULT signal [chars] on port [int]
Explanation An SFP module has a "TX FAULT" signal.
Recommended Action Check the SFP module.
Error Message%LC_SFP-4-SFP_NOT_COMPLIANT : Wrong SFP module compliance in port [int]
Explanation The SFP module is of the wrong compliance.
Recommended Action Check the SFP module.
Error Message%LC_SFP-4-SFP_NOT_READY : SFP: Interface [chars][int]/[int] can't come up; SFP modules are not ready
Explanation The SFP modules are not ready.
Recommended Action Check the SFP module.
Error Message%LC_SFP-2-SFP_RX_POWER_HI_ALARM : RX power high alarm
Explanation The Rx power has exceeded the high alarm level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-4-SFP_RX_POWER_HI_WARN : RX power high warning
Explanation The Rx power has exceeded the high warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_RX_POWER_LO_ALARM : RX power low alarm
Explanation The Rx power is below the high alarm level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-4-SFP_RX_POWER_LO_WARN : RX power low warning
Explanation The Rx power is below the high warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_TEMP_HI_ALARM : Temperature high alarm
Explanation The internal temperature has exceeded the high alarm level.
Recommended Action Replace the SFP.
Error Message%LC_SFP-4-SFP_TEMP_HI_WARN : Temperature high warning
Explanation The internal temperature has exceeded the high warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_TEMP_LO_ALARM : Temperature low alarm
Explanation The internal temperature is below the low alarm level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-4-SFP_TEMP_LO_WARN : Temperature low warning
Explanation The internal temperature is below the low warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_TX_BIAS_HI_ALARM : TX bias high alarm
Explanation The Tx bias current has exceeded the high alarm level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-4-SFP_TX_BIAS_HI_WARN : TX bias high warning
Explanation The Tx bias current has exceeded the high warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_TX_BIAS_LO_ALARM : TX bias low alarm
Explanation The Tx bias current is below the low alarm level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-4-SFP_TX_BIAS_LO_WARN : TX bias low warning
Explanation The Tx bias current is below the low warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_TX_POWER_HI_ALARM : TX power high alarm
Explanation The Tx output power has exceeded the high alarm level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-4-SFP_TX_POWER_HI_WARN : TX power high warning
Explanation The Tx output power has exceeded the high warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_TX_POWER_LO_ALARM : TX power low alarm
Explanation The Tx output power is below the low alarm level.
Recommended Action Replace the SFP.
Error Message%LC_SFP-4-SFP_TX_POWER_LO_WARN : TX power low warning
Explanation The Tx output power is below the low warning level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-2-SFP_VOLT_HI_ALARM : Vcc high alarm
Explanation The supply voltage has exceeded the high alarm level.
Recommended Action Replace the SFP.
Error Message%LC_SFP-4-SFP_VOLT_HI_WARN : Vcc high warning
Explanation The supply voltage has exceeded the high warning level.
Recommended Action Replace the SFP.
Error Message%LC_SFP-2-SFP_VOLT_LO_ALARM : Vcc low alarm
Explanation The supply voltage is below the low alarm level.
Recommended Action Replace the SFP module.
Error Message%LC_SFP-4-SFP_VOLT_LO_WARN : Vcc low warning
Explanation The supply voltage is below the low warning level.
Recommended Action Replace the SFP module.
LC_SSRP Messages
The following are Internet Router SSRP line card messages.
Error Message%LC_SSRP-3-BMAPAR : [chars] SSRP, [chars]. BMA_DATA[3:0]=[hex]. (src=[hex], det1=[hex], det2=[hex])
Explanation A parity error has occurred on the SSRP ASIC BMA engine.
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%LC_SSRP-3-CAM : LC_SSRP([dec]/[dec]), CAM overflowed with addresses
Explanation A CAM 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%LC_SSRP-3-DFRAC : DFRAC [int] ASIC bus error: BUS error status = [hex]
Explanation DFRAC bus 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 in the error message. If diagnostics pass, contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%LC_SSRP-3-FILTER : [chars] \n
Explanation An internal error has occurred in the address filter software.
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%LC_SSRP-1-INITFAIL : LC_SSRP([dec]/[dec]), initialization timeout failure
Explanation LC SSRP ASIC and Framer initialization have failed.
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%LC_SSRP-1-LC_ASIC_ERR_INT : Hardware Error detected (Asic: [chars], status: [hex], seq: [dec])
Explanation A ASIC error has been detected on the line card.
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 in which the error occurred. If the card passes the diagnostic tests, 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.
Error Message%LC_SSRP-3-LC_NULL_ADDRESS : Malloc failure or dereferencing of a null pointer
Explanation A software error occurred; either a memory allocation failure or an attempt to use an un-initialized pointer. Some functionality may have been damaged.
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 diagnostics pass, 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%LC_SSRP-3-MACFPGALOCK : MAC FPGA has locked up and is being reset
Explanation The software is unable to access the MAC FPGA registers because the FPGA has locked up. An automatic reset of the FPGA followed by a line card reset should bring the SRP interface back into operation. If the problem persists, it could indicate fault with the line card hardware, which would require line card replacement.
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%LC_SSRP-6-MACFPGAVER : Download MAC FPGA version [hex], was [hex]
Explanation The MAC FPGA component on the SRP line card is normally programmed only on power cycle. When Cisco IOS starts up on the line card, it checks the version number of the MAC FPGA program. If for any reason the instance of Cisco IOS does not support that version of the MAC FPGA, the FPGA will be reprogrammed accordingly.
Recommended Action No action is required.
Error Message%LC_SSRP-1-QMAC_LOAD : NULL
Explanation An error has occurred while the QMAC FPGA was being loaded.
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 in which the error occurred. If the card passes the diagnostic tests, 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.
Error Message%LC_SSRP-3-QUATTRO : [chars] Quattro ASIC bus error: BUS error status = [hex]
Explanation Quattro bus 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 in the error message. If diagnostics pass, contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%LC_SSRP-3-QUATTRO_RX : RX-Quattro asic error: [chars] [chars]=[hex], status:[chars]=[hex]
Explanation RX-Quattro 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 in the error message. If diagnostics pass, contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%LC_SSRP-3-QUATTRO_TX : TX-Quattro asic error: [chars] [chars]=[hex], status:[chars]=[hex]
Explanation Tx-Quattro 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 in the error message. If diagnostics pass, contact your Cisco technical support representative and provide