-
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
FR Messages
The following are Frame Relay messages.
Error Message%FR-3-BQ_DEQ_ERR : fr_bq_proc: unknown packet on broadcast queue, packet dropped!
Explanation An invalid packet has been detected on the Frame Relay broadcast queue, and the packet has been dropped.
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%FR-3-BQ_DEQ_PTR : fr_br_proc: hdr-[hex] size-[dec] dlci-[hex] [hex] [hex]
Explanation An invalid datagram start has been detected on the Frame Relay broadcast queue, and the packet has been dropped.
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%FR-3-BQ_ENQ_ERR : fr_oqueue: Invalid datagramstart [hex] [hex], pak dropped
Explanation A broadcast packet with an invalid datagram start has been detected in the Frame Relay output queue, and the packet has been dropped.
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%FR-5-CONVERT_ROUTE : Converting route pair to connect
Explanation A pair of Frame Relay routes are being converted to connections.
Recommended Action No action is required.
Error Message%FR-3-FRTSZEROCIR : FRTS: attempt to configure zero CIR
Explanation It should not be possible to configure a zero CIR. To do so would prevent data transmission on the VC.
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%FR-3-MAP_DELETE_ERROR : [chars]
Explanation An error occurred while a Frame Relay map was being deleted.
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%FM-3-V6_MERGE_ON_RP : [chars] V6 acls cannot be merged on RP. Turn off RP merge flag and try again
Explanation A V6 ACL merge 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.
FR_ADJ Messages
The following are Frame Relay Adjacency messages.
Error Message%FR_ADJ-3-ADD_MEMBER : Unable to add adjacency for vc-bundle [chars] member [dec]
Explanation An error occurred while a VC bundle member adjacency was being added.
Recommended Action Delete the VC bundle, and reconfigure the bundle on the same interface.
Error Message%FR_ADJ-3-ARRAY_FULL : Unable to setup adjacencies for vc-bundle [chars]
Explanation An error occurred while VC bundle adjacencies were being set up.
Recommended Action Attempt to shut down the subinterface on which the VC bundle is configured. After waiting approximately one minute, verify that the adjacencies on the subinterface have been deleted. Reconfigure the VC bundle.
%FR_ADJ-3-ARRAY_INDEX_ERROR : Adjacency array index is incorrect for vc-bundle [chars] member [dec]
Explanation An error occurred while VC bundle adjacencies were being set up.
Recommended Action Attempt to shut down the subinterface on which the VC bundle is configured. After waiting approximately one minute, verify that the adjacencies on the subinterface have been deleted. Reconfigure the VC bundle.
FR_EA Messages
The following are Frame Relay messages.
Error Message%FR_EA-3-RADIXTREE : Radix tree problem
Explanation An error was detected in the DLCI radix tree.
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%FR_EA-3-USECOUNT : PVC use count incorrect [dec]
Explanation An attempt has been made to delete a PVC that is in use.
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.
FR_RP Messages
The following are Frame Relay RP messages.
Error Message%FR_RP-3-IPC_STATS_INVALID_DLCI : Error processing IPC msg - msg type [chars]
Explanation An error occurred while an IPC statistics message was being processed.
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%FR_RP-3-IPC_STATS_INVALID_INTERFACE : Error processing IPC msg - msg type [chars]
Explanation An error occurred while an IPC statistics message was being processed.
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%FR_RP-3-IPC_STATS_INVALID_MSG : Error processing IPC msg - msg type [chars]
Explanation An error occurred while an IPC statistics message was being processed.
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%FR_RP-3-IPC_STATS_MISC : Error processing IPC msg - [chars]
Explanation An error occurred while an IPC statistics message was being processed.
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.
FR_VCB Messages
The following are Frame Relay VC messages.
Error Message%FR_VCB-3-BUMPING : Bumping error - vcb [chars] - [chars]
Explanation An error occurred while traffic in a VC bundle was being bumped.
Recommended Action Reconfigure the VC bundle to avoid the bumping condition.
Error Message%FR_VCB-3-CONFIG : Configuration error - vcb [chars] - [chars]
Explanation An error occurred while a VC bundle configuration was being interpreted.
Recommended Action Attempt to reconfigure the VC bundle.
Error Message%FR_VCB-3-FIBSW_MISSING_TABLE_ENTRY : FIB switching error - vc-bundle [chars]
Explanation An error occurred while the FIB was switching packets across the VC bundle.
Recommended Action Delete the VC bundle, and employ a PVC to substitute for the VC bundle.
Error Message%FR_VCB-3-PROCESS_SWITCHING : Switching error - vcb [chars] - [chars]
Explanation An error occurred while the system was switching packets across the VC bundle.
Recommended Action Delete the VC bundle and employ a PVC to substitute for the VC bundle.
Error Message%FR_VCB-5-UPDOWN : FR VC-Bundle [chars] changed state to [chars]
Explanation The state of a Frame Relay VC bundle has changed from inactive to active.
Recommended Action No action is required.
FR_VIP Messages
The following are Frame Relay VIP messages.
Error Message%FR_VIP-5-FLUSH : Flushing frame relay state
Explanation The Frame Relay state is being cleared on the VIP card.
Recommended Action No action is required.
Error Message%FR_VIP-3-INCONSISTENT : Invalid state on VIP: DLCI [dec]: Slot [dec]: Error code [dec]
Explanation An error occurred while the Frame Relay state on the VIP was being processed.
Recommended Action Enter the shutdown and no shutdown commands on the Frame Relay-encapsulated interface for the slot that is reporting the problem.
Error Message%FR_VIP-3-MISSING_STATE : Missing state on VIP: DLCI [dec]: Slot [dec]
Explanation An error occurred while an IPC statistics unit was being prepared.
Recommended Action Enter the shutdown and no shutdown commands on the Frame Relay-encapsulated interface for the slot that is reporting the problem.
Error Message%FR_VIP-3-SWITCHING : [chars] DLCI [dec]: [chars]
Explanation An error was detected a packet was being switched on the VIP.
Recommended Action Enter the shutdown and no shutdown commands to shut down and restart the interface. Unconfigure, then re-configure, the interface. If this message recurs, 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.
FX1000 Messages
The following are Gigabit Ethernet controller messages.
Error Message%FX1000-3-ERRINT : [chars], error interrupt, csr_STATUS=[hex]
Explanation The Gigabit Ethernet controller has signaled an error condition.
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%FX1000-1-INITFAIL_NOMEM : [chars], initialization failed, no buffer memory
Explanation The Gigabit Ethernet port initialization failed because of an insufficient memory condition.
Recommended Action Upgrade the GEIP with a larger memory model. If this message recurs, 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%FX1000-5-LOSTCARR : [chars] cable/transceiver problem?
Explanation The Gigabit Ethernet port has detected a link failure, meaning that it is no longer receiving signals from the LAN. This condition can be caused by disconnected Gigabit Ethernet cabling, a transceiver (GBIC) failure, or a shutdown of the remote end.
Recommended Action Check your Gigabit Ethernet wiring and port adapter. If this message recurs, 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%FX1000-2-NOISL : Interface [chars] does not support ISL
Explanation The ISL protocol is not supported on the hardware on which the specified interface is configured.
Recommended Action No action is required.
Error Message%FX1000-3-NOTFX1000 : slot[[dec],[dec]] detects unknown PCI device (id=[hex])
Explanation The GE PA does not contain a Gigabit controller chip.
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%FX1000-3-TOOBIG : [chars], packet too big ([dec]), src [enet], dst [enet]
Explanation The interface has detected a packet larger the predefined MTU size.
Recommended Action Check the MTU setting of the other station. Otherwise, no action is required.
GBIC_SECURITY Messages
The following are GBIC security messages.
Error Message%GBIC_SECURITY-4-GBIC_INTERR : Internal error occurred in setup for GBIC interface [chars]
Explanation The system could not allocate resources, or some other problem occurred, in the setup for the specified GBIC interface.
Recommended Action Reload the system. If this message recurs, 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.
GBIC_SECURITY_CRYPT Messages
The following are GBIC security serial EEPROM verification messages.
Error Message%GBIC_SECURITY_CRYPT-4-ID_MISMATCH : Identification check failed for GBIC in port [dec]
Explanation The GBIC was identified as a Cisco GBIC, but the system was unable to verify its identity.
Recommended Action Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Otherwise, verify that the GBIC was obtained from Cisco or from a supported vendor.
Error Message%GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR : GBIC in port [dec] manufactured by an unrecognized vendor
Explanation The GBIC was identified as a Cisco GBIC, but the system was unable to match its manufacturer with one on the known list of Cisco GBIC vendors.
Recommended Action Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required.
Error Message%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR : GBIC in port [dec] has bad crc
Explanation The GBIC was identified as a Cisco GBIC, but it does not have a valid CRC in the EEPROM data.
Recommended Action Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Even if the GBIC is unrecognized by the system, the GBIC may still operate properly but might have limited functionality.
GBIC_SECURITY_UNIQUE Messages
The following are GBIC security uniqueness verification messages.
Error Message%GBIC_SECURITY_UNIQUE-3-DUPLICATE_GBIC : GBIC interface [dec]/[dec] is a duplicate of GBIC interface [dec]/[dec]
Explanation The GBIC was identified as a Cisco GBIC, but its vendor ID and serial number match that of another interface on the system.
Recommended Action Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor.
Error Message%GBIC_SECURITY_UNIQUE-4-DUPLICATE_SN : GBIC interface [dec]/[dec] has the same serial number as another GBIC interface
Explanation The GBIC was identified as a Cisco GBIC, but its serial number matches that of another interface on the system.
Recommended Action Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor.
GE4_DM Messages
The following are GE4 DM messages.
Error Message%GE4_DM-3-ERROR : [chars]
Explanation An internal 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 that 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.
GE4_L2PROTO Messages
The following are GE4 Layer 2 protocol messages.
Error Message%GE4_L2PROTO-3-ERROR : [chars]
Explanation An internal error has occurred. The command could not be configured.
Recommended Action Reload the line card. If this message recurs, 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%GE4_L2PROTO-3-MEM_ERROR : [chars]
Explanation A memory resource error has occurred.
Recommended Action Retry the operation. If this message recurs, reload the line card. If you require further assistance, 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%GE4_L2PROTO-3-TMGR : [chars]
Explanation An inconsistency has occurred between the TCAM manager and driver structures.
Recommended Action If this message recurs, reload the line card. If the error persists, 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.
GE4_L2_SRAM Messages
The following are GE4 Layer 2 SRAM messages.
Error Message%GE4_L2_SRAM-4-MEM_ERR : [chars]
Explanation A memory resource error has occurred.The parity error recovery mechanism for statistics could not be started. If an SRAM parity error involving statistics occurs on the line card, some counters may provide incorrect data
Recommended Action Reload the microcode on the line card to attempt to solve the problem. If this message recurs, 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%GE4_L2_SRAM-3-POLICY_WRITE : [chars]. sram addr:[hex] sram type:[hex]
Explanation An internal PLIM error has occurred. An SRAM single-bit parity error could not be corrected.
Recommended Action Reload the line card to attempt to solve the problem. If this message recurs, 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.
GE4_L2_TCAM Messages
The following are GE4 Layer 2 TCAM messages.
Error Message%GE4_L2_TCAM-3-TCAM_DRV : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
GE4_L2_TCAM_SCAN Messages
The following are GE4 Layer 2 TCAM scan messages.
Error Message%GE4_L2_TCAM_SCAN-4-TCAM_REGION : [chars] region: [dec] index [dec]
Explanation This message provide information about the TCAM region.
Recommended Action No action is required.
Error Message%GE4_L2_TCAM_SCAN-4-TCAM_SCAN_HANDLE : [chars]: [dec]
Explanation This message provide information about the TCAM scan handle.
Recommended Action No action is required.
GE4_L2_VMR Messages
The following are GE4 Layer 2 VMR messages.
Error Message%GE4_L2_VMR-3-MALLOC_FAIL : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
GE4_VLAN Messages
The following are GE4 VLAN messages.
Error Message%GE4_VLAN-3-ERROR : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
GEN7 Messages
The following are GEN7 messages.
Error Message%GEN7-4-uRPF : \n[chars] uRPF [chars] since TFIB [chars]
Explanation The TFIB has become operational on an E4P card, and uRPF has been disabled.
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.
GEN7_ACL Messages
The following are Gen7 ACL messages.
Error Message%GEN7_ACL-3-ADD_FEAT_FAILURE : Adding feature [chars] to label [dec] failed.
Explanation This is an invalid label, an empty label list element was indexed by a label, or this is not a new feature.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-DFLT_ENTRY_INSERT_FAIL : [chars], [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-ERROR : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-GET_ACLSB_FAIL : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-L4OP_ALLOC_FAIL : ACE# [dec]. L4op allocation failed. There are too many l4 operations in the ACL. All traffic hitting the ACL will be punt to CPU.
Explanation When converting an ACL to VMR, there is no memory to allocate a l4 operation, or the number of allocated l4 operations exceeds the upper limit as defined by MAX_FM_L4OP_MAPS.
Recommended Action Check if there is a memory leak. Reduce the number of unique l4 operations of the ACL.
Error Message%GEN7_ACL-3-NOT_SUPPORT : Hardware doesn't support '[chars]' in ACL. All traffic hitting the rule will be processed in CPU. Performance will be severely degraded for those traffic.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-NOT_SUPPORT : There are unsupported rules in ACLs due to mulitple features configured on this interface. If you are using deny rules with protocols other than TCP or UDP, please try to change them to permit rules by enumerating supported cases. protocol: [dec].
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-PROT_OVERRUN : There are too many protocols in the ACL. Protocol [dec] will be treated as IP protocol.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-SET_LABEL_STH_FAILURE : Set [chars] for label [dec] failed.
Explanation This is an invalid label, or an empty label list element has been indexed by label.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-TCAM_DELETE_FAIL : ACL list number [dec], label [dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%GEN7_ACL-3-TCAM_FAIL : Write label: [dec], direction: [chars] to TCAM error: [chars]. Performance will be seriously degraded for traffic hitting ACL rules beyond hardware capability.
Explanation Writing a block of VMRs to the TCAM has failed. None of the VMRs can be written.
Recommended Action Unavailable.
GEN7_VMR Messages
The following are Gen7 VMR messages.
Error Message%GEN7_VMR-3-MALLOC_FAIL : [chars], [chars]
Explanation Unavailable.
Recommended Action Unavailable.
GENERAL Messages
The following are general information messages.
Error Message%GENERAL-2-CRITEVENT : [chars]
Explanation A critical 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%GENERAL-3-EREVENT : [chars]
Explanation This is a general error to be used for sanity tests.
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%GENERAL-3-EREVENT1 : [chars] [hex]
Explanation This is a general error to be used for sanity tests
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%GENERAL-3-EREVENTIP : [chars] [IP_address]
Explanation This is a general error to be used for sanity tests.
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%GRP-3-HAREGFAIL : Failed to register HA Application '[chars]'\n
Explanation The HA application specified in the error message failed to register with the GRP HA application infrastructure.
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%GENERAL-3-HWCEF_CHUNK : Failed to alloc Mtrie HW mnode from chunk [chars] for [IP_address]/[dec]
Explanation An attempt to allocate memory for a hardware mnode 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%GENERAL-3-HWCEF_FIB_ROOT : Failed to alloc Mtrie HW root for [chars] fib
Explanation An attempt to allocate a hardware mnode root 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%GENERAL-3-HWCEF_MNODE : Failed to alloc Mtrie HW mnode for [IP_address]/[dec] at level [dec]
Explanation A attempt to allocate a hardware mnode structure 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%GENERAL-3-HW_IPV6CEF_CHUNK : Failed to alloc Mtrie HW mnode from chunk [chars] forUnrecognized format ` %P'/[dec]
Explanation An attempt to allocate memory for a hardware multicast node 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%GENERAL-3-HW_IPV6CEF_FIB_ROOT : Failed to alloc Mtrie HW root for tableid [dec]
Explanation An attempt to allocate a hardware multicast node root 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%GENERAL-3-HW_IPV6CEF_MNODE : Failed to alloc Mtrie HW mnode forUnrecognized format ` %P'/[dec] from block [dec]
Explanation An attempt to allocate a hardware multicast node structure 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%GENERAL-3-HW_IPV6CEF_MTRIECORRUPT : Could not add prefiUnrecognized format `x%P'/[dec] flags=[dec] at level [dec]
Explanation An internal software error occurred in the PXF mtrie table.
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%GENERAL-3-HW_VCCI_FAIL : Maximum number of interfaces reached, [chars] is not functional in PXF
Explanation A PXF resource allocation 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%GENERAL-6-INFOEVENT : [chars]
Explanation This is an informational message.
Recommended Action No action is required.
Error Message%GENERAL-5-NOTEVENT : [chars]
Explanation This is a notification message.
Recommended Action No action is required.
GE_VMR Messages
The following are GE_VMR messages.
Error Message%GE_VMR-3-MALLOC_FAIL : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
GLCFLOW Messages
The following are flow cache messages.
Error Message%GLCFLOW-3-BADFLOW : Bad value (null) for flow.
Explanation An invalid flow was returned by the flow cache.
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.
GLCFR Messages
The following are Internet Router line card Frame Relay messages.
Error Message%GLCFR-3-DLCIRANGE : [chars]([chars]) bad dlci value [int]
Explanation The GLC Frame Relay support code has received a bad DLCI number.
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%GLCFR-3-ERROR : [chars]
Explanation An error has occurred in the line card Frame Relay 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.
GLCROMMON Messages
The following are Internet Router line card ROM Monitor (RMMON) messages.
Error Message%GLCROMMON-6-NO_UPGRADE : Linecard ROM monitor is not upgraded, version in flash ([hex].[hex]) is >= version in IOS ([hex].[hex])
Explanation The line card ROM monitor was not upgraded because the line card boot ROM monitor version in the Flash memory is greater than the ROM monitor version in the Cisco IOS image.
Recommended Action Ensure that the the ROM monitor version in the Cisco IOS image is greater than the line card boot ROM monitor version in the Flash memory.
GLCSPA Messages
The following are Shared Port Adapter messages on a GSR LC.
Error Message%GLCSPA-3-BUS_ERROR : subslot [dec]: (error_status = [hex])
Explanation A reading or writting transaction on the SPA busfailed to complete succesfully or a bus parity error has been detected. This could be a transient error if the error does not repeat itself.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.Error Message%GLCSPA-3-CONTROLLER_CREATION : subSlot [dec] port [dec]
Explanation Failed to create a controller. This may be due to insufficient memory.
Recommended Action Reduce system activity to ease the memory demand or upgrade to a larger memory configuration.
Error Message%GLCSPA-3-ERROR : NULL
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.Error Message%GLCSPA-3-HOST_LC : Error: [chars]
Explanation The specified error happened on the linecard that is hosting SPAs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.Error Message%GLCSPA-3-HW_ERROR : subSlot [dec], spaType [hex]: [chars]
Explanation Hardware error is detected on the SPA.
Recommended Action Corrective action has been taken when the hardware error is detected. If the error does not repeat, then no further action is required; otherwise, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.Error Message%GLCSPA-3-INTERFACE_CREATION : subSlot [dec] port [dec] vc [dec]. [chars].
Explanation Failed to create an interface. This may be due to insufficient memory.
Recommended Action Reduce system activity to ease the memory demand or upgrade to a larger memory configuration.
Error Message%GLCSPA-3-INTERFACE_ERROR : [chars]. ([chars], port [dec], vc [dec], ifType [hex])
Explanation The specified error happened on the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.Error Message%GLCSPA-4-IPC_CHAN_CREATION : [chars]: failed to create an IPC channel.
This may happen if there are too many (sub-)interfaces provisioned
on the linecard and resource exhaustion happens.
Explanation This may happen due to a software error or resource exhaustion as a
result of too many (sub-)interfaces being provisioned on the LCRecommended Action Enter the command exec slot <slot_num> show control frfab queue to check whether there is any free TX queue left. If not, un-provision some interfaces from the line card and reload the SPA. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.Error Message%GLCSPA-3-ISR_RC_ERROR : ISR return code out of range. rc=[dec]
Explanation The ISR error return code is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.Error Message%GLCSPA-3-JTAG_NOT_SUPPORTED : JTAG programming is not supported on the SPA carrier