-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
FECPM Messages
The following are Fast Ethernet (FE) Combination Port Module (CPM) device driver messages.
Error Message%FECPM-3-BSCHUNT : BSC HUNT cmd for int [chars] failed
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 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%FECPM-3-INVALID_CLOCKRATE : Unsupported clock rate req on int [chars] - index [dec]
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 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%FECPM-3-OWNERR : Buffer owner ship error on int [chars], pak=[hex]
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 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%FECPM-2-SCCFAIL : Init of SCC[dec] for int [chars] failed to do [chars]
Explanation The software failed to initialize or restart an SCC process for a serial interface on the FECPM.
Recommended Action Clear the serial 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.
Error Message%FECPM-3-SCCRESET : SCC reset for int [chars] at [chars] failed
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 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%FECPM-5-TOOBIG : On int [chars], tx pak is [dec] bytes
Explanation A packet greater than the assigned MTU of this serial interface was queued for transmission.
Recommended Action The system should recover. 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%FECPM-5-TOOSMALL : On int [chars], tx pak size is [dec] bytes
Explanation A packet that is smaller than 2 bytes was queued for transmission. The interface cannot process such small packets for transmission.
Recommended Action The system should recover. 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%FECPM-3-TXCOMPNOTIFY : On int [chars], tx_comp_notify vector is not set
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 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%FECPM-3-UFHANDLE : UnderFlow handling on int [chars] failed.
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 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%FECPM-5-UNDERFLOW : Transmit underflow on int [chars]
Explanation While a frame was being transmitted, the local buffer of the serial controller chip received insufficient data because data could not be transferred to the chip quickly enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
FESMIC_FLTMG Messages
The following are FESMIC fault management-related messages.
Error Message%FESMIC_FLTMG-3-CMIC : Warning: [chars]
Explanation A warning-level event 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%FESMIC_FLTMG-5-EEPROM : Warning: [chars]
Explanation A warning-level event 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%FESMIC_FLTMG-3-ESB : Warning: [chars]
Explanation A warning-level event 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%FESMIC_FLTMG-7-INTERNAL_ERR : Internal 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 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%FESMIC_FLTMG-5-NOTICE : Notice: [chars]
Explanation A notice-level event 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%FESMIC_FLTMG-3-TOOMANYSVI : Error: Cannot create more than [dec] VLAN interfaces
Explanation An error event has occurred. The error message text provides more information on the nature of the 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. 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%FESMIC_FLTMG-4-VLANMACADDR_ALLOC_ERR : fesmic VLAN MAC Addr allocation error : [chars]
Explanation No more MAC addresses can be allocated for the VLAN. The MAC address was to be used for the bridge ID for a VLAN STP.
Recommended Action Limit the number of VLAN STPs to the maximum that the router can support. For the Cisco 3660 and 3640 routers, a maximum of 64 STPs are allowed. For the Cisco 2600 series and the Cisco 3620 routers, a maximum of 32 STPs are allowed. 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%FESMIC_FLTMG-5-WARNING : Warning: [chars]
Explanation A warning-level event 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.
FIB Messages
The following are forwarding information base (FIB) messages.
Error Message%FIB-3-FIBBADXDRHWSBDECODE : HW subblock decode ([chars] / [dec]) - wrong length read.
Explanation The specified hardware subblock is not being processed correctly on the line card. The error has been corrected, but it should be reported in case there are related problems that have to be addressed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBBADXDRSWSBDECODE : SW subblock decode ([chars] / [dec]) - wrong length read.
Explanation The specified software subblock is not being processed correctly on the line card. The error has been corrected, but it should be reported in case there are related problems that have to be addressed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBLC_OOSEQ : Slot [dec] disabled - Out of Sequence. Expected [dec], received [dec] expected seq_epoch [dec] received seq_epoch [dec]
Explanation The RP has received an out-of-sequence IPC from the line card. CEF switching has been disabled on the specified slot.
Recommended Action Enter the clear cef linecard slot-number command, with slot-number being the slot number of the affected line card. Then check the status of the line card by entering the show cef linecard command. 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%FIB-4-FIBMSG : Invalid message received. Type [chars], event/sub-type [dec], length [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show cef linecard failed-ipc command. 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, show tech-support, and show cef linecard failed-ipc commands and your pertinent troubleshooting logs.
Error Message%FIB-3-FIBSEQ : Out of sequence. State [dec] Rcvd [dec] seq_epoch [dec] received seq_epoch [dec]
Explanation The line card has received an out-of-sequence IPC from the RP. CEF switching has been disabled on the specified slot.
Recommended Action Enter the clear cef linecard slot-number command, with slot-number being the slot number of the affected line card. Then check the status of the line card by entering the show cef linecard command. 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%FIB-2-IF_NUMBER_ILLEGAL : Attempt to create CEF interface for [chars] with illegal if_number: [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB-2-RDBADDFAIL : Failed to add RDB to NDB
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
FIB_HM Messages
The following are forwarding information base (FIB) health monitor (HM) messages.
Error Message%FIB_HM-3-CLEANUP_FAIL : [chars] after Health Monitor rule ([chars]) creation failed.
Explanation Cleanup failed after the creation of a health monitor rule failed. There is little adverse effect, apart from using a small amount of memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB_HM-3-CREATE_RULE_FAILED : The FIB Health Monitor rule ([chars]) creation failed: [chars]
Explanation The FIB has failed to create a health monitor rule. The health monitor rule is not operational. This failure does not have any adverse affects on the FIB or on the health monitor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB_HM-3-HM_REGISTRATION_FAILED : The FIB HM subsystem failed to register with the Health-Monitor
Explanation The FIB has failed to register with the health monitor. The health monitor rules associated with FIB are not operational. This failure does not have any adverse affects on the FIB or on the health monitor.
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.
FIB_HM_MVL Messages
The following are platform dependent, FIB Health Monitor messages.
Error Message%FIB_HM_MVL-4-FB_BUSYOUT : Busy out feature board [dec], [chars]
Explanation The feature board is busied out for the reason specified.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB_HM_MVL-4-FB_RESET : Power cycling feature board [dec], [chars]
Explanation A feature board is being reset for the reason specified in the message text.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%FIB_HM_MVL-3-SUBSYS_HEALTH_CHANGE_FAIL : Attempt to [chars] FIB HM subsystem health (re slot [dec]) by [dec] failed.
Explanation An attempt to update the health of the FIB HM subsystem failed. The FIB subsystem health is not correct.
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.
FILESYS Messages
The following are file system messages.
Error Message%FILESYS-4-RCSF : [chars] ([dec]) <[chars]>
Explanation The configuration that is running could not be synchronized.
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.
FIO_TDM Messages
The following are messages related to the Cisco 3700XM TDM device.
Error Message%FIO_TDM-1-INIT_FAIL : C3700XM TDM Initialization Failed
Explanation TDM hardware initialization on the C3700XM platform has failed.
Recommended Action Power down and reboot 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 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.
FLEX_DNLD Messages
Error Message The following are Voice Over IP (VoIP) driver messages.%FLEX_DNLD-3-ERROR_ANALYZE : Error analyzing the device in slot [dec].
Explanation The port module in the slot specified in the message could not be recognized.
Recommended Action Power down, reinsert the port module, and reboot 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.
Error Message%FLEX_DNLD-3-ERROR_FIRMWARE_DNLD : DSP firmware download fails for slot [dec] dsp_id [dec]
Explanation The DSP could not be initialized with the application firmware.
Recommended Action Power down, reinsert the port module, and reboot 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.
Error Message%FLEX_DNLD-1-INCORRECT_DSP_ID : AIM VOICE at slot [dec] receives data from incorrect DSP-ID [dec].
Explanation The DSP ID provided by the FPGA for download is not valid.
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%FLEX_DNLD-3-NO_FIRMWARE_DNLD : No DSP firmware download invoked for slot [dec], no DSPs on the card
Explanation No DSP could be detected on the card.
Recommended Action Plug the DSP into the network module.
Error Message%FLEX_DNLD-1-NOPCIMEMORY : VPM ([dec]/[dec]), PCI memory unavailable.
Explanation The router or access server could not allocate memory for the descriptors.
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%FLEX_DNLD-1-NO_RING_DESCRIPTORS : No more ring descriptors available on slot [dec] dsp [dec].
Explanation The download driver for the DSP firmware cannot queue messages to the egress queue so that the FPGA can transmit them.
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%FLEX_DNLD-1-TOOBIG : [chars], packet(size [dec]) too big.
Explanation A packet greater than 264 bytes has been received on this interface.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates an error that might be related to data traffic patterns. 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.
FM Messages
The following are Forwarding Manager (FM) messages.
Error Message%FM-3-APPL_BAD : [chars]
Explanation A Forwarding Manager internal error has occurred. An invalid application type has been passed to the Forwarding Manager.
Recommended Action 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%FM-3-BAD_PORT_NUMBER : [chars]
Explanation A Forwarding Manager internal error has occurred. The destination port passed to the Forwarding Manager is invalid.
Recommended Action 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%FM-3-INTERNAL_ERROR : [chars]
Explanation A Forwarding Manager internal error has occurred.
Recommended Action 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%FM-3-INVALID_OFHDR : [chars]
Explanation A Forwarding Manager internal error has occurred. The table entry contained an invalid flow header.
Recommended Action 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%FM-3-INVALID_PARAM : [chars]
Explanation Invalid parameters have been passed to the Forwarding Manager.
Recommended Action 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%FM-3-INVALID_STREAM : [chars]
Explanation The Forwarding Manger has encountered an invalid stream ID.
Recommended Action 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%FM-3-MALLOC_FAIL : [chars], [chars]
Explanation A Forwarding Manager internal error has occurred. There has been a memory allocation failure. This condition might have been caused by low system memory or a memory leak.
Recommended Action 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%FM-3-SELECT_MODE_BAD : [chars]
Explanation A Forwarding Manager internal error has occurred. The forwarding manager selected an invalid mode while a stream was being set up.
Recommended Action 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%FM-3-SWITCH_STREAM_CREATION_FAILED : [chars]
Explanation The stream or flow could not be created in the switch fabric driver.
Recommended Action 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%FM-3-SWITCH_STREAM_REMOVAL_FAILED : [chars]
Explanation The stream or flow could not be removed from the MMC driver.
Recommended Action 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%FM-3-TBLENT_NOT_FOUND : [chars]
Explanation A Forwarding Manager internal error has occurred. A table entry could not be found for the port, application type and interface specified in the error message
Recommended Action 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.
FPGA Messages
The following are LS 1010 chip-specific messages.
Error Message%FPGA-3-ABR : ABR FPGA don't reset properly, Control Register=[hex]
Explanation An event that should never be seen on a Cisco 6400 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%FPGA-2-DONE_PIN : Done pin or Status pin didn't go low, FPGA# [dec]
Explanation The specified FPGA chip has shown an incorrect status after its control microcode was downloaded. This condition is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.
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%FPGA-2-DOWNLOAD : Download Fail, FPGA# [dec]
Explanation The specified FPGA chip failed to respond after downloading its control microcode. This condition is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.
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%FPGA-3-MCAST : Multicast FPGA did not reset properly, Control Register=[hex]
Explanation An event that should never be seen on a Cisco 6400 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%FPGA-3-NOFORK : Couldn't start Per-VC counter daemon
Explanation The per-VC counter daemon process could not be started during system initialization.
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%FPGA-2-STATUS_PIN : Error in status pin, FPGA# [dec]
Explanation The specified FPGA chip showed an incorrect status after its control microcode had been downloaded. This condition is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.
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%FPGA-3-TRAFF : Traffic FPGA don't reset properly, Control Register=[hex]
Explanation An event that should never be seen on a Cisco 6400 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%FPGA-3-TYPE : ***WARNING*** Invalid feature card type -n Use higher version of software: [hex]\n
Explanation The Cisco IOS software found an unrecognized feature card during Cisco LS1010 initialization. This message probably means that the software should be upgraded to support hardware that was not available when the software was released.
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%FPGA-3-VERSION : Feature Card version invalid/old. Feature Card Version:[dec].[dec], NSP Version:[dec].[dec]
Explanation An invalid or obsolete version of the feature card has been installed. It is incompatible with the current NSP version.
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.
FLEXDSPRM Messages
The following are flex DSPRM operation messages.
Error Message%FLEXDSPRM-5-CB_UPDOWN : Channel Bank [chars] state is [chars]
Explanation The channel bank status has changed.
Recommended Action Check if the voice ports in the channel bank are enabled (UP).
FR Messages
The following are Frame Relay messages.
Error Message%FR-3-MFR_UNEXPECTEDEVENT : MFR Timer process error: event table is NULL for event [dec], state [dec]
Explanation The event was ignored because the state transition table is NULL. Normal processing will continue.
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.
FR_VCB Messages
The following are Frame Relay VC bundle messages.
Error Message%FR_VCB-5-UPDOWN : FR VC-Bundle [chars] changed state to [chars]
Explanation The state of a Frame Relay VC bundle changed from "up" to "down".
Recommended Action No action is required.
FREEDM Messages
The following are CT3 trunk card Freedm messages.
Error Message%FREEDM-3-FREEDM_PCI_PERR : PCI PERR on FREEDM [dec] interrupt status reg: [hex]
Explanation A PCI parity error was detected on Freedm. It is not a problem if this error is the result of an on-line removal.
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. Enter 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 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%FREEDM-3-FREEDM_PCI_SERR : PCI SERR on FREEDM [dec] interrupt status reg: [hex]
Explanation A PCI system error was detected on Freedm. It is not a problem if this error is the result of an on-line removal.
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. Enter 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 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.
FS_IPHC Messages
The following are fast IP header compression messages.
Error Message%FS_IPHC-4-LC_IPCSENDFAIL : LC unable to send IPHC msg to RP
Explanation A line card was unable to send an IP header compression information message to the Route Processor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug ip rtp head and debug ip tcp head commands for the period during which this message appeared, if possible. 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%FS_IPHC-2-LC_IPHC_SETUP_FAIL : Failed to initialise or allocate memory for IP Compression database.
Explanation The IP Compression main database could not be created because of a lack of memory resources. The line card cannot allocate memory for an IP Compression database.
Recommended Action If possible, add more memory to the VIP. Allocate additional free memory on the VIP by reducing features that are used for buffer allocations. Reduce the number of contexts configured on all interfaces on the affected line card by entering the ip rtp compression-connections command in interface configuration mode.
Error Message%FS_IPHC-4-LC_NOIPCBUFFER : Unable to malloc IPC msg buffer ([int]) on line card
Explanation The line card did not have enough memory in its private memory pool to send IPHC information to the RP.
Recommended Action If this message occurs frequently, 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%FS_IPHC-4-RP_IPCSENDFAIL : RP unable to send IPHC msg to Line Card
Explanation The Route Processor was unable to send an IP header compression configuration message to a line card interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. If possible, also provide the output of the debug ip rtp head and debug ip tcp head commands for the period during which this message appeared.
FW Messages
The following are inspection subsystem messages.
Error Message%FW-4-ALERT_OFF : [chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the number of half-open connections have dropped below the low threshold, or the new connection initiation rate has dropped below the low threshold. This message may indicate that an attack has stopped.
Recommended Action No action is required.
Error Message%FW-4-ALERT_ON : [chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the high threshold of half-open connections has been exceeded, or the new connection initiation rate has been exceeded. This error message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is for informational purposes only, but may indicate a security problem.
Recommended Action If an attack is suspected, perform actions to block the security attack.
Error Message%FW-2-BLOCK_HOST : Blocking new TCP connections to host [IP_address] for [dec] minute[chars] (half-open count [dec] exceeded).
Explanation The threshold of half-open TCP connections has been exceeded, and the blocking option will now block any subsequent new connections. The blocking will be removed when the configured block-time expires. This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.
Recommended Action If a SYN attack is suspected, perform actions to block a SYN attack.
Error Message%FW-6-DROP_PKT : Dropping [chars] pkt [IP_address]:[int] => [IP_address]:[int]
Explanation A packet has been dropped during a firewall inspection operation.
Recommended Action This message is for informational purposes only. No action is required.
Error Message%FW-5-EMAIL_DROP_FRAGMENT : [chars]Dropping [chars] command fragment from initiator ([IP_address]:[dec])
Explanation The CBAC code detected a pipelined POP3/IMAP command fragment in the inspected POP3 connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The fragment was immediately dropped by the firewall.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
Error Message%FW-3-FTP_NON_MATCHING_IP_ADDR : Non-matching address [IP_address] used in [chars] -- FTP client [IP_address] FTP server [IP_address]
Explanation A suspicious violation was detected while an attempt was made to modify the security policy in the firewall. An FTP client attempted to use a port command, or the FTP server attempted to use the response to a pasv command, to trick the firewall into opening access to a third-party host that is different from the two hosts engaged in the FTP connection. The command is rejected, and the connection has been reset by the firewall. This message is for informational purposes only, but may indicate that an attempt was made to grant or open access to unauthorized hosts.
Recommended Action If you suspect that an attempt was made to grant or open access to unauthorized hosts, perform actions to block this attempt.
Error Message%FW-3-FTP_PRIV_PORT : Privileged port [dec] used in [chars] -- FTP client [IP_address] FTP server [IP_address]
Explanation A suspicious violation has been detected from an FTP client or server that was attempting to modify the security policy in the firewall. An FTP client attempted to use a port command, or the FTP server attempted to use the response to a pasv command, to trick the firewall into opening access to a privileged port. The command is rejected and the connection is reset by the firewall. This message is for informational purposes only, but may indicate that an attempt was made to gain access to privileged ports.
Recommended Action if you suspect that an attempt was made to gain access to privileged ports, perform actions to block this attempt.
Error Message%FW-3-FTP_SESSION_NOT_AUTHENTICATED : Command issued before the session is authenticated -- FTP client [IP_address] FTP server [IP_address]
Explanation A suspicious attempt has been made by a client or server to trick the firewall into opening a hole so that outside attackers can take advantage of the firewall opening. An FTP client attempted to use the port command, or an FTP server attempted to use the response to a pasv command to open a data channel in the firewall before the client could be successfully authenticated with the server. This condition indicated a suspicious violation. The port or pasv command and response has been rejected by the firewall. The data channel in the firewall will not be opened until the authentication is successfully performed. This message is for informational purposes only, but may indicate that an illegal attempt was made to modify the firewall security policy.
Recommended Action If you suspect that an illegal attempt was made to modify the firewall security policy, perform actions to block that attempt.
Error Message%FW-4-HOST_TCP_ALERT_ON : Max tcp half-open connections ([dec]) exceeded for host [IP_address].
Explanation The maximum limit of half-open TCP connections has been exceeded. A high number of half-open connections is being received by the protected server. This condition may indicate that a SYN flood attack is in progress and is targeted to the specified server host. This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.
Recommended Action If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a lot of legitimate traffic coming in to that server. In this case, set the max-incomplete host parameter to a higher number to avoid false alarms.
Error Message%FW-3-HTTP_JAVA_BLOCK : JAVA applet is blocked from ([IP_address]:[dec]) to ([IP_address]:[dec]).
Explanation A Java applet was seen in the HTTP channel, and the firewall configuration indicates that the applet from the specified Internet site should be prohibited. The applet is being downloaded from one of the prohibited sites, and its entrance to the protected network is not allowed. The connection has been reset and the transmission of the detected applet has been immediately aborted. This message is for informational purposes only, but may indicate a security problem.
Recommended Action Determine the cause of this condition.
Error Message%FW-5-IMAP_INVALID_COMMAND : [chars]Invalid IMAP command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected an invalid IMAP command in the inspected IMAP connection. This message indicates that a suspicious violation was detected that may be an attack to the mail server system. The command is rejected and the connection is immediately reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
Error Message%FW-5-IMAP_NON_SECURE_LOGIN : [chars]LOGON IMAP command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected a cleartext logon attempt in the inspected IMAP connection while secure-login is configured. The command was rejected and the connection was immediately reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
Error Message%FW-6-INIT : Firewall inspection startup completed; beginning operation.
Explanation Firewall inspection is present in the startup configuration for at least one interface.
Recommended Action This message is for informational purposes only. It may be used to verify whether firewall inspection is active during system startup.
Error Message%FW-3-INTERNAL_ERROR : IP Firewall internal failure -- [chars]
Explanation There were miscellaneous errors in the IP FW subsystem.
Recommended Action This message indicates the miscellaneous errors in the IP FW subsystem.
Error Message%FW-3-NOTFOUND : Session context for ([IP_address]:[dec]) => ([IP_address]:[dec]) not found.
Explanation The CBAC code was searching its database for information for a particular inspection session, but this information was not found.
Recommended Action 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%FW-5-POP3_INVALID_COMMAND : [chars]Invalid POP3 command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected an invalid POP3 command in the inspected POP3 connection. A suspicious violation was detetected that may be an attack to the mail server system. The command was rejected and the connection was immediately reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
Error Message%FW-5-POP3_NON_SECURE_LOGIN : [chars]LOGON POP3 command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected a cleartext logon attempt in the inspected POP3 connection while secure-login is configured. The command was rejected and the connection was immediately reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
Error Message%FW-6-PRE_ALLOCATED_MEDIA_CHANNEL : Pre-Allocated [chars] channel from [IP_address][[dec]:[dec]] to [IP_address][[dec]:[dec]]
Explanation The CBAC inspection has preallocated data structures and has created ACEs to allow the data or media traffic to flow through the firewall. This message is for informational purposes only, and may be used to verify whether data or media sessions are being created.
Recommended Action No action is required.
Error Message%FW-6-SESS_AUDIT_TRAIL : Stop [chars] session: initiator ([IP_address]:[dec]) sent [int] bytes -- responder ([IP_address]:[dec]) sent [int] bytes
Explanation This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source and destination addresses and ports, as well as the number of bytes transmitted by the client and server. This message is for informational purposes only, and can be used to collect basic accounting information for inspected sessions.
Recommended Action No action is required.
Error Message%FW-6-SESS_AUDIT_TRAIL_START : Start [chars] session: initiator ([IP_address]:[dec]) -- responder ([IP_address]:[dec])
Explanation This message documents the opening of an inspection session. The message is issued at the start of each inspected session and it records the source and destination addresses and ports. This message is for informational purposes only, and can be used to collect basic accounting information for inspected sessions.
Recommended Action No action is required.
Error Message%FW-6-SESS_AUDIT_TRAIL_START : Start [chars] session: initiator ([IP_address]:[dec]) -- responder ([IP_address]:[dec])
Explanation An inspection session has started. The message is issued at the start of each inspected session, and it records the source and destination addresses and ports. This message is for informational purposes only and can be used to collect the basic accounting for inspected sessions.
Recommended Action No action is required.
Error Message%FW-4-SESSION_THRESHOLD_EXCEEDED : [chars]Number of sessions for the firewall rule '[chars]' applied on interface '[chars]' exceeds the configured threshold [dec]
Explanation This message indicates that the number of established CBAC sessions has exceeded the configured threshold.
Recommended Action This message is for informational purpose only, but may indicate a security problem. This might also mean that the session threshold is set to a low value, in which case the threshold value could be increased through a CLI command.
Error Message%FW-4-SKINNY_INSPECTION_DISABLED : Skinny Inspection Disabled; Error = [chars]
Explanation Inspection of skinny protocol traffic has been disabled due to internal errors. The firewall will not inspect any skinny protocol traffic. This condition occurs when the firewall does not have enough memory to allocate initial skinny data structures.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Restart the firewall, the router, or both to enable inspection of skinny protocol traffic.
Error Message%FW-3-SMTP_INVALID_COMMAND : Invalid SMTP command ([chars])(total [dec] chars) from initiator ([IP_address]:[dec])
Explanation The CBAC code has detected an invalid SMTP command in the inspected SMTP connection. This condition indicates that a suspicious violation was detected that may be an attack to the mail server system. The command has been rejected and the connection has immediately been reset by the firewall. This message is for informational purposes only, but may indicate a security problem.
Recommended Action If you suspect a security problem, perform actions to correct the problem.
Error Message%FW-3-SMTP_UNSUPPORTED_PARAMETER : Unsupported SMTP parameter ([chars]) from initiator ([IP_address]:[dec])
Explanation The CBAC code has detected an invalid or unsupported parameter in an SMTP command. The parameter "@ or # to ETRN" means that the initiator is trying to send an invalid etrn command. This message is for informational purposes only, but may indicate a security problem.
Recommended Action If you suspect a security problem, perform actions to correct the problem.
Error Message%FW-4-TCP_MAJORDOMO_EXEC_BUG : Majordomo Execute Attack - from [IP_address] to [IP_address]
Explanation A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server. For security reasons, users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack.
Recommended Action Shun the source of the command execution immediately.
Error Message%FW-4-TCP_SENDMAIL_BAD_FROM_SIG : Sendmail Invalid Sender - from [IP_address] to [IP_address]
Explanation A pipe (|) symbol has been found in the "From:" field of a mail message. For security reasons, users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack.
Recommended Action Shun the source of the mail message.
Error Message%FW-4-TCP_SENDMAIL_BAD_TO_SIG : Sendmail Invalid Recipient - from [IP_address] to [IP_address]
Explanation A pipe (|) symbol has been found in the recipient field of a mail message. For security reasons, users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack.
Recommended Action Shun the source of the mail message.
Error Message%FW-4-TCP_SENDMAIL_DECODE : Sendmail Decode Alias - from [IP_address] to [IP_address]
Explanation A ": decode@'' has been found in the header of a mail message. The decode alias is used to decode binary files and is primarily implemented as a convenience for system administration. For security reasons, users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack.
Recommended Action Shun the source of the mail message.
Error Message%FW-4-TCP_SENDMAIL_INVALID_COMMAND : Invalid SMTP command - [IP_address] to [IP_address]
Explanation An invalid SMTP command has been detected in the SMTP connection. A suspicious violation has been detected that may indicate an attack to the mail server system.
Recommended Action Investigate the unusual traffic.
Error Message%FW-4-TCP_SENDMAIL_OLD_SIG : Archaic Sendmail Attacks - from [IP_address] to [IP_address]
Explanation A wiz or debug command has been sent to the SMTP port. For security reasons, users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack.
Recommended Action Shun the source of the commands immediately.
Error Message%FW-4-UNBLOCK_HOST : New TCP connections to host [IP_address] no longer blocked
Explanation New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted. This message is for informational purposes only, but may indicate that a SYN flood attack was previously attempted to the host.
Recommended Action No action is required.
GBIC_SECURITY Messages
The following are GBIC security check messages.
Error Message%GBIC_SECURITY-4-EEPROM_CRC_ERR : EEPROM checksum error for GBIC in [chars]
Explanation The GBIC in the port specified in the error message contains invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.
Error Message%GBIC_SECURITY-4-EEPROM_READ_ERR : Error in reading GBIC serial ID in [chars]
Explanation An error occurred while the GBIC type was being read from EEPROM.
Recommended Action Remove the GBIC from the specified port.
Error Message%GBIC_SECURITY-4-EEPROM_SECURITY_ERR : GBIC in [chars] failed security check
Explanation The GBIC in the port specified in the error message contains invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.
Error Message%GBIC_SECURITY-4-GBIC_INTERR : Internal error occurred in setup for GBIC interface [chars]
Explanation The system could not allocate resources, or had some other error, in the setup for the specified GBIC interface.
Recommended Action Reload the system. 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.
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 in the specified port was identified as a Cisco GBIC, but the system was unable to verify its identity.
Recommended Action Verify that 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 in the specified port 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 Verify that 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 Verify that 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.
GENERAL Messages
The following are Zenith Route Processor miscellaneous 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 that is to be used for sanity testing.
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-EREVENTHEX : [chars] [hex]
Explanation This message provides error information to be used for sanity testing.
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-EREVENTPXF : [chars] [chars], [chars], [chars]=[dec], [chars]=[dec],[dec], [chars]=[hex], [chars]=[hex], [chars]=[hex], [chars]=[int]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GENERAL-3-EREVENTSTR : [chars] [chars]
Explanation This message is a general error condition that is primarily displayed 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%GENERAL-5-IPHCEREVENT : [chars] [dec] [chars] [dec] [chars]
Explanation There was an RPM-XF specific IPHC error.
Recommended Action No action is required.
Error Message%GENERAL-5-NOTEVENT : [chars]
Explanation This message provides general information regarding a notification message.
Recommended Action No action is required.
Error Message%GENERAL-3-WSEVENT : [chars]
Explanation This message provides information on a general error to be used for sanity testing.
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.
GK Messages
The following are GK-H.323 messages.
Error Message%GK-3-GKTMP_SERVER_MARKED_UNUSABLE : GKTMP Server: [chars]([chars]) connected to GK: [chars] is marked unusable
Explanation The gatekeeper has marked a GKTMP server as unusable when flow control is configured. The reason for this action could be that the average response time of the GMTMP server is very high, or the number of messages queued to be sent to the GKTMP server is very high. These conditions could be caused by an overloaded server or a problem with the TCP connection between the server and the gatekeeper.
Recommended Action Check the operational status of the GKTMP server and the network link between the server and the gatekeeper. If both are operational, enter the show running-config and
the show gatekeeper servers commands and verify the status of the GKTMP server. Enter the debug gatekeeper server command on the Gatekeeper to enable debugging on the gatekeeper server. Gather this information, contact your Cisco technical support representative, and provide the representative with the gathered information.Error Message%GK-5-GKTMP_SERVER_MARKED_USABLE : GKTMP Server: [chars]([chars]) connected to GK: [chars] is marked usable
Explanation The gatekeeper has marked the GKTMP server as usable when flow control is configured.
Recommended Action No action is required.
Error Message%GK-3-GKTMP_SERVER_OFFLINE : GKTMP Server: [chars]([chars]) is disconnected with Gatekeeper: [chars]
Explanation The connection between a GKTMP server and a gatekeeper has been closed. The reason for the closed connection could be one of the following:
–
Closing of a connection by the gatekeeper because a socket read or write operation failed.
–
–
–
–
–
Recommended Action Check the operational status of the gatekeeper and the GKTMP server. If both are operational, check the TCP connection between the server and the gatekeeper. Check the output of the show running-config and show gatekeeper servers commands. Verify the status of the GKTMP server. Enter the debug gatekeeper server command on the gatekeeper to enable debugging on the gatekeeper server. Collect this information, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GK-5-GKTMP_SERVER_ONLINE : GKTMP Server: [chars]([chars]) is connected with Gatekeeper: [chars]
Explanation A connection between a GKTMP server and a gatekeeper has been established. The establishment of a connection could be initiated by either the gatekeeper or a GKTMP server.
Recommended Action No action is required.
GPRSFLTMG Messages
The following are Global Packet Radio Service fault management messages.
Error Message%GPRSFLTMG-4-AAAFAIL_PDPACTIVATIONFAIL : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]
Explanation PDP activation has failed for one of the following reasons:
1.
2.
3.
4.
5.
Recommended Action For reason 1, check to see that the RADIUS server is configured properly and that the server is reachable via a ping operation. For reason 2, check to see whether the RADIUS server is configured properly. Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command. 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%GPRSFLTMG-4-APNRELATEDERROR_PDPACTIVATIONFAIL : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]
Explanation PDP activation has failed because of one of the following APN-related problems:
1.
2.
3.
4.
Recommended Action Check the APN configuration as indicated in the given reason. If that does not solve the problem and the message recurs, enter the show running-config and show gprs access-point all commands. 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%GPRSFLTMG-4-CHARGING : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]
Explanation One of the following conditions is present:
1.
2.
3.
4.
5.
Recommended Action Reason 1 is an information message only. For reason 2, check to see whether the charging gateways are configured correctly and are active with the charging functionality. For reason 3, if the configured charging gateway is up and reachable from the GSN, check to see whether the charging function is enabled in the gateway. For reasons 4 or 5, if you have entered the gprs char charging-send-buffer-size command and have specified minimum bytes, specify maximum bytes as well. If the 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%GPRSFLTMG-0-GPRS_DHCP : [chars]
Explanation Either the DHCP client could not be started, possibly because of memory allocation failures, or the GPRS DHCP process could not be started.
Recommended Action Do not use this GGSN for PDP session establishment with SGSN that includes a dynamic IP request. Check the available memory on the router and reduce other system activity to ease memory demands. If the DHCP client could not be started, enter the debug dhcp detail command and attempt to recreate the problem. 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%GPRSFLTMG-0-GPRS_SERVICE : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]
Explanation One of the following conditions has occurred:
1.
2.
3.
4.
5.
6.
7.
Recommended Action Messages with reasons 2, 5, and 6 are informational. For any of the other messages that were received, 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%GPRSFLTMG-4-GTPv1AAAFAIL_PDPACTIVATIONFAIL : GSN: [IP_address], TEID: [hex], APN: [chars], Reason: [dec], [chars]
Explanation A PDP Activation has been failed because of one of the following reasons:
1.
2.
3.
4.
Recommended Action For reason 1, check whether the RADIUS server is configured properly and if a ping operation can be performed successfully. For reason 2, check whether the RADIUS server is configured properly. For reasons 3 and 4, 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%GPRSFLTMG-4-GTPv1APNRELATEDERROR_PDPACTIVATIONFAIL : GSN: [IP_address], TEID: [hex], APN: [chars], Reason: [dec], [chars]
Explanation PDP activation has failed because of one of the APN-related problems:
1.
2.
3.
4.
Recommended Action Check the APN configuration that corresponds to the error that was received. If the error persists, copy the message exactly as it appears on the console or in the system log. Enter the show running-config and show gprs access-point all commands. 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%GPRSFLTMG-4-GTPv1IPALLOCATIONFAIL_PDPACTIVATIONFAIL : GSN: [IP_address], TEID: [hex], APN: [chars], Reason: [dec], [chars]
Explanation An IP address could not be dynamically allocated because of one of the following reasons:
1.
a.
b.
c.
2.
3.
Recommended Action For reason 1a, check that the GGSN is configured with the valid DHCP/RADIUS server IP address. For reason 1b, check that the DHCP or RADIUS server is configured properly to allocate an IP address. For reason 1c, if the configurations are properly configured, check that the server is reachable from GGSN. For reason 2, configure the IP allocation pool as either a DHCP proxy client or a RADIUS client in the APN. For any other reason, or if the 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%GPRSFLTMG-4-GTPv1MOBILITY : GSN: [IP_address], TEID: [hex], APN: [chars], Reason: [dec], [chars]
Explanation One of the following mobility-related problems has occurred:
1.
2.
3.
4.
5.
Recommended Action If the 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%GPRSFLTMG-0-GTPv1NORESOURCE : GSN: [IP_address], TEID: [hex], APN: [chars], Reason: [dec], [chars]
Explanation Available resources are exhausted. GGSN service cannot continue because of one of the following reasons:
1.
2.
3.
Recommended Action For reason 1, check whether the number of PDPs that can be processed by GGSN can be increased. Check the APN configuration that corresponds to the error that was received. For any other reason, or if the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show gprs gtp status command. 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%GPRSFLTMG-4-GTPv1QOSFAIL_PDPACTIVATIONFAIL : GSN: [IP_address], TEID: [hex], APN: [chars], Reason: [dec], [chars]
Explanation A QoS negotiation or update has failed. System resources were not available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show gprs gtp status command. 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%GPRSFLTMG-4-HARDWAREFAIL : Reason: [chars]
Explanation An NVRAM write operation has failed.
Recommended Action 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%GPRSFLTMG-4-IPALLOCATIONFAIL_PDPACTIVATIONFAIL : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]
Explanation An IP address could not be dynamically allocated because of one of the following reasons:
1.
2.
3.
4.
5.
Recommended Action For reason 1, check to see whether the GGSN is configured with the valid DHCP or RADIUS server IP address. For reason 2, check to see whether the DHCP or RADIUS server is properly configured to allocate an IP address. For reason 3, if the configurations have been checked and are correct, check to see whether the server is reachable from GGSN. For reason 4, configure the IP allocation pool as either a DHCP proxy client or a RADIUS client in the APN. If you still cannot fix the problem, or if any other message was received, 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%GPRSFLTMG-4-MOBILITY : GSN: [IP_address], TID: [hex][hex], APN: [chars], Username: [chars] Reason: [dec], [chars]
Explanation One of the following problems related to mobility has occured:
1.
2.
3.
4.
5.
Recommended Action If the 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%GPRSFLTMG-0-NOPROCESS : [chars]
Explanation A process could not be started.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show gprs gtp status command. 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%GPRSFLTMG-4-QOSFAIL_PDPACTIVATIONFAIL : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]
Explanation QoS could not be negotiated or updated because resources were not available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show gprs gtp status command. 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%GPRSFLTMG-0-RESOURCE : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]
Explanation Available resources have become exhausted. GGSN service cannot continue because of one or more of the following reasons:
1.
2.
3.
Recommended Action For reason 1, check to see whether you can increase the number of PDPs that can be processed by GGSN. For any of the other reasons, if the problem recurs, copy the message exactly as it appears on the console or in the system log. Enter the show gprs gtp status command. 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.
GPRSMIB Messages
The following are Global Packet Radio Service MIB messages.
Error Message%GPRSMIB-4-FRAGMENT_ERROR : fragmentation error (s_uid = [hex]) received
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GPRSMIB-4-INVALIDMSG : Invalid GPRSMIB message (msg_type [hex]) received
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
GRP_C10K_CH_DS3 Messages
The following are Cisco 10000 channelized-to-DS3 RP driver messages.
Error Message%GRP_C10K_CH_DS3-1-ALLOCFAIL : C10K [dec]/[dec][chars] allocation failure
Explanation A Cisco 10000 channelized-to-DS3 controller or channel memory allocation failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GRP_C10K_CH_DS3-5-BERT : Interface [chars], BERT [chars]
Explanation The Cisco 10000 channelized-to-DS3 driver has received and processed a BERT completion event.
Recommended Action No action is required.
Error Message%GRP_C10K_CH_DS3-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The running configuration for the Cisco 10000 channelized-to-DS3 RP driver is corrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show gsr and show ipc status commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show gsr and show ipc status command output, 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_C10K_CH_DS3-5-FAREND : Interface [chars] [chars] far end request of type ([chars])
Explanation The Cisco 10000 channelized-to-DS3 driver has received and processed a known far-end request (for example, a loopback request).
Recommended Action No action is required.
Error Message%GRP_C10K_CH_DS3-1-MIA : C10K [dec]/[dec] LC removed during initialization
Explanation A Cisco 10000 channelized-to-DS3 line card was removed during initialization.
Recommended Action If C10K-channelized-to-DS3 functionality is desired, replace the line card.
Error Message%GRP_C10K_CH_DS3-4-MSGVERSION : Incompatible message version with slot [dec]
Explanation There is an incompatibility between the message version being sent by the line card and the message version used by the GRP. This type of incompatibility could happen if the GRP and the line card are using different Cisco IOS software versions because of a GRP OIR event. PoS statistics will not be sent to the GRP as a result of this condition; however, all functionality will be retained.
Recommended Action Reload the microcode to solve the problem.
Error Message%GRP_C10K_CH_DS3-3-OP : Interface ([chars]): [chars]
Explanation The Cisco 10000 channelized-to-DS3 driver has received an unexpected event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show gsr and show ipc status commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show gsr and show ipc status command output, 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_C10K_CH_DS3-3-TIMEOUT : Interface ([chars]): [chars]
Explanation The Cisco 10000 channelized-to-DS3 driver has queried the line card for SONET information, but the line card did not respond.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show gsr, show ipc nodes, show ipc ports, and show ipc status commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show gsr, show ipc nodes, show ipc ports, and show ipc status command output, 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_C10K_CH_DS3-3-UNKNOWN_FAREND : Interface [chars] received an unknown far end request ([int])
Explanation The C10K-CH-DS3 RP driver has received an unknown far-end request.
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.
GSHDSL Messages
The following are G.Symmetric High bit rate DSL (G.SHDSL) messages.
Error Message%GSHDSL-3-RESETFAIL : Interface [chars], restart failed.
Explanation The WIC hardware might have 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.
GSI Messages
The following are G.Symmetric High bit rate DSL (G.SHDSL) messages.
Error Message%GSI-1-INITFAIL : Interface [chars], init failed.
Explanation The DSL network module hardware might have 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%GSI-3-NOMEM : Interface [chars], system is out of memory
Explanation The router does not have enough memory installed to run this image.
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%GSI-3-NORESET : Interface [chars], failed when tried resetting from CLI.
Explanation The specified interface did not reset. The WIC hardware might have 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%GSI-1-PROCFAIL : Interface [chars], failed to create process
Explanation An attempt to create the monitor process has failed. There might not be enough available memory for creation of the monitor process.
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.
GT64120 Messages
The following are GT64120 DMA controller driver messages.
Error Message%GT64120-3-ID_ERROR : System controller has unexpected vendor id [hex] (expected [hex]) or unexpected device id [hex] (expected [hex])
Explanation The system controller has detected an unexpected vendor or device identification number. The system controller could be faulty or it could have a wrong hardware version. The system might not operate as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. 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.
GT96K_FE Messages
The following are messages related to Cisco 3700 series and Cisco 3631 system controller.
Error Message%GT96K_FE-2-CIU_LE : FE - interface: [chars] CIU arbiter configured incorrectly
Explanation The CIU arbiter is configured for little-endian mode, but the image expects the mode to be configured for big-endian.
Recommended Action Update the Cisco IOS software image to the latest version in your release train. 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.
GT96K_FEWAN Messages
The following are messages related to Cisco 3700 series and Cisco 3631 system controller.
Error Message%GT96K_FEWAN-3-BSCHUNT : BSC HUNT cmd for int [chars] failed
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show cef linecard failed-ipc command. 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, show tech-support, and show cef linecard failed-ipc commands and your pertinent troubleshooting logs.
Error Message%GT96K_FEWAN-1-DISCOVER : NM slot [dec]: only [dec] PCI dev found
Explanation Some of the interface controller devices on the GT96K_FEWAN network module did not initialize properly.
Recommended Action Power down the system, reinsert the port module, and reboot 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.
Error Message%GT96K_FEWAN-3-INVALID_CLOCKRATE : Unsupported clock rate req on int [chars] - index [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show cef linecard failed-ipc command. 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, show tech-support, and show cef linecard failed-ipc commands and your pertinent troubleshooting logs.
Error Message%GT96K_FEWAN-2-SCCFAIL : Init of SCC[dec] for int [chars] failed to do [chars]
Explanation The software failed to initialize or restart an SCC process for a serial interface on the GT96K FEWAN module.
Recommended Action Clear the serial 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.
Error Message%GT96K_FEWAN-3-SCCRESET : SCC reset for int [chars] at [chars] failed
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show cef linecard failed-ipc command. 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, show tech-support, and show cef linecard failed-ipc commands and your pertinent troubleshooting logs.
Error Message%GT96K_FEWAN-5-TOOSMALL : On int [chars], tx pak size is [dec] bytes
Explanation A packet that is smaller than 2 bytes was queued for transmission. The interface cannot process such small packets for transmission.
Recommended Action The system should recover. 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%GT96K_FEWAN-3-TXCOMPNOTIFY : On int [chars], tx_comp_notify vector is not set
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show cef linecard failed-ipc command. 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, show tech-support, and show cef linecard failed-ipc commands and your pertinent troubleshooting logs.
Error Message%GT96K_FEWAN-3-UFHANDLE : UnderFlow handling on int [chars] failed.
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show cef linecard failed-ipc command. 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, show tech-support, and show cef linecard failed-ipc commands and your pertinent troubleshooting logs.
GT96K_TDM Messages
The following are Cisco 37xx, Cisco 2691, and Cisco 3631 TDM subsystem messages.
Error Message%GT96K_TDM-1-INITFAIL : C3700 TDM Initialization Failed
Explanation The platform TDM hardware for the Cisco 3700 series Multiservice Access Routers could not be initialized.
Recommended Action Attempt to power down and reboot 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.