Feedback
Table Of Contents
SWEPA Messages
This section contains software encryption port adapter (SWEPA) and key management messages.
SWEPA-6
Error Message %SWEPA-6-EPA_EXP_RUNNING: Exp Running ....Explanation The EXP process is running.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SWEPA-6-EPA_EXP_TIMER_EXPIRED: Exp Timer Expired!Explanation The EXP timer has expired.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SWEPA-6-FAILED_TO_ALLOCATE_ENCRYPT_QUE: Failed to allocate the encrypt queue.Explanation The encryption queue could not be allocated.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SWEPA-6-FAILED_TO_START_DES_PROCESS: Failed to start DES processExplanation The DES process has failed to start.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SWEPA-6-FAILED_TO_START_EXP_PROCESS: Failed to start EXP processExplanation The EXP process has failed to start.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SWEPA-6-INIT_SW_EPA_IDB: Init swepa idb start ...Explanation The software encryption port adapter information descriptor block (IDB) is being initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SWEPA-6-START_DES_PROCESS: DES process start ...Explanation The DES process has started.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SWEPA-6-START_EXP_PROCESS: EXP process start ...Explanation The EXP process has started.
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://tools.cisco.com/ServiceRequestTool/create, 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.
SWITCH Messages
This section contains switch interface messages.
SWITCH-3
Error Message %SWITCH-1-RF_REGISTRTN_FAILED: unable to register switch driver client to RFExplanation The switch driver client could not be registered to the redundancy facility (RF).
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://tools.cisco.com/ServiceRequestTool/create, 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.
SWITCHOVER Messages
This section contains line card switchover-related messages.
SWITCHOVER-6
Error Message %SWITCHOVER-6-LC_HA_UNAWARE: Line card (type [hex]) in slot [dec] is not confgured HA mode awareExplanation The line card in the specified slot does not support the configured RP redundancy mode. The line card will be reset and reinitialized during RP failover.
Recommended Action No action is required.
SWITCH_QOS_TB Messages
This section contains trusted boundary messages.
SWITCH_QOS_TB-5
Error Message %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: [chars] detected on port [chars], port trust enabled.Explanation The trusted boundary facility has detected a device that matches the trusted device setting for the port, and the port trust state has been modified.
Recommended Action No action is required.
Error Message %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: [chars] no longer detected on port [chars], port set to untrusted.Explanation The trusted boundary facility has lost contact with a trusted device, and has set the port trust state to untrusted.
Recommended Action No action is required.
SWITCH_SPAN_ISSU Messages
This section contains span switch in-service software upgrade (ISSU) messages.
SWITCH_SPAN_ISSU-3
Error Message %SWITCH_SPAN_ISSU-3-BUFFER: span switch ISSU client failed to get buffer for message, error %dExplanation The SPAN switch ISSU client was unable to get a buffer for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %SWITCH_SPAN_ISSU-3-CAPABILITY: span switch ISSU client %sExplanation The SPAN switch ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %SWITCH_SPAN_ISSU-3-INIT: span switch ISSU client initialization failed at %s, error %sExplanation The SPAN switch ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SWITCH_SPAN_ISSU-3-MSG_NOT_OK: span switch ISSU client message %d is not compatibleExplanation The SPAN switch ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %SWITCH_SPAN_ISSU-3-MSG_SIZE: span switch ISSU client failed to get the message size for message %dExplanation The SPAN switch ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %SWITCH_SPAN_ISSU-3-POLICY: span switch ISSU client message type %d is %sExplanation The SPAN switch ISSU client received a message type that it does not support. A policy is applied to make the session compatible.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show issu session commands and your pertinent troubleshooting logs.
Error Message %SWITCH_SPAN_ISSU-3-SEND_FAILED: span switch ISSU client failed to send a negotiation message, error %dExplanation The SPAN switch ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %SWITCH_SPAN_ISSU-3-SESSION: span switch ISSU client %sExplanation The SPAN switch ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %SWITCH_SPAN_ISSU-3-TRANSFORM: span switch ISSU client %s transform failed, error %sExplanation The SPAN switch ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the SPAN switch state will not be identical with the active unit.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
SW_DAI-4-UNAVAILABLE
Error Message %SW_DAI-4-UNAVAILABLE: %d packets received in %d milliseconds on %s.Explanation The switch has received the given number of ARP packets in the given duration on the given interface. This message is logged just before the port is err-disabled because of exceeded packet rate. And this message is logged when the burst interval is set to 1 second.
Recommended Action LOT_STD_NO_ACTION
Error Message %SW_DAI-4-UNAVAILABLE: %d packets received in %d seconds on %s.Explanation The switch has received the given number of ARP packets in the specified burst interval. The interface is errdisabled when the switch receives packets at a rate higher than the configured packet rate every second over the configured burst interval. The message is logged just before the interface is err-disabled, and if the configured burst interval is more than a second.
Recommended Action LOT_STD_NO_ACTION
Error Message %SW_DAI-4-UNAVAILABLE: %ld Invalid ARP packets [%CC]Explanation The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message differs from other messages in that while the other can be used to provide as much information of the packet as possible, this message is used as a catch all message when the rate of incoming packets exceed DAI logging rate.
Recommended Action LOT_STD_NO_ACTION
Error Message %SW_DAI-4-UNAVAILABLE: %ld Invalid ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])Explanation The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and their presence indicates that administratively denied packets have been seen in the network. This log message shows up when packet(s) have been denied by acls either explicitly or implicitly(with static acl configuration). The presence of these packets indicates that man-in-the-middle attack(s) may have been attempted in the network.
Recommended Action LOG_STD_NO_ACTION
Error Message %SW_DAI-4-UNAVAILABLE: %ld Invalid ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])Explanation The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message is logged when the senders ip and mac binding for the received vlan is not present in the dhcp snooping database.
Recommended Action LOG_STD_NO_ACTION
Error Message %SW_DAI-4-UNAVAILABLE: %ld Invalid ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])Explanation The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and they do not pass one or more of source mac or destination mac or IP validation checks.
Recommended Action LOG_STD_NO_ACTION
SW_DAI-6
Error Message %SW_DAI-6-UNAVAILABLE: %ld ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])Explanation The switch has received ARP packets that have been permitted as a result of ACL match.
Recommended Action LOG_STD_NO_ACTION
Error Message %SW_DAI-6-UNAVAILABLE: %ld ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])Explanation The switch has received ARP packets that have been permitted as a result of senders IP and MAC address match against the dhcp snooping database for the received vlan.
Recommended Action LOG_STD_NO_ACTION
SW_MGR Messages
This section contains segment switch manager messages.
SW_MGR-3
Error Message %SW_MGR-3-CM_ERROR: Connection Manager Error - [chars].Explanation An error has occurred in the segment switch connection manager.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-CM_ERROR_CLASS: Connection Manager Error: Class [chars]: - [chars].Explanation An error has occurred in the connection manager.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-CM_ERROR_FEATURE: Connection Manager Feature Error: (%s) - %s.Explanation A segment switch connection manager feature class error 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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-CM_ERROR_FEATURE_CLASS: Connection Manager Feature Error: Class %s: (%s) - %s.Explanation A segment switch connection manager feature error 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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-FHM_ERROR: SSM Feature Handler Manager Error - %s.Explanation A feature handler manager error 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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-INVALID_HANDLE: Segment Manager Error - Invalid [chars] handle - [dec].Explanation The connection manager encountered an invalid handle.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-INVALID_SEGMENT: Segment Switch Manager Error - Invalid segment - [chars].Explanation The segment switch manager encountered an invalid segment.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-SM_ERROR: Segment Manager Error - [chars].Explanation An error has occurred in the segment manager.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_MGR-3-SSM_SEG_ISSU: SSM Segment ISSU: [chars] not supported.Explanation ISSU of this SSM Segment is not supported.
Recommended Action Not Available.
SW_VLAN Messages
This section contains Virtual LAN (VLAN) manager messages.
SW_VLAN-3
Error Message %SW_VLAN-3-UNAVAILABLE: VLAN Manager synchronization failure with Port Manager over %sExplanation Due to lack of ready pool space, the VLAN manager dropped a notification from the Port Manager as indicated by the message.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-3-UNAVAILABLE: VTP protocol code internal error: %sExplanation VTP protocol code encountered an unexpected error will processing configuration request, packet, or timer expiration.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_VLAN-3-VLAN_PM_NOTIFICATION_FAILURE: VLAN Manager synchronization failure with Port Manager over %sExplanation Due to lack of ready pool space, the VLAN manager dropped a notification from the Port Manager as indicated by the message.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_VLAN-3-VTP_PROTOCOL_ERROR: VTP protocol code internal error: %sExplanation VTP protocol code encountered an unexpected error will processing configuration request, packet, or timer expiration.
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://tools.cisco.com/ServiceRequestTool/create, 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.
SW_VLAN-4
Error Message %SW_VLAN-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memoryExplanation VLAN software failed to use VLAN configuration from startup-config file. It will fallback to use the binary VLAN configuration file in non-volatile memory.
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE: VLAN configuration file contained incorrect verification word: 0x%xExplanation The VLAN configuration file read by the VLAN manager did not begin with correct value which would indicate a valid VLAN configuration file. Thus, it has been rejected.
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration file contained unknown file version: %dExplanation The VLAN configuration file read by the VLAN manager contained an unrecognized file version number. (This may indicate an attempt to regress to an older version of the VLAN manager software.)
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-BAD_VLAN_TIMER_ACTIVE_VALUE: Encountered incorrect VLAN timer active value: %sExplanation Due to a software error, a VLAN timer was dectected active when it should have been inactive or inactive when it should have been active.
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-EXT_VLAN_INTERNAL_ERROR: Extended VLAN manager received an internal error %d from %s: %sExplanation An unexpected error code was received by the VLAN Manager from the extended VLAN configuration software.
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-IFS_FAILURE: VLAN manager encountered file operation error: call = %s / file = %s / code = %d (%s) / bytes transfered = %dExplanation The VLAN manager received an unexpected error return from a IOS file system call.
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-STARTUP_EXT_VLAN_CONFIG_FILE_FAILED: Failed to configure extended range VLAN from startup-config. Error %sExplanation VLAN software failed to use extended VLAN configuration from startup-config file. All extended range VLANs configuration will be lost after system boot up.
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-VLAN_ADD_FAIL: Failed to add VLAN [dec] to vlan database: [chars]Explanation The specified VLAN could not be added to the VLAN database. The platform may not allow the addition or there may be insufficient memory to expand the VLAN database.
Recommended Action Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars]Explanation The specified VLANs could not be created. The VLAN manager called a VLAN database routine to create one or more VLANs, but the port manager failed the VLAN creation requests. A possible cause of this error is that the VLANs already exist in the port manager as internal VLANs.
Recommended Action Check the internal VLAN usage by entering the show vlan internal usage command. Unconfigure the feature that occupies the internal VLAN and retry the VLAN creation operation. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-VLANMGR_INVALID_DATABASE_DATA: VLAN MANAGER received bad data of type %s: value %d from function %sExplanation The VLAN manager received invalid data from a VLAN configuration database 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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_VLAN-4-VTP_DB_INVALID_VLANID: Invalid VLAN ID [dec] found in VTP database downloadExplanation An invalid VLAN ID was detected in the VTP database during the download of the VTP configuration file. This condition indicates that the VTP configuration file in NVRAM is corrupted.
Recommended Action Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-VTP_DB_SIZE_CHECK_FAILED: The %s VTP database of length %d cannot be supported by the systemExplanation The VLAN trunking protocol (VTP) database size is larger than the system can support.
Recommended Action Reduce the database size by decreasing the configuration parameters. For example, reduce the size of vlan-names.
Error Message %SW_VLAN-4-VTP_INTERNAL_ERROR: VLAN manager received an internal error %d from vtp function %s: %sExplanation An unexpected error code was received by the VLAN Manager from the VTP configuration software.
Recommended Action Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function %s. Semaphore locked by %sExplanation The VTP database is currently locked by another task and is not available. Users should retry the operation sometime later.
Recommended Action Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: %sExplanation VTP protocol code encountered an unusual diagnostic situation which the user should be made aware of.
Recommended Action Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SW_VLAN-4-VTP_PRIMARY_SERVER_CHG: %e has become the primary server for the %s VTP featureExplanation The primary server status has changed and the indicated device has become the primary server for the indicated VTP feature.
Recommended Action No action is required.
Error Message %SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars]Explanation The VTP database is currently locked by another task and is not available.
Recommended Action Retry the operation later. If this condition 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://tools.cisco.com/ServiceRequestTool/create, 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.
SW_VLAN-6
Error Message %SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].Explanation The VTP domain name was changed through configuration to the name
specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.Recommended Action This is an informational message only. No action is required.
Error Message %SW_VLAN-6-OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.Explanation This message indicates that the VLAN software detected an old version of the VLAN configuration file format. The software was able to interpret the file with no problems but will create files using the new format in the future. The first [dec] is the old version number, and the second [dec] is the new version number.
Recommended Action No action is required.
Error Message %SW_VLAN-6-VTP_MODE_CHANGE: VLAN manager changing device mode from [chars] to [chars].Explanation Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is. [chars] is the VTP device mode. In VTP server mode, the VLAN manager must record each change of VTP configuration and each change of device configuration relating to VTP (such as mode changes, device domain name changes, and password changes) to non-volatile storage using IFS system calls. If a system call fails, the device must spontaneously convert to the VTP client mode. Call failures are usually the result of a hardware failure of the non-volatile storage system, which may require replacement. Other possible causes include software bugs or, in the case of TFTP storage, a transient network or TFTP server failure.
Recommended Action No action is required.
Error Message %SW_VLAN-6-VTP_PRUNING_CHANGE: VTP Operational Pruning [chars].Explanation VTP operational pruning has been enabled or disabled as shown in [chars], due to either an administrative pruning change, a VTP mode change, or VTP configuration propagation. To view the reason for the change, enter the show vtp status command.
Recommended Action No action is required.
SW_SW-VLAN
Error Message %SW_VLAN_RF-3-CREATE_PROCESS: Switch Vlan RF client failed to create %s processExplanation Switch Vlan RF client could not create a process, this will cause bulk sync to fail.
Recommended Action Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
SW_SP-VLAN
Error Message %SW_VLAN-SP-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to %s.Explanation The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.
Recommended Action No action is required.
SW_VLAN_ISSU Messages
This section contains switch VLAN in-service software upgrade (ISSU) messages.
SW_VLAN_ISSU-2
Error Message %SW_VLAN_ISSU-2-GET_BUFFER: Switch Vlan ISSU client failed to get buffer for message. Error: %d (%s)Explanation The switch VLAN ISSU client was unable to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-2-INIT: Switch Vlan ISSU client initialization failed to %s. Error: %d (%s)Explanation The switch VLAN ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SW_VLAN_ISSU-2-SEND_NEGO_FAILED: Switch Vlan ISSU client failed to send negotiation message. Error: %d (%s)Explanation The switch VLAN ISSU client was unable to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-2-SESSION_NEGO: Switch Vlan ISSU client encountered unexpected client nego_done. Error: %d (%s)Explanation An ISSU-compliant client transitions through a series of internal states. The switch VLAN ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-2-SESSION_REGISTRY: Switch Vlan ISSU client failed to register session information. Error: %d (%s)Explanation The switch VLAN ISSU client was unable to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
SW_VLAN_ISSU-3
Error Message %SW_VLAN_ISSU-3-CAP_INVALID_SIZE: Switch Vlan ISSU client capability list is empty.Explanation The switch VLAN ISSU client capability exchange list is empty, which is an invalid condition.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show issu capability entires commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-3-CAP_NOT_COMPATIBLE: Switch Vlan ISSU client capability exchange result incompatible.Explanation Based on the results of the capability exchange, the switch VLAN ISSU client is not compatible with the peer.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-3-INVALID_SESSION: Switch Vlan ISSU client does not have a valid registered session.Explanation The switch VLAN ISSU client does not have a valid registered session.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER: 'Message Type %d' is not supported by Switch Vlan ISSU client at peerExplanation The switch VLAN ISSU client at the peer supervisor is not compatible for this message type. The switch VLAN client will be marked as incompatible with the peer.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-3-MSG_NOT_OK: Switch Vlan ISSU client 'Message Type %d' is not compatibleExplanation The switch VLAN ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-3-MSG_SIZE: Switch Vlan ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)Explanation The switch VLAN ISSU client was unable to calculate the MTU for the specified message. As a result, the client is unable to send the message to the standby device.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-3-SESSION_UNREGISTRY: Switch Vlan ISSU client failed to unregister session information. Error: %d (%s)Explanation The switch VLAN ISSU client was unable to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %SW_VLAN_ISSU-3-TRANSFORM_FAIL: Switch Vlan ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)Explanation The switch VLAN ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the switch VLAN state between the active device and the standby device is not identical.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
SW_VLAN_RF Messages
This section contains switch VLAN redundancy facility (RF) messages.
SW_VLAN_RF-3
Error Message %SW_VLAN_RF-3-CREATE_PROCESS: Switch Vlan RF client failed to create %s processExplanation The switch VLAN redundancy facility (RF) client could not create a process. As a result, bulk synchronization will fail.
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://tools.cisco.com/ServiceRequestTool/create, 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.
SYS Messages
This section contains operating system messages.
SYS--
Error Message %SYS--UNAVAILABLE: Bad pid %d for tty %tExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
SYS-1
Error Message %SYS-1-UNAVAILABLE: CCA Detected System Error, code = %dExplanation CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-1-UNAVAILABLE: System detected OVERTEMPERATURE condition. Please resolve cooling problem immediately!Explanation The environmental monitor detected a high-temperature condition.
Recommended Action Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Call your technical support representative for assistance, if necessary.
Error Message %SYS-1-UNAVAILABLE: Threshold: %s CPU Utilization(Total/Intr) %d%%/%d%%.Explanation CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled.
Recommended Action No action is required.
Error Message %SYS-1-UNAVAILABLE: Threshold: %s CPU Utilization(Total/Intr): %d%%/%d%%, Top 3 processes(Pid/Util): %d/%d%%, %d/%d%%, %d/%d%%Explanation The system is experiencing high CPU usage, possibly from a process that is using too much CPU. This condition demands immediate attention, or packets or calls may be dropped.
Recommended Action Enter the show processes CPU command to determine the CPU hogging process that is causing this condition and, if possible, disable the activity that is causing the CPU hog condition so that CPU utilization is reduced.
SYS-2
Error Message %SYS-2-BAD_BM_ARG: Invalid BM index boolean used as argument ([dec])Explanation An illegal boolean manager index argument was referenced.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-CHUNKPARTIAL: Attempted to destroy partially full chunk, chunk [hex].Explanation A software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %SYS-2-CHUNKSIBLINGDEST: Attempted to destroy a sibling chunk %x (%s).Explanation A software error 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-FAILEDUPDATE: Failed to update Process id: %d in %sExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-IMMORTAL: Attempt to shut down management process [dec] ([chars]).Explanation An attempt was made to shut down the specified management 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://tools.cisco.com/ServiceRequestTool/create, 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, the stack trace, and your pertinent troubleshooting logs.
Error Message %SYS-2-INPUT_GETBUF: Bad getbuffer, bytes= [dec], for interface= [chars]Explanation The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-MMAP: mmap failed for size %d bytes Caller PC 0x%x errno %dExplanation Failed to allocate memory for the requested size.The memory could not be mapped because there is no memory.
Recommended Action This message may indicate either a logic error in the issuing component or it may indicate that a mmap failed to allocatecontiguous memory for the requested size. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-2-NOPID: Process MIB is not aware of Process id: %dExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-NV_BAD_PTR: Bad NVRAM pointer. NV Header values are, nv: %p .textbase: %p .textsize: %d .magic: 0x%X .checksum: 0x%X .system_version: %d .textptr: %p v1_ptr: %p .priv: %pExplanation A pointer corruption in NVRAM caused a failure in accessing the NVRAM.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-STACKMAGIC: Stackmagic corrupted for process %s, stackstart = %x magic = %xExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-STACKMMAP: Stack allocation mmap for IOStasks failedExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-SYSMEMINFO: System Memory: %luK total, %luK used, %luK freeExplanation This is an auxiliary message to several memory-related messages. It provides system memory information usage.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message.
Error Message %SYS-2-UNAVAILABLE: Bad chunk reference count, chunk %x data %x refcount %x alloc pc %x.Explanation An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-2-UNAVAILABLE: Bad chunk reference count, chunk %x data %x.Explanation An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-2-UNAVAILABLE: Bad free magic number in chunk header, chunk %x data %x chunk_freemagic %xExplanation An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent, but there could be a hardware problem with memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-2-UNAVAILABLE: Bad getbuffer, bytes= %dExplanation The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.
Recommended Action When reporting this condition, copy the error message text exactly as it appears; include the associated stack trace; and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Bad getbuffer, bytes= %d, for interface= %sExplanation The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-UNAVAILABLE: Bad magic number in chunk header, chunk %x data %x chunkmagic %x chunk_freemagic %xExplanation An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent, but there could be a hardware problem with memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-2-UNAVAILABLE: Bad parameter (%d) when calling to the allocator utilityExplanation Illegal parameter is used when called to allocator. may represent data some corruption.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Bad pid %d for tty %tExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Bad poolsize returned by the system : %uExplanation System returns a non-optimal pool size. Need to change pool sizes
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Bad refcount in %s, ptr=%x, count=%xExplanation A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero, the data structure is freed. This message indicates that when the count was accessed, it was found to be negative which means that the data structure will not be freed until the system is reloaded.
Recommended Action If this messages recurs, copy it exactly as it appears; include the stack trace; and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Buffer %x already in free pool %sExplanation A block of memory at the indicated location is corrupt and/or has been erroneously freed twice.
Recommended Action If this message recurs, copy it exactly as it appears and the output of 'show buffer address ' for the given address as well as 'show buffer pool dump' for the given pool. Report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Buffer %x found in pool %x, should be in pool %xExplanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Buffer %x linked to itself in free pool %sExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Buffer in list, ptr= %xExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Buffer in list, ptr= %x, caller= %xExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: CCA Detected Logic Error, code = %dExplanation CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-UNAVAILABLE: Can't create process with start address = %xExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Chunk element size is more than 64k for %sExplanation Chunk manager cannot function properly with big chunk elements
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Could not expand chunk pool for %s. No memory availableExplanation There is not enough processor memory left to grow this chunk pool.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Could not find the sibling to allocate memory from. Chunk %s, total free %d inuse %d.Explanation An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-2-UNAVAILABLE: Could not return memory Neutrino via munmap at %lx, size %d errno %dExplanation Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap.
Recommended Action This message may indicate either a logic error in the issuing component or it may indicate that a portion of the memory management structures have been over written. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: EXMEM %d: %sExplanation The requested external memory allocator failed to be initialized. reasons are not clear.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Error noticed in the sibling of the chunk %s, Chunk index : %d, Chunk real max : %dExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Error: %sExplanation A software Error occurred while decompressing the Image. The actual error is within the string of the error message.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SYS-2-UNAVAILABLE: Failed to update Process id: %d in %sExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %SYS-2-UNAVAILABLE: Free a non allocated ptr %x size %d.Explanation Trying to free a memory which not all of it marked as allocated.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Generated configuration not backward compatibleExplanation The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set.
Recommended Action Allow the router to save the configuration using the command set of the current software version, or remove the commands that cannot be saved using the older command set.
Error Message %SYS-2-UNAVAILABLE: INPUTQ set, but no IDB, ptr=%xExplanation This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted.
Recommended Action When reporting this condition, copy the text of the message exactly as it appears; include the associated stack trace; and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Inconsistant counters for chunk : %stotal free %d/%d, total sibs %d/%d, total alloc %d/%dExplanation System returns a non-optimal pool size. Need to change pool sizes
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Invalid BM index boolean used as argument (%d)Explanation An illegal boolean manager index argument was referenced
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Invalid BM nameExplanation An illegal name string was registered with the BM
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Invalid chunk header type %d for chunk %x, data %xExplanation An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-2-UNAVAILABLE: Killing process %s, associated with line %dExplanation A process associated with a tty line was killed by another process. The line may go dead
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Killing process %s, pid %d againExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Low-memory debug exception (limit=%u free=%u)Explanation The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features.
Recommended Action If you suspect a memory leak, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support.
Error Message %SYS-2-UNAVAILABLE: Low-memory debug exception (limit=%u free=%u)Explanation The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features.
Recommended Action If you suspect a memory leak, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support.
Error Message %SYS-2-UNAVAILABLE: Memory allocation of %u bytes failed from %#x, alignment %d Pool: %s Free: %u Cause: %s Alternate Pool: %s Free: %u Cause: %sExplanation The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error may have exhausted or fragmented the router's memory.
Recommended Action If you suspect a software error, copy the error message exactly as it appears on the colsole or in the system log, contact your technical supportrepresentative,and provide the representative with the gathered information. Otherwise, you may need to add more memory or reduce the number of features you are trying to support.
Error Message %SYS-2-UNAVAILABLE: Memory fragmentation check debug exception (fragment size %u)Explanation The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features.
Recommended Action If you suspect memory thrashing, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support.
Error Message %SYS-2-UNAVAILABLE: Memory fragmentation check debug exception (fragment size %u)Explanation The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features.
Recommended Action If you suspect memory thrashing, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support.
Error Message %SYS-2-UNAVAILABLE: Memory requested from Null ChunkExplanation Chunk manager cannot allocate memory from NULL chunks
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Message from %t(%s): %sExplanation A user has used the 'send log' command to include a message on theconfigured logging destinations. Such messages can be used to helptag where user-initiated events occur during debugging.
Recommended Action This message is informational only.
Error Message %SYS-2-UNAVAILABLE: Multiple Signals are sent to a process %dExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: No memory available for %s %dExplanation An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory.
Error Message %SYS-2-UNAVAILABLE: No such process %dExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Process %s has trashed stack, old size %dExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Process MIB is not aware of Process id: %dExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %SYS-2-UNAVAILABLE: Process aborted on invalid signal, signum = %d.Explanation An attempt was made to send an invalid signal to another process.
Recommended Action If this message occurs more than once, report this message to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Process aborted on watchdog timeout, process = %s.%sExplanation The indicated process ran for too long without relinquishing control. The system killed it as a runaway process.
Recommended Action This message may be realted to a combination of system load and configuration. When reporting this message, copy the message text exactly as it appears; include the stack trace; and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Process creation of %s failed (at level %d).Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Process creation of %s failed (no memory).Explanation Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak.
Recommended Action A memory leak may be the cause if the system has been running for a while without changing its configuration. If you suspect a leak, then copy this message exactly as it appears and report it to your technical support representative. Otherwise, ensure that more memory is available to support the additional features.
Error Message %SYS-2-UNAVAILABLE: Regular expression access check with bad list %dExplanation This message indicates that a pointer to an access list is invalid.
Recommended Action The event that caused this message to be issued should not have occured. It can mean that one or more data structures have been overwritten. If this message recurs, and you decide to report it to your technical representative, you should copy the text of the message exactly as it appears and include the associated stack trace. Since access list corruption may have occurred, a technical representative should verify that access lists are functioning corectly.
Error Message %SYS-2-UNAVAILABLE: Root chunk need to be specified for %xExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Stack allocation mmap for IOStasks failedExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Stackmagic corrupted for process %s, stackstart = %x magic = %xExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: System Crashed, Writing Core....Explanation The system has crashed because of an exception, A core is being generated
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-2-UNAVAILABLE: System Memory: %luK total, %luK used, %luK freeExplanation This is an auxiliary message to several memory-related messages. It provides system memory information usage.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message.
Error Message %SYS-2-UNAVAILABLE: Task hung with blocking disabled, value = 0x%x.Explanation The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled.
Recommended Action This message may be a result of high loads. If it recurs, copy the text exactly as it appears and report it, along with the associated stack trace to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: Trying to set unknown special character %d to %dExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: mmap failed for size %d bytes Caller PC 0x%x errno %dExplanation Failed to allocate memory for the requested size.The memory could not be mapped because there is no memory.
Recommended Action This message may indicate either a logic error in the issuing component or it may indicate that a mmap failed to allocatecontiguous memory for the requested size. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-2-UNAVAILABLE: pthread_mutex_lock failed for %sExplanation The thread failed in pthread_mutex_lock while trying to acquire a mutex.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SYS-3
Error Message %SYS-3-BADRESID: Clock hardware returned bad residual [dec].Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-CHUNK_NO_EXMEM: No handler to [chars] external memory.Explanation An attempt was made to allocate or free a chunk of external memory, but no handler for managing external memory was registered.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-3-INVMEMPID: Invalid pid %d in block: %xExplanation There has been attempt to allocate memory on behalf of an invalid 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-3-LOGGER_DROPPED: System dropped %d console debug messages.Explanation Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages.
Recommended Action Consider using conditional debugging or turning off console logging.
Error Message %SYS-3-MEMSEMFAIL: Mempool semaphore creation failed for [chars]Explanation Semaphore creation for the specified memory pool has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-3-PREEMPTSUSP: Suspending a preemptive process [chars]Explanation A preemptive process attempted a suspend, which is not allowed because they are expected to finish their work as quickly as possible and go back to idle queue.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-3-PROCSEMFAIL: Process semaphore creation for preemptive processes failed.Explanation Creation of a process function semaphore to protect the critical section of the process create routine has failed. The semaphore creation can fail if there is not enough chunk memory to create the event structure.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-3-UNAVAILABLE: Cannot start timer (%#x) with negative offset (%d).Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Clock hardware returned bad residual %d.Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Corrupt block at %x (magic %08x)Explanation The free memory pool is corrupt.An inconsistensy was detected in the free memory pool.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-3-UNAVAILABLE: Corrupt free block at %x (magic %08x)Explanation A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.
Error Message %SYS-3-UNAVAILABLE: Couldn't add process process pid %d to resource group %x, Cause: %sExplanation An attempt to create a resource group failed at the indicatedlocation
Recommended Action This message may indicate either a logic error in the issuing component or may be due to a low memory condititon as specified in theCause. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Couldn't delete process process pid %d from resource group Cause: %sExplanation An attempt to remove a process from a resource group failed atthe indicated location
Recommended Action This message indicates a logic error in the issuing component When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Couldn't destroy resource group %x, Cause: %sExplanation An attempt to destroy a resource group failed at the indicated location
Recommended Action This message indicates a logic error in the issuing component When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Crashinfo subsys initialization did not add registry crashinfo_get_default_file_name.Explanation In order to figure out the device which the crashinfo writes to, the crashinfo subsys has to add the registry crashinfo_get_default_file_name.
Recommended Action Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem. This SHOULD never happen - it is an indication of a bug elsewhere in the code.
Error Message %SYS-3-UNAVAILABLE: Failed to parse boot command:%s Error:%dExplanation Boot configuration failed to parse when copied to startup-config.Most likely reason would be syntax errors in the boot configuration.
Recommended Action Decode the traceback and check configuration file for the boot commands. Boot commands are sandwiched between boot-start-marker and boot-end-marker
Error Message %SYS-3-UNAVAILABLE: Function %s: value %#x passed in parameter %sExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Illegal printing attempt from interrupt level.Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Invalid memory action (%s) at interrupt levelExplanation This message indicates that a memory allocation or deallocation was attempted from an interrupt handler.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Invalid pid %d in block: %xExplanation There has been attempt to allocate memory on behalf of an invalid process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and look up the message in the Bug Toolkit at: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you are unable to resolve the issue using Bug Toolkit, please copy the text of the message exactly as it appears; include the stack trace, any additonal related failure data and the output of the command show tech-support and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Mempool semaphore creation failed for %sExplanation This message indicates that the semaphore creation for the specified mempool failed.
Error Message %SYS-3-UNAVAILABLE: No handler to %s external memory.Explanation An attempt was made to allocate or free a chunk of external memory, but no handler for managing external memory was registered.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: No space remaining to save private configExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Nonvolatile storage write error; configuration failedExplanation The write of the nonvolatile configuration failed.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Null IDB in %sExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Overflow in %s, chars %d, buffer size %dExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Process %s top-level routine exitedExplanation An internal software error occurred
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Process has no associated tty (in %s).Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Process semaphore creation for preemptive processes failed.Explanation Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure.
Error Message %SYS-3-UNAVAILABLE: Questionable reset of process %d on tty%tExplanation A process was reset without giving it a chance to clean itself up.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Removed a non-empty list(%x, name: %s), having %lu elementsExplanation A non-empty list should not be destroyed. If it happens, there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-3-UNAVAILABLE: Requested memory thresholding operation on resource group failed Resource Group handle: %x, Cause: %sExplanation The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location
Recommended Action This message indicates a logic error in the issuing component asspecified in the Cause. When reporting this message, copy thetext exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Resource group creation failed, Cause: %sExplanation An attempt to create a resource group failed at the indicated location
Recommended Action This message may indicate either a logic error in the issuing component or may be due to a low memory condititon. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Same tty%t in linewatch_timers, type %dExplanation A tty appeared twice in a timer list where it should have only appeared once.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Storing of console terminal control settings failedExplanation This occurs during console initialization, the retrieving and storing ofconsole terminal control settings soon after initialization fails
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: System cannot release chunk memory.Explanation The system was not able to destroy a previously allocated chunk of memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: System dropped %d console debug messages.Explanation Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages.
Recommended Action Consider using conditional debugging or turning off console logging.
Error Message %SYS-3-UNAVAILABLE: System pausing to ensure console debugging output.Explanation Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen, the rest of the system is paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link.
Recommended Action Consider using conditional debugging, turning off console logging, or using the o logging console guaranteed command, or turning off link-state messages for some interfaces
Error Message %SYS-3-UNAVAILABLE: System reloading, unable to complete startup configuration updateExplanation Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-3-UNAVAILABLE: System running-config write error; configuration failedExplanation The write of the system running configuration failed.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: System was paused for %TE to ensure console debugging output.Explanation Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen, the rest of the system was paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link.
Recommended Action Consider using conditional debugging, turning off console logging, or using the o logging console guaranteed command, or turning off link-state messages for some interfaces
Error Message %SYS-3-UNAVAILABLE: TTY%t: Managed Timer(s) %s still runningExplanation One or more managed timers for a TTY that is deleted are still running.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYS-3-UNAVAILABLE: Task is running for (%d)msecs, more than (%d)msecs (%d/%d),process = %s.%sExplanation The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load, hardware or operational configuration, a configuration change, initialization (of many interfaces, cards or ports for example), a high momentary error rate, a sustained abnormal condition or many other conditions.
Recommended Action If you suspect a software error, copy the error message exactly as it appears on the colsole or in the system log, contact your technical supportrepresentative, and provide the representative with the gathered information.
Error Message %SYS-3-UNAVAILABLE: Timer callback ran long, PC = %x.Explanation The indicated callback routine ran for too long without relinquishing the processor.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Unknown socket protocol %dExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: Unknown stack. Process: %sExplanation An internal error occurred when running the garbage detector
Recommended Action Copy the error message exactly as it appears on the console or in the system log and look up the message in the Bug Toolkit at: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you are unable to resolve the issue using Bug Toolkit, please issue a show tech and contact your technical support representative with the gathered information.
Error Message %SYS-3-UNAVAILABLE: Unknown stack. Process: %sExplanation An internal error occurred when running the memory leak detector
Recommended Action Copy the error message exactly as it appears on the console or in the system log and look up the message in the Bug Toolkit at: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you are unable to resolve the issue using Bug Toolkit, please issue a show tech and contact your technical support representative with the gathered information.
Error Message %SYS-3-UNAVAILABLE: Variable %s not set properly in the routine %s.Explanation The write of the nonvolatile configuration failed because an internal variable was not set properly.
Recommended Action If this messages occurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: cannot open file for reading '%s'Explanation The URL for the cannot be opened for reading.
Recommended Action Check for proper Uniform Resource Locator syntax and for read permission and retry.
Error Message %SYS-3-UNAVAILABLE: cannot set TCL interpreter variable '%s' to '%s' : '%s'Explanation The value could not be passed to the TCL interpreter
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: heap timer at 0x%x has not been initializedExplanation A heap timer has not been initialized
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: heap timer at 0x%x in state %dExplanation A heap timer has not been initialized
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-3-UNAVAILABLE: redirection url write failed '%s'Explanation Redirection of output to URL failed.
Recommended Action Check for free space on destination URL and retry.
Error Message %SYS-3-UNAVAILABLE: timer heap at 0x%x needed to expand, but hasn'tExplanation A timer heap should have expanded, but has not
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SYS-4
Error Message %SYS-4-UNAVAILABLE: %s while processing the input regular expression. Aborting processing, use alternate regular expression. Input regular expression: %sExplanation Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload.
Recommended Action The regular expression specified leads to stack overflow/processing timeout of the indicated process. Recommended to use a different regular expression.
Error Message %SYS-4-UNAVAILABLE: %s%s is seeing %s cpu util %u%% at %s level more than the configured %s limit %u %%Explanation The system is experiencing high CPU usage, possibly from a process that is using too much CPU. This condition demands immediate attention, or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification.
Recommended Action No action is required
Error Message %SYS-4-UNAVAILABLE: %s.Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-4-UNAVAILABLE: An nvram checksum is already in progressExplanation User attempted multiple nvram operations at the same time. If not at interrupt, the system will attempt the nvram operation again.
Recommended Action Nothing - unless the command fails; in which case, the command needs to be attempted again.
Error Message %SYS-4-UNAVAILABLE: An nvram checksum is already in progress; the nvram checksum from interrupt cannot be servicedExplanation An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use.
Recommended Action Nothing - unless the command fails; in which case, the command needs to be attempted again.
Error Message %SYS-4-UNAVAILABLE: Attempt via SNMP failed, system shutdown not configuredExplanation SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-4-UNAVAILABLE: Configuration from version %d.%d may not be correctly understoodExplanation The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version.
Recommended Action Examine all the messages printed while the router was booting. For each message about an unknown command, determine whether that feature is required. If so, upgrade to a newer version of software that supports that feature.
Error Message %SYS-4-UNAVAILABLE: Configuration needs to be truncated to fit into nvramExplanation The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration
Recommended Action Save the configuration to flash if the platform supports boot config nvbypass command.
Error Message %SYS-4-UNAVAILABLE: External memory allocation of %d bytes failed from EXMEM %dExplanation The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-4-UNAVAILABLE: Free Memory has dropped below low watermark Pool: %s Free: %lu freemem_lwm: %luExplanation The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit.
Recommended Action No action is required
Error Message %SYS-4-UNAVAILABLE: Non config data present at the end of nvram is corruptedExplanation The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload.
Recommended Action Compress the configurtion and store or copy to flash as appropriate
Error Message %SYS-4-UNAVAILABLE: Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvramExplanation The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload.
Recommended Action Compress the configurtion and store or copy to flash as appropriate
Error Message %SYS-4-UNAVAILABLE: Running invalid image for platform!Explanation The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003, Cisco 1004, or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005.
Recommended Action Install the correct software image.
Error Message %SYS-4-UNAVAILABLE: SNMP WriteNet request. Writing current configuration to %iExplanation SNMP is writing the current configuration to a network host.
Recommended Action These are notification messages only. No action is required.
Error Message %SYS-4-UNAVAILABLE: SNMP hostConfigSet request. Loading configuration from %iExplanation SNMP is reading the host configuration from a network host.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-4-UNAVAILABLE: SNMP netConfigSet request. Loading configuration from %i.Explanation SNMP is reading the network configuration from a network host.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-4-UNAVAILABLE: SNMP system message request %d denied because of pending jobExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-4-UNAVAILABLE: System config parse from (%s) failedExplanation The configuration file from the URL specified in the error message could not be read.
Recommended Action Enter the no service config command to disable autoloading of configuration files OR investigate why the tftp load is failing.
Error Message %SYS-4-UNAVAILABLE: The configuration could not be lockedExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %SYS-4-UNAVAILABLE: Truncated configuration to %ld bytes from %ld bytesExplanation The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration.
Recommended Action Save the configuration to flash if the platform supports boot config command.
Error Message %SYS-4-UNAVAILABLE: Unable to initialize the geometry of nvramExplanation The software detected that it failed to initialize the nvram block geometry, a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature, could not find the minimum room in the nvram to initialize block file system.
Recommended Action Reduce the configurations in the nvram atleast by 2K
Error Message %SYS-4-UNAVAILABLE: Update to memory leak detector on free of 0x%x failed, CLI output is unreliableExplanation managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false.
Recommended Action Ignore the output of show memory debug leaks.. if system is in low memory condition else perform a bug toolkit search on the web for existing bugs related to this error message, if none found, contact TAC for this problem providing show version and show memory statistics output.
Error Message %SYS-4-UNAVAILABLE: sanity check failed for string %sExplanation The owner of this string must have freed their structure without letting the string database know
Recommended Action No action is required
SYS-5
Error Message %SYS-5-UNAVAILABLE: Scheduled reload cancelled at %sExplanation A scheduled reload that was requested for the router has been cancelled.
Recommended Action No action is required.
Error Message %SYS-5-UNAVAILABLE: %s table %s damaged: %s.Explanation An internal table entry became corrupt.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %SYS-5-UNAVAILABLE: Configuration file %s accepted, aborting setupExplanation A configuration was accepted over the network, so the setup session will be aborted.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: Configured from %sExplanation The router's configuration was changed.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: Configured from %s by %sExplanation The router's configuration was changed.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: Flow-control threshold on module %d has exceeded the default value. Threshold will be set to lower valueExplanation The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default, the value is set to new (lower) value
Recommended Action LOG_STD_NO_ACTION
Error Message %SYS-5-UNAVAILABLE: Free Memory has recovered above low watermark Pool: %s Free: %lu freemem_lwm: %luExplanation The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit.
Recommended Action No action is required
Error Message %SYS-5-UNAVAILABLE: Nonvolatile storage configured from %sExplanation The configuration was written successfully.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: Nonvolatile storage configured from %s by %sExplanation The configuration was written successfully.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: Privilege level set to %d by%s%sExplanation The privileged mode is enabled or the privilege level is changed; therefore, the associated , and information will be logged.
Recommended Action This is a notification message only. No action is required. To disable this particular logging feature, issue the no logging userinfo command from the global configuration mode.
Error Message %SYS-5-UNAVAILABLE: Reload requested for %sExplanation A scheduled reload has been requested for the router.
Recommended Action No action is required.
Error Message %SYS-5-UNAVAILABLE: Reload requested%sExplanation A reload or restart was requested.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: Switchover requestedExplanation A switchover was requested.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: Switchover requested%sExplanation A switchover was requested.
Recommended Action This is a notification message only. No action is required.
Error Message %SYS-5-UNAVAILABLE: System restarted -- %sExplanation A reload or restart was requested.
Recommended Action This is a notification message only. No action is required.
SYS-6
Error Message %SYS-6-UNAVAILABLE: %#x: %#x %#x %#x %#xExplanation This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Error Message %SYS-6-UNAVAILABLE: %d queue error messages have been droppedExplanation Some queue error messages were dropped due to message buffer full.
Recommended Action This is an informational message. There should have been other queue related error messages before this one. Report those earlier messages to your technical support represenatative.
Error Message %SYS-6-UNAVAILABLE: %s %s.Explanation A configured boot system command failed.
Recommended Action If a system image was eventually loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative.
Error Message %SYS-6-UNAVAILABLE: %s packet %x has a zero reference count, freeing pid = %x, freeing pc = %x %s.Explanation Provides additional information about original freer of packet.
Recommended Action If this messages recurs, copy it exactly as it appears; include the stack trace; and report it to your technical support representative.
Error Message %SYS-6-UNAVAILABLE: %s%s is no longer monitoring %s cpu at %s level for the configured %s limit.Explanation CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked.
Recommended Action No action is required
Error Message %SYS-6-UNAVAILABLE: %s%s is no longer seeing %s high cpu at %s level for the configured %s limit %u%%, current value %u%%Explanation CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled.
Recommended Action No action is required
Error Message %SYS-6-UNAVAILABLE: %s: addr, pc ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPCExplanation This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message.
Error Message %SYS-6-UNAVAILABLE: %sblk %x, words %u, alloc %x, %s, dealloc %x, rfcnt %xExplanation This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Error Message %SYS-6-UNAVAILABLE: Bridging software not presentExplanation Your system is not configured to be a bridge.
Recommended Action Configure the bridging software.
Error Message %SYS-6-UNAVAILABLE: Logging of buginf debugs was %sExplanation All calls to debugging have been disabled in Cisco IOS software as a result the user entering the no logging buginf command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor (CPU hog condition). This condition differs from the use of the undebug all command in that all debugging calls have been disabled in the Cisco IOS software. No debug reporting is available, even if debugging is enabled. Note that even though debugging has been completely disabled in the system, other message reporting, including error reporting, is still available.
Recommended Action This is an informational message only. No action is required.
Error Message %SYS-6-UNAVAILABLE: Logging to host %s%s%s%sExplanation Syslog logging to specified server or host(vrf) has started or stopped
Recommended Action LOG_STD_NO_ACTION
Error Message %SYS-6-UNAVAILABLE: Messages above this line are from the boot loader.Explanation At least one informational or error message was printed by the boot loader.
Recommended Action If the system image was loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative.
Error Message %SYS-6-UNAVAILABLE: Process %s just finished executingExplanation This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.
Recommended Action Copy this messages exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative.
Error Message %SYS-6-UNAVAILABLE: Reserve memory is being createdExplanation A portion of memory is reserved exclusively for console
Recommended Action The console access is made available even in low memory condition. User can collect the details like tech-support for further diagnosis
Error Message %SYS-6-UNAVAILABLE: Reserve memory is being usedExplanation The reserved memory is being used by the console
Recommended Action The system is low in memory. The reserved memory will be used only by the console process. Please take a techsupport so that the reason for low memory can be found
Error Message %SYS-6-UNAVAILABLE: Scheduler test %#x (for %s) just executedExplanation This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.
Recommended Action Copy this message exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative.
Error Message %SYS-6-UNAVAILABLE: Stack for %s %s running low, %d/%dExplanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message %SYS-6-UNAVAILABLE: System clock has been updated from %s to %s, configured from %s by %s.Explanation This message indicates that the system clock has been modified.
Recommended Action This is informational message.
Error Message %SYS-6-UNAVAILABLE: Time since last reboot not availableExplanation This is an informational message for the user. The time taken for the router to come up after OIR is not available.
Recommended Action No action required.
Error Message %SYS-6-UNAVAILABLE: Time taken to reboot after reload = %-4d secondsExplanation This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set, and router is in rommon for a long time, then the reload time shown could be large.
Recommended Action No action required.
Error Message %SYS-6-UNAVAILABLE: boot system %s command is skippedExplanation A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried
Recommended Action Replace the failed boot system image with a good one. There could be various reasons that this specified image failed, for example the image might be with a bad checksum.
SYS-7
Error Message %SYS-7-UNAVAILABLE: ESM shutdownExplanation The Embedded Syslog Manager has been shut down
Recommended Action LOG_STD_NO_ACTION
Error Message %SYS-7-UNAVAILABLE: Initialized the geometry of nvramExplanation Initialized the nvram block geometry, a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload.
SYS-SP
SYS-SP-3
Error Message %SYSCTLR-3-UNAVAILABLE: Health monitoring setup failed on shelf_id %dExplanation Health monitor failed to setup the monitoring command on that particular shelf
Error Message %SYSCTLR-3-UNAVAILABLE: Invalid parameter/mangled pointer routine: %s, file: %s, line: %dExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %SYSCTLR-3-UNAVAILABLE: No context associated with the expired SDP timerExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %SYSCTLR-3-UNAVAILABLE: SDP packet received by system controller containted invalid version number.Explanation Check that shelf is running compatible version of SDP
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %SYSCTLR-3-UNAVAILABLE: SDP packet with duplicate shelf-id %d received from %s,already discovered shelf located at %sExplanation Two shelves with same shelf-id are configured in the system.
Recommended Action Change the shelf-id for one of the shelf.
Error Message %SYSCTLR-3-UNAVAILABLE: Shelf id protocol errorExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %SYSCTLR-3-UNAVAILABLE: Unable to send message %d to process with pid %d.Explanation Most likely the performance collector process has terminated.
Error Message %SYSCTLR-3-UNAVAILABLE: socket bind failedExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message %SYSCTLR-3-UNAVAILABLE: socket open failedExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message SYSCTLR-4%SYSCTLR-4-UNAVAILABLE: Configuration for the shelf %d located %i changedExplanation SDP protocol on system controller has detected that a particular shelf configuration has changed.
Error Message %SYSCTLR-4-UNAVAILABLE: Hello packet from shelf %d not received, shelf removed.Explanation No SDP hello packets were received from the particular shelf, this could indicate that particular router shelf is down or is mis-configured.
Error Message %SYSCTLR-4-UNAVAILABLE: Local time %s %s on shelfid %d is not active, resetting monitor_type %dExplanation Health monitor setup commands polling information. If you see this message shows up every ten minutes, that means health monitor is not able to set that corresponding entry on that shelf.
Error Message %SYSCTLR-4-UNAVAILABLE: Shelf %d located %i reloadedExplanation SDP protocol on system controller has detected that a particular shelf has reload.
Error Message %SYSCTLR-4-UNAVAILABLE: Shelf %d located at address %i removed.Explanation SDP protocol on system controller didn't receive hello packets from particular shelf.
Error Message %SYSCTLR-4-UNAVAILABLE: Shelf %d not reachable via SNMPExplanation Shelf indicated above is not responding to SNMP requests.
Recommended Action Check the snmp configuration for the above shelf and also check correct community string is specified in configuration command system-controller community on the system controller.
SYSCTLR-5
Error Message %SYSCTLR-5-UNAVAILABLE: MD5 digest does not match, SDP packet received from, %i rejectedExplanation A SDP hello packet was received from shelf, which is not trusted.
Recommended Action Either specify the correct SDP password and/or destination on the shelf from which this message was received.
SYSCTLR-6
Error Message %SYSCTLR-6-UNAVAILABLE: Communication with shelf %d located at address %iExplanation SDP protocol on system controller has detected a particular shelf.
Error Message %SYSCTLR-6-UNAVAILABLE: Found Shelf %d with an invalid IP address %sExplanation System Controller found a Shelf with an invalid ip address
Recommended Action Check the IP address set on the Shelf
Error Message %SYSCTLR-6-UNAVAILABLE: Shelf %d discovered located at address %iExplanation SDP protocol on system controller has detected a particular shelf.
SYSLOGD Messages
This section contains system logging (SYSLOG) messages.
SYSLOGD-3
Error Message %SYSLOGD-3-DROPPED_MESSAGES: A total of [int] messages have been dropped by the syslog daemon, due to [chars]Explanation The syslogd process has dropped received messages. The syslogd process may be receiving too many messages to process before the buffer fills, or it may have received a message for which there was insufficient memory available. In either case, there may be a bug in the sending 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://tools.cisco.com/ServiceRequestTool/create, 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.
SYSLOG_SERVER-3
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Failed to add Syslog file %s, maximum Syslog files %d.Explanation Exceeded the maximum Syslog files allowed.
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Failed to create a Syslog file.Explanation Failed to create a Syslog file.
Recommended Action There is probably no PCMCIA disk on slot0 on the System Controller. Please check to see if it is not a PCMCIA Flash
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Failed to open %s.%d syslog file.Explanation Failed to open a syslog file.One or more of the subfiles may have been deleted or there is no PCMCIA disk
Recommended Action You may not be having a PCMCIA disk in slot0 on the System Controller. Please check to see if it is not a PCMCIA Flash. If one or more of the subfiles is missing, then they will be automatically restored when the current file reaches its capacity and gets archived
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Failed to read a file.Explanation Failed to read a file.
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Failed to write a syslog file.Explanation Failed to write a syslog file.
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Illegal file system %s.Explanation Illegal file system.
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Parsing file error.Explanation The Router is not configured to timestamp all the log messages
Recommended Action Please configure your router with appropriate commands to timestamp the log messages. Eg: service timestamps
Error Message %SYSLOG_SERVER-3-UNAVAILABLE: Unknown command or device name, or unable to find device address.Explanation Unknown command or device name, or unable to find device address.
SYSLOG_SERVER-4
Error Message %SYSLOG_SERVER-4-UNAVAILABLE: No configuration change.Explanation There is no configuration change to the syslog-server
Error Message %SYSLOG_SERVER-4-UNAVAILABLE: No memory left.Explanation No memory left.
Recommended Action The System Controller is running very low on memory.
Error Message %SYSLOG_SERVER-4-UNAVAILABLE: No syslog file.Explanation No syslog file.
Error Message %SYSLOG_SERVER-4-UNAVAILABLE: Syslog file [%s] exists.Explanation You may have issued a directory name that already exists on the PCMCIA disk.
Recommended Action Please check to see if the directory name you supplied already exists on the PCMCIA disk and re-enter a different one
Error Message %SYSLOG_SERVER-4-UNAVAILABLE: syslog records do not appear to be timestamped.Explanation This may be a result of not turning the service timestamp command.
Recommended Action Please turn the service timestamps log datetime command on your router. This will cause the system to timestamp debugging or logging messages.Use atleast datetime.
SYSMGT_RPC-3
Error Message %SYSMGT_RPC-3-UNAVAILABLE: SYSMGT RPC - IPC %s %s failed (%s)Explanation System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSMGT_RPC-3-UNAVAILABLE: SYSMGT RPC - NETMGT Event: %s (%d)Explanation System Management Remote Procedure Call Network management event error detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSMGT_RPC-3-UNAVAILABLE: SYSMGT RPC - RPC %s %s failed (%s %d)Explanation System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
SYSMGR Messages
This section contains system manager messages.
SYSMGR-3
Error Message %SYSMGR-3-ABNORMTERM: [chars]:[dec] (jid [dec]) abnormally terminated, [chars]Explanation A process was abnormally terminated.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSMGR-3-ERROR: [chars]:[dec] (jid [dec]) [chars] ([chars])Explanation The system manager server has encountered an error condition.
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://tools.cisco.com/ServiceRequestTool/create, 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.
SYSMGR-6
Error Message %SYSMGR-6-ERROR_EOK: [chars]:[dec] (jid [dec]) [chars]Explanation The system manager server has encountered an error condition.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSMGR-6-RESTART: Restarting process [chars] by [chars]Explanation A process was restarted through the CLI.
Recommended Action This is an informational message only. No action is required.
SYSMGR_PLATFORM Messages
This section contains Cisco Catalyst 6000 system manager process messages.
SYSMGR_PLATFORM-5
Error Message %SYSMGR_PLATFORM-5-WAIT_RP: Waiting RP to complete crashinfo and core file collectionExplanation Sysmgr.proc process is waiting for the RP to signal the end of crashinfo or core file collection.
Recommended Action This is an informational message only. No action is required.
SYSTEM_BUS_ASIC Messages
This section contains System Bus Translator ASIC messages.
SYSTEM_BUS_ASIC-3
Error Message %SYSTEM_BUS_ASIC-3-INTR_FATAL: SYSTEM BUS ASIC [dec]: recoverable interrupt [chars]Explanation The System Bus Translator ASIC detected an unexpected interrupt condition. This message indicates a hardware failure or malfunction. The system will reload to fix the problem.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSTEM_BUS_ASIC-3-INTR_RECOVERY: SYSTEM BUS ASIC [dec]: recoverable interrupt [chars]Explanation The System Bus Translator ASIC detected an unexpected interrupt condition.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSTEM_BUS_ASIC-3-INTR_RESET: SYSTEM BUS ASIC [dec]: was resetExplanation The System Bus Translator ASIC was reset as part of the system recovery sequence.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSTEM_BUS_ASIC-3-INTR_STATS_RECOVERY: SYSTEM BUS ASIC [dec]: Recoverable Interrupt warning [chars]Explanation The System Bus Translator ASIC detected an unexpected condition in the statistics collection module.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSTEM_BUS_ASIC-3-INTR_WARN: SYSTEM BUS ASIC [dec]: Non-fatal Interrupt warning [chars]Explanation The System Bus Translator ASIC detected an unexpected nonfatal condition.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSTEM_BUS_ASIC-3-INTR_WARN_TYPE2: SYSTEM BUS ASIC [dec]: Non-fatal interrupt Warning [chars] error code [dec]Explanation The System Bus Translator ASIC detected an unexpected nonfatal condition.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSTEM_BUS_ASIC-3-KUMA_INTR_THROTTLED: SYSTEM BUS ASIC %d: Kuma interrupts throttledExplanation The system bus translator ASIC detected too many interrupts. To avoid performance degradation, the system has temporarily masked interrupts.
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://tools.cisco.com/ServiceRequestTool/create, 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 %SYSTEM_BUS_ASIC-3-KUMA_INTR_UNTHROTTLED: SYSTEM BUS ASIC %d: Kuma interrupts unthrottledExplanation The system has unmasked the interrupts that were masked temporarily.
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://tools.cisco.com/ServiceRequestTool/create, 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.
SYSTEM_CONTROLLER Messages
This section contains system controller messages.
SYSTEM_CONTROLLER-3
Error Message %SYSTEM_CONTROLLER-3-COR_MEM_ERR: Correctable DRAM memory error. Count [dec], log [hex]Explanation A transient DRAM memory error was detected and corrected.
Recommended Action If the error message appears infrequently, no action is required. If the message recurs, reseat the SDRAM SIMM on the supervisor engine. If errors persist, replace the SIMM. If the errors continue after the SIMM is replaced, the supervisor engine may need to be replaced.
Error Message %SYSTEM_CONTROLLER-3-ERROR: Error condition detected: [chars]Explanation The most common errors from the Mistral ASIC on the MSFC are TM_DATA_PARITY_ERROR, SYSDRAM_PARITY_ERROR, SYSAD_PARITY_ERROR, and TM_NPP_PARITY_ERROR. Possible causes of these parity errors are random static discharge or other external factors.
Recommended Action If the error message appears only once (or rarely), monitor the system log to determine whether the error message was an isolated incident. If the message recurs, check the environmental conditions for problems such as power brownouts, static discharges, or strong EMI fields. If these environmental conditions are within normal ranges and the error continues to appear, the supervisor engine may need to be replaced.
Error Message %SYSTEM_CONTROLLER-3-EXCESSIVE_RESET: System Controller is getting reset so frequentlyExplanation The MISTRAL ASIC is being reset frequently. The usual cause is an improperly seated module or another hardware condition.
Recommended Action Power down and reseat the module. If the problem 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %SYSTEM_CONTROLLER-3-INVALID_EARL_HANDLER: EARL interrupt handler is not validExplanation The EARL interrupt handler 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://tools.cisco.com/ServiceRequestTool/create, 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 %SYSTEM_CONTROLLER-3-MISTRAL_RESET: System Controller is reset:Normal Operation continuesExplanation The system controller is being reset. Operation will continue, but the message rate will be limited.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TAC Messages
This section contains TACACS system messages.
TAC-3
Error Message %TAC-3-SERVCONF: Server config failure: [chars]Explanation The server configuration failed.
Recommended Action Please configure the server properly.
Error Message %TAC-3-SERVINT: [chars]Explanation This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %TAC-3-SERVNO: Server [chars] is not configuredExplanation The server is not configured.
Recommended Action Please configure a server before un-configuring it.
Error Message %TAC-3-XTACACL: %s: accesslist 0x%x out of range for %sExplanation The TACACS facility created a message that contains an accesslist which is not a valid accesslist (out of bounds).
Recommended Action If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
TAC-4
Error Message %TAC-4-NOTIMEOUT: Warning: This command has been deprecated in favor of the line-command timeout login responseExplanation This command is deprecated, and should no longer be used. Instead, the line-command timeout login response now provides this functionality
Recommended Action Use the line-command timeout user-response
Error Message %TAC-4-SERVREFNAME: Warning: Server [chars] is still referenced by server group.Explanation The server being removed is still referenced by a server group.
Recommended Action Please dereference the server from the server group as soon as possible.
Error Message %TAC-4-UNEXREP: Reply for non-existent request, %d on queueExplanation The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. It also may be due to an internal software problem.
Recommended Action If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
TAC-6
Error Message %TAC-6-SENDTMO: Send type %d to %i timed outExplanation A background TACACS notification (enabled with the command tacacs notify) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server. This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.
Recommended Action Check the TACACS server and the network attached to it.
Error Message %TAC-6-SENDTMO: Send type %d to %i timed outExplanation A background TACACS notification (enabled with the command tacacs notify) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server. This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.
Recommended Action Check the TACACS server and the network attached to it.
Error Message %TAC-6-SERVDEP: tacacs-server host CLI will be deprecated soon. Please move to tacacs server CLIExplanation Migration from tacacs-server host CLI to tacacs server CLI.
Recommended Action Please try to use the new CLI.
TAGCON-3
Error Message %TAGCON-3-UNAVAILABLE: %i/%i, %sExplanation A problem was encountered in clean up following termination of a Tag Distribution Protocol (TDP) session.
Recommended Action ACTION_COPY_REPORT_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: %i/%i; %sExplanation An operation on the TDP Directed Adjacency data structure failed.
Recommended Action ACTION_COPY_REPORT_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: %sExplanation An action attempted by the Tag Control process encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message %TAGCON-3-UNAVAILABLE: %s sort bad; item %dExplanation EXPLANATION_ADDR_TBL_TAGCON
Recommended Action ACTION_TOGGLE_TAG_IP_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: Can't alloc work item for %sExplanation Internally when a process, such as the TDP process, must request the tag distribution and control process take some action, it queues a work item for the tag distribution and control process. This message is generated when an attempt to queue work for the tag distribution and control process fails. The failure can occur if the system is unable to allocate memory to hold the work request, or if the process has stopped processing requests on its work queue.
Recommended Action ACTION_COPY_REPORT_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: Cannot alloc %sExplanation An attempt to allocate a label switching data structure failed because of a low memory condition.
Recommended Action ACTION_STD_LOW_MEMORY_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: Cannot allocate local tagExplanation An attempt to allocate a local (incoming) tag failed. This should happen only if the system has allocated all available local tags.
Recommended Action The number of tags available for allocation can be changed by the tag-switching tag-range ... configuration command. Consult with your technical service representative to determine whether you should use this command to increase the number of available tags.
Error Message %TAGCON-3-UNAVAILABLE: Duplicate Address %i advertised by peer %s is already bound to %sExplanation An address message advertisement is received from TDP/LDP peer. The address is rejected as it has already been advertised by an another peer. This implies that the rejected IP address has been configured on both peers by mistake
Recommended Action Correct the configuration by changing the IP address on one of the peers.
Error Message %TAGCON-3-UNAVAILABLE: Platform specified information for label region %s is invalid.Explanation A platform service routine provides label region information about all label regions it supports. This error message is printed when the service routine does not specify its label region information correctly.
Recommended Action Report this condition to your technical service representative.
Error Message %TAGCON-3-UNAVAILABLE: TDP peer %i(%s): %sExplanation An operation involving the state machine for a TDP peer failed.
Recommended Action ACTION_COPY_REPORT_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: TIB walk failed (%s)Explanation Some Tag Information Base (TIB) maintenance operations involve a complete scan (walk) of the TIB radix tree data structure. This message is generated when a TIB walk encounters an unexpected failure.
Recommended Action ACTION_COPY_REPORT_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: Tag Local Address Table revision number wrappedExplanation The revision number used to manage advertisement of interface addresses to TDP peers overflowed. This will result in faulty advertisement of interface addresses to TDP peers and faulty tag switching on those peers.
Recommended Action To restore proper interface address advertisement reboot the platform. Report this condition to your technical service representative.
Error Message %TAGCON-3-UNAVAILABLE: Unexpected blist_type (%d) for %s PIE from peer %sExplanation A TDP protocol information element (PIE) received from a TDP peer contained an unexpected binding list type. The PIE will be be ignored.
Recommended Action ACTION_IGNORE_PIE_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: Unexpected event; state=%s, event=%sExplanation An operation on the state machine for the tag distribution and control process failed.
Recommended Action ACTION_COPY_REPORT_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: peer %s, TDP Id/Addr mapping problem (%s)Explanation EXPLANATION_ADDR_TBL_TAGCON
Recommended Action ACTION_TOGGLE_TAG_IP_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: peer %s; %s not implementedExplanation A tag distribution protocol (TDP) peer has requested an action which is not currently implemented by the tag distribution and control subsystem.
Recommended Action The request will be ignored. If it repeatedly occurs, copy the message exactly as it appears and report it to your technical service representative.
Error Message %TAGCON-3-UNAVAILABLE: process cannot initializeExplanation The tag distribution and control process failed to initialize itself. The probable cause is insufficient memory.
Recommended Action ACTION_STD_LOW_MEMORY_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: process not createdExplanation An attempt to create the tag distribution and control process failed. The probable cause is insufficient memory.
Recommended Action ACTION_STD_LOW_MEMORY_TAGCON
Error Message %TAGCON-3-UNAVAILABLE: unexpected error %d; peer %s; %sExplanation An unexpected failure occurred while building a TDP protocol information element (PIE) for transmission to a TDP peer. It occurred when attempting to add a tag binding or an address to the PIE.
Recommended Action ACTION_COPY_REPORT_TAGCON
TAGCON-4
Error Message %TAGCON-4-UNAVAILABLE: Adjusting configured label range to default rangeExplanation The saved configuration has been ignored and the default label range is being used.
Recommended Action Please reconfigure the label range to a valid range using mpls label range ... configuration command.
Error Message %TAGCON-4-UNAVAILABLE: Can't alloc work item for %iExplanation When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an 'address process'. This message is generated when an attempt to queue work for the address process fails.
Recommended Action This is an informational message. The system remembers that it needs to do this work and will regularly attempt to queue the necessary work item. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative.
Error Message %TAGCON-4-UNAVAILABLE: Can't create tagcon addr procExplanation When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an 'address process'. This message is generated when an attempt to create the address process fails.
Recommended Action This is an informational message. As long as it needs the process, the system will regularly attempt to create it. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative.
Error Message %TAGCON-4-UNAVAILABLE: Failure to initialize tag allocation pool %dExplanation The system was unable to initialize the data structure used to support allocation of tags for tag switching for the specified tag pool.
Recommended Action The system proceeds by ignoring the event. However, since the system will not be able to allocate tags from the tag pool, it will not advertise them to peers and, therefore, will not be able to forward tagged packets it receives (because it advertises no tags, it should not receive any tagged packets). Copy the message exactly as it appears and report it along with the startup and running configuration to your technical service representative.
TAGCON-5
Error Message %TAGCON-5-UNAVAILABLE: cannot queue TDP %s pie for %i(%s)Explanation An attempt to queue a TDP PIE (protocol information element) for transmission to a TDP peer failed.
Recommended Action This is an informational message. Failure to queue a PIE for a peer should occur only when the TDP session with the peer no longer exists. The software should recover from this situation by discarding the TDP session and trying to establish a new one. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative.
TAR_FS Messages
This section contains tar file system messages.
TAR_FS-3
Error Message %TAR_FS-3-IMAGE_FILE_INVALID: [chars] file not found in archiveExplanation The tar file system could not locate the relevant tar element inside the archive.
Recommended Action Check whether the archive is complete and not corrupted, or if it is the wrong format. If the problem can be recreated with debug ifs file turned on, you can more quickly identify the problem. Save the output of the archive tar /table archive-name command if it is a pure tar archive, or the show image contents file archive-name command if the archive is a system image. 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://tools.cisco.com/ServiceRequestTool/create, 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.
TBRIDGE-4
Error Message %TBRIDGE-4-UNAVAILABLE: %s received on %s - invalid media for transparent bridgingExplanation Transparent bridging was configured on an interface that does not support it.
Recommended Action Remove transparent bridging from the configuration on the specified interface.
Error Message %TBRIDGE-4-UNAVAILABLE: Destination VC unknown for packetExplanation A transparently bridged packet destined for an ATM interface cannot be fully addressed.
Recommended Action Clear the bridge table to force re-learning of all addresses.
Error Message %TBRIDGE-4-UNAVAILABLE: Giant received on %s, %d exceeds %d DA %e SA %e [0x%08x]Explanation A packet was received that exceeds the expected maximum transmission unit (MTU) length for the receiving interface. The first four bytes of the packet following the source address are also provided to assist diagnosis.
Recommended Action Use the address and packet information provided to trace the source of these packets and reduce its MTU to conform to the standard for the given media.
Error Message %TBRIDGE-4-UNAVAILABLE: MAC-address table size limit (%lu entries) reachedExplanation The total number of bridge MAC-address table entries (across all bridge groups) has reached the configured maximum limit.
Recommended Action Check the bridge tables to determine the origin of the bridge MAC-address table entries. Check the network configuration and ensure that the entries are as expected. Use the bridge mac-address-table limit configuration command to either increase the maximum limit or to disable limit-checking altogether.
Error Message %TBRIDGE-4-UNAVAILABLE: No VC's configured for bridging on %sExplanation An ATM interface was configured for transparent bridging without also specifying the associated virtual circuits.
Recommended Action Configure the required virtual circuits on the specified interface.
Error Message %TBRIDGE-4-UNAVAILABLE: Subscriber SA %e moved or loop between circuits %d and %dExplanation A subscriber bridged packet dropped because potential circuit loop or roaming host at subscriber end of network.
Recommended Action Clear bridge table. If problem persists it is not a roaming host, but a loop between virtual circuits at subscriber end of network. Take looping virtual circuits out of service and/or shut the software interface they are on while subscriber is contacted to remove loop condition at subscriber end of network.
Error Message %TBRIDGE-4-UNAVAILABLE: Unexpected encapsulation received on %s %sExplanation The transparent bridging driver received a packet with unrecognizable encapsulation. The packet had to be discarded.
Recommended Action This could indicate a network media error or that a protocol which is newer than this version of the Cisco IOS software is being used. If it is believed that the dropped packets are of a real protocol, upgrade to a new version of the software which handles it.
Error Message %TBRIDGE-4-UNAVAILABLE: XMACACCESS: Invalid extended access list %dExplanation This is a configuration problem. The specified extended access list either does not exist or contains an error.
Recommended Action Correct the configuration problem.
Error Message %TBRIDGE-4-UNAVAILABLE: invalid action found for %e on %s - %08xExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
TCAM_MGR Messages
This section contains TCAM manager messages.
TCAM_MGR-3
Error Message %TCAM_MGR-3-BAD_FIRST_DYN_REGION: [dec]Explanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCAM_MGR-3-BAD_LAST_DYN_REGION: [dec]Explanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCAM_MGR-3-INTERNAL_ERROR: [chars], [chars], [dec]Explanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCAM_MGR-3-INVALID_OPERATION: [chars], [dec]Explanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCAM_MGR-3-INVALID_REG_TYPE: [chars], [dec]Explanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCAM_MGR-3-MALLOC_FAIL: [chars], [chars]Explanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCAM_MGR-3-OP_FAIL: [chars] failed for application [chars], application entry [hex] with [chars] errorExplanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCAM_MGR-3-UNUSUAL_BUG_WARNING: [chars] mbu [hex] free_array_index [dec] region_id [dec]Explanation A TCAM error was detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TCAMMGR Messages
This section contains TCAM manager messages.
TCAMMGR-3
Error Message %TCAMMGR-3-GROW_ERROR: cam region [dec] can not growExplanation This CAM region is configured as a static region with a fixed number of entries, and a call was requested to add more CAM entries to the specified region.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalidExplanation The CAM handle that was used by the caller is invalid.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCAMMGR-3-INDEX_ERROR: cam value/mask index [dec] is invalidExplanation The CAM index that was used by the caller is invalid.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCAMMGR-3-MOVE_ERROR: cam entry move from index [int] to index [int] failedExplanation A move operation for a CAM entry from one index to another has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %TCAMMGR-3-REGION_ERROR: cam region [dec] is invalidExplanation The CAM region is invalid.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCAMMGR-3-REGMASK_ERROR: invalid cam region [dec] mask [dec] pairExplanation Only a predetermined set of masks are allowed in a region. The caller requested to install an entry in the specified region that contained an invalid mask for that region.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TCATM Messages
This section contains ATM tag distribution and control messages.
TCATM-3
Error Message %TCATM-3-INTERNAL: [chars]Explanation An operation that is required for proper operation of the TCATM has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
TCP Messages
This section contains Transmission Control Protocol (TCP) messages.
TCP-2
Error Message %TCP-2-UNAVAILABLE: %s called but TCP not initializedExplanation An internal software error occurred.
Recommended Action If this message recurs, copy the message exactly as it appears and contact your technical support.
Error Message %TCP-2-UNAVAILABLE: Bad TCB refcount: TCB 0x%x, refcnt %dExplanation An internal software error occurred
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message %TCP-2-UNAVAILABLE: Callback failed to accept connection from %s(%d) to %s(%d) -- discardingExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message %TCP-2-UNAVAILABLE: Invalid TCB encaps pointer: 0x%xExplanation An invalid TCP ENCAPS is used.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message %TCP-2-UNAVAILABLE: Invalid TCB pointer: 0x%xExplanation An invalid TCB is used.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message %TCP-2-UNAVAILABLE: Multiple entry for packet %xExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message %TCP-2-UNAVAILABLE: Tty%t, buffering bugExplanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message %TCP-2-UNAVAILABLE: Tty%t, tcp_putbyte() with blocking disabledExplanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message %TCP-2-UNAVAILABLE: Tty%t, tcp_putbyte() write disabledExplanation TCP received a packet from a user application after the connection was already halfclosed.
Recommended Action Determine which TCP application is still sending after the connection was halfclosed.
Error Message %TCP-2-UNAVAILABLE: Tty%t: Bad refcnt for packet 0x%x during retransmit, %s(%d) to %s(%d), state %dExplanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
TCP-3
Error Message %TCP-3-BADMSS: Incorrect mss [dec] observedExplanation The maximum segment size is incorrect. TCP cannot guarantee further reliable operation for this connection.
Recommended Action Check the MTU for the interface and increase it as required. If, after adjusting the MTU, 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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-CHKPT_INIT: TCP failed to initialize checkpoint storage: %sExplanation The TCP process failed to initialize checkpoint storage for ports.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_DUMP_DEB: netdump_print_context failed, %dExplanation Netdump print failed while dumping a process debug context.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_MD5_INVALID: MD5 validation failed, incoming packet src: %s:%d, dst: %s:%dExplanation MD5 validation failed on an incoming packet.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_MD5_WRITE: MD5 option write failed, dst: %s:%dExplanation The TCP process failed to write an MD5 option.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_NETWORK_INIT: TCP failed to connect with network layer: %s, error %sExplanation TCP initialization with the network layer 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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_OUT_BUFF: ran out of buffer with %ld bytes %s to sendExplanation TCP ran out of buffer space while copying segment data.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_PAK_FSV: %sExplanation An FSV operation failed on the packet.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_PAK_DISCARD: %s: %s, <%s:%d> -> <%s:%d>Explanation Packet information from a discarded packet is displayed.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_PCB_VECTOR: ip_pcb_get_family_vector failed, %dExplanation The TCP process failed to get a pointer to the PCB family vector.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-ERR_SET_APP_LEN: %s: set_Application_length failed: %sExplanation The TCP process failed to set an application buffer for the segment.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-FORKFAIL: Failed to start a process to negotiate options.Explanation The system failed to create a process to handle requests from a client. This condition could be caused by insufficient memory.
Recommended Action Reduce other system activity to ease memory demands.
Error Message %TCP-3-SOCKET_RESMGR_ATTACH: Failed to setup the transport as a resource manager: %sExplanation The TCP process failed to advertise itself to the system as a resource manager.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TCP-3-TRACE_ERR: %s error (%d). Premature trace termination for control block 0x%pExplanation A trace terminated prematurely.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TCP-4
Error Message %TCP-4-ERR_PAK_CLIENT: %s, res %dExplanation A packet client operation failed in TCP.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCP-4-WARNING_DEBUG: %sExplanation TCP failed to open the console device for debug.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TCP-6
Error Message %TCP-6-INFO_RCV_SIG: recieved signal %dExplanation The TCP process received a signal.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TCP-6-MD5NOSPACE: Insufficient space for MD5 optionExplanation There was insufficient space for the MD5 option. This condition should not occur, because the MD5 option, when requested, is required and is given preference over other TCP options.
Recommended Action Unconfigure other TCP options, if any, in an attempt to create space for the MD5 option. 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://tools.cisco.com/ServiceRequestTool/create, 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.
TCP-7
Error Message %TCP-7-ERR_TCP_INIT: TCP failed to initialize: %s, error %sExplanation TCP initialization failed.
Error Message 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the %TDM-1-UNAVAILABLE: Motherboard TDM init failure: stream %d, channel %d, channel register 0x%x, control register 0x%x.Explanation A TDM port on the system motherboard failed to be initialized. The error message specifies which port. This is possibly due to a hardware failure.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TDM-1
Error Message %TDM-1-UNAVAILABLE: Slot %d TDM init failure: stream %d, channel %d, channel register 0x%x, control register 0x%x.Explanation A TDM port failed to be initialized. The error message specifies which port. This is possibly due to a hardware failure.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Recommended Action 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.
TDM-3
Error Message %TDM-3-UNAVAILABLE: Slot %d bad board ID 0x%x detected.Explanation The specified board returned an ID that was not recognized by the operating system. This could be due to a hardware failure reporting an incorrect ID or because this software predates the hardware.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TDM-4
Error Message %TDM-4-UNAVAILABLE: Bad connection requested: slot %d, stream %d, channel %d to slot %d, stream %d, channel %d.Explanation The TDM cross-connect that was requested was not possible. This is probably because one of the devices either does not exist or is not properly configured for TDM.
Recommended Action Check the command for errors and the ports for correct configuration before trying again. Note that the ype option of the dm-group command only applies if the mode cas command is enabled. If configuring cross-connect pass-through from UIO serial port 0 or 1 to a controller, the encapsulation clear-channel command must be configured on the serial port.
TDM_CLOCK_SYNCHRONIZATION-4
Error Message %TDM_CLOCK_SYNCHRONIZATION-4-UNAVAILABLE: TDM frame clock %s lost lock - clock source failed.Explanation The clock source has failed.
Recommended Action If alternate source is available, it will be used.
Error Message %TDM_CLOCK_SYNCHRONIZATION-4-UNAVAILABLE: TDM frame clock source transitioned from Priority %d %s %s to Priority %d %s %sExplanation This warning message indicates a change in the clock source.
Recommended Action No action required.
Error Message %TDM_CLOCK_SYNCHRONIZATION-4-UNAVAILABLE: TDM frame clock state change, state: %sExplanation This debug message indicates a clock state change
Recommended Action No action required.
Error Message %TDM_CLOCK_SYNCHRONIZATION-4-UNAVAILABLE: TDM frame clock state error, state: %s event: %sExplanation This warning message indicates a invalid clock event
Recommended Action No action required.
TDP-3
Error Message %TDP-3-UNAVAILABLE: %sExplanation An action attempted by the Tag Distribution Protocol (TDP) encountered an unexpected condition.
Recommended Action ACTION_COPY_REPORT_TDP
Error Message %TDP-3-UNAVAILABLE: %sExplanation An action attempted by the Tag Distribution Protocol (TDP) implementation failed.
Recommended Action ACTION_COPY_REPORT_TDP
Error Message %TDP-3-UNAVAILABLE: Can't alloc KA PIEExplanation An attempt to allocate a buffer for Tag Distribution Protocol (TDP) Keep Alive protocol information element (PIE) has failed.
Recommended Action The system will continue by omitting transmission of the TDP Keep Alive PIE. This may result in termination of one or more TDP sessions as the peers time out the sessions. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance.
Error Message %TDP-3-UNAVAILABLE: Interface %s, Bad VPI/VCI range. Can't start a TDP sessionExplanation The VPI range exchanged between the Tag Distribution Protocol (TDP) peers is non-overlapping.
Recommended Action The system will not be able to create a TDP session between the affected TDP peers. Re-issue the tag-switching vpi command on the appropriate interface with the correct VPI range.
Error Message %TDP-3-UNAVAILABLE: Interface %s, Resource failure. Can't start a TDP sessionExplanation An attempt to allocate a buffer for Tag Distribution Protocol (TDP) TAGATM VPI/VCI ranges has failed.
Recommended Action The system will not be able to create a TDP session between the affected TDP peers. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance.
Error Message %TDP-3-UNAVAILABLE: peer %s, read failureExplanation An error occurred while attempting to read a TDP PDU received from a peer.
Recommended Action ACTION_NEW_SESSION_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; address len %dExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address with a bad length has been received from a peer.
Recommended Action ACTION_IGNORE_REST_OF_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; alist_type %d; %s pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer.
Recommended Action ACTION_IGNORE_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; alist_type %d; %s pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown address list type has been received from a peer.
Recommended Action ACTION_IGNORE_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; blist_type %d; %s pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a binding list type that is unexpected for the situation has been received from a peer.
Recommended Action ACTION_IGNORE_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; blist_type %d; %s pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown binding list type has been received from a peer.
Recommended Action ACTION_IGNORE_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; format error for pie type 0x%xExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) that is malformed has been received from a TDP peer.
Recommended Action ACTION_NEW_SESSION_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; mlist_type %d; %s pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown metric list type or one that is unexpected for the situation has been received from a peer.
Recommended Action ACTION_IGNORE_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; prefix len %dExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a destination prefix with a bad length has been received from a peer.
Recommended Action ACTION_IGNORE_REST_OF_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; unexpected pie type 0x%xExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) that is unexpected for the situation has been received from a peer.
Recommended Action ACTION_IGNORE_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: peer %s; unknown pie type 0x%xExplanation An unknown Tag Distribution Protocol (TDP) protocol information element (PIE) type has been received from a peer.
Recommended Action ACTION_IGNORE_PIE_TDP
Error Message %TDP-3-UNAVAILABLE: unexpected event: peer %i(%s), state=%s, event=%s%sExplanation An operation on the state machine for a TDP peer failed.
Recommended Action ACTION_COPY_REPORT_TDP.
TDP-4
Error Message %TDP-4-UNAVAILABLE: Peer %s; %sExplanation The session parameters proposed by an LDP peer differ from those preferred by the platform. The differences are not sufficient to prevent the LDP session from being established, but may have an impact on label distribution operation
Recommended Action If the parameters identified relate to the optional path vector-based loop detection mechanism, note that the IETF LDP specification recommends that when Loop Detection is enabled in a portion of a network, it is recommended that all LSRs in that portion of the network be configured with Loop Detection enabled and with the same path vector limit. If the parameters identified relate to some other aspect of the LDP session and the message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative.
Error Message %TDP-4-UNAVAILABLE: Peer = %s %s(%i%m) Maxhop=%d hopcount=%d %sExplanation This message appears when signalling to establish an MPLS Label Switched Path (LSP), or Tag Switching Tag Switched Path, discovers a transient loop in the path to the LSP destination. Normally this is a transient condition.
Recommended Action ACTION_LOOPING_LSP
Error Message %TDP-4-UNAVAILABLE: Peer = %s %s(%i%m) hopcount=%d %sExplanation This message appears when LDP loop detection is configured and signalling to establish an MPLS Label Switched Path (LSP) detects a transient loop in the path to the LSP destination. Normally this is a transient condition.
Recommended Action ACTION_LOOPING_LSP
Error Message %TDP-4-UNAVAILABLE: cannot set %s%s TDP identExplanation The Tag Distribution Protocol (TDP) requires each TDP instance have a TDP identifier. An attempt to set the TDP identifier for the shown VRF or TDP instance has failed.
Recommended Action This is an informational message. As long as it needs to set its chassis TDP identifier the system will periodically attempt to do so until it succeeds. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative.
Error Message %TDP-4-UNAVAILABLE: peer %s, %sExplanation A violation of the TDP protocol by a TDP peer has been detected.
Recommended Action ACTION_NEW_SESSION_TDP
TDP-5
Error Message %TDP-5-UNAVAILABLE: %sExplanation This is an informational message generated by the Tag Distribution Protocol (TDP) implementation.
Recommended Action No action is required.
Error Message %TDP-5-UNAVAILABLE: tag advertise-tags has no effect for tc-atmExplanation EXPLANATION_ACL_TDP
Recommended Action No action is required.
TEMUX84-3
Error Message %TEMUX84-3-UNAVAILABLE: temux84 Byte-Sync indirect access failed, %sExplanation hardware busy bit not cleared
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TEMUX84-3-UNAVAILABLE: temux84 RTTB indirect access failed, %sExplanation hardware busy bit not cleared
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TEMUX84-3-UNAVAILABLE: temux84 SBI indirect access failed, %sExplanation hardware busy bit not cleared
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TEMUX84-3-UNAVAILABLE: temux84 T1E1 indirect access failed, %sExplanation hardware busy bit not cleared
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TEMUX84-3-UNAVAILABLE: temux84 T3E3 PMON update failed, %sExplanation T3E3 PMON counter failed to latch
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://tools.cisco.com/ServiceRequestTool/create, 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.
TENGIGE_LC Messages
This section contains 10-Gigabit Ethernet line card messages.
TENGIGE_LC-3
Error Message %TENGIGE_LC-3-LASER_TEMP_ERR: Laser Temperature Alarm : [dec]/[dec]Explanation A laser temperature alarm condition 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://tools.cisco.com/ServiceRequestTool/create, 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 %TENGIGE_LC-3-MIB_TENGIGE_LASER_FAILURE: Laser failure detected during soft-start procedures : [chars]Explanation A laser 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://tools.cisco.com/ServiceRequestTool/create, 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 %TENGIGE_LC-3-MIB_TENGIGE_LOSYNC_ALM: Loss of Sync ; [chars]Explanation The Gigabit Ethernet function lost its synchronization.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TENGIGE_LC-3-TENGIGE_LOSYNC_ALM: [chars] side Loss of Sync lock: [chars]Explanation The Gigabit Ethernet function lost its synchronization.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TENGIGE_LC-3-TENGIGE_LOSYNC_ALM_CLR: CLEARED : [chars] Loss of Sync lock: [chars]Explanation The Gigabit Ethernet function lost its synchronization.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TENGIGE_LC-6
Error Message %TENGIGE_LC-6-LASER_DISABLED: Laser disabled as per user configuration [[dec]/[dec]]Explanation The laser has been disabled as specified by the user configuration.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TENGIGE_LC-6-LASER_DISABLED_BY_HW: Laser disabled as per laser safety configuration [[dec]/[dec]]Explanation The laser has been disabled as specified by the safety configuration.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TENGIGE_LC-6-MIB_TENGIGE_TRUNK_LOSYNC_PALM: Trunk side Loss of Sync Prealarm; [chars]Explanation The trunk lost its synchronization while it was receiving data.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TENGIGE_LC-6-TENGIGE_TRUNK_RX_LOSYNC_PALM: Trunk side Loss of Sync lock Prealarm: [chars]Explanation The trunk lost its synchronization while it was receiving data.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TESTPA-3
Error Message %TESTPA-3-UNAVAILABLE: bay [%d] analyze failedExplanation The TestPA port adapter driver failed to successfully complete the necessary tasks for initial bring up of the port adapter. This is typically due to shortage of memory. Previous messages in the log will indicate the exact reason for the failure. The port adapter will be deactivated.
Recommended Action Verify that the port adapter is properly seated in the bay.
Error Message %TESTPA-3-UNAVAILABLE: bay [%d] dma error: %sExplanation A DMA failure occurred.
Recommended Action Verify that the port adapter is properly seated in the bay.
Error Message %TESTPA-3-UNAVAILABLE: bay [%d] initialization failed: %sExplanation The TestPA port adapter driver failed to successfully initialize the hardware on the TestPA port adapter. The port adapter will be deactivated.
Recommended Action Verify that the port adapter is properly seated in the bay.
Error Message %TESTPA-3-UNAVAILABLE: bay [%d] powered offExplanation The port adapter has been powered off. Other messages in the log specify the cause of this event.
Recommended Action If possible, correct any errors indicated by the other messages occurring at the time of this message. If the error persists, verify that the port adapter is properly seated in the bay.
TI1570-1
Error Message %TI1570-1-UNAVAILABLE: %s %sExplanation The ATM Port Adapter failed to complete hardware initialization. Details of the failure are shown in the error message.
Recommended Action Reset the adapter. This should not be a recurring condition. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-1-UNAVAILABLE: %s for subunit %d in bay %dExplanation The ATM Port Adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-1-UNAVAILABLE: Only %#x bytes of memory available for %sExplanation The port adaptor needs more PCI memory. The installed amount is less than required by the drivers for packet buffers.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TI1570-1-UNAVAILABLE: PCI configuration for %s in slot %dExplanation The ATM Port Adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-1-UNAVAILABLE: VIP only supports one PA-A1 ATM LITE PA. The other PA bay must be emptied in order for the PA-A1 ATM LITE PA to function.Explanation The bandwidth requirements of the installed port adapters exceed the processor's rated capability.
Recommended Action Either remove one of the port adapters or upgrade the VIP.
TI1570-3
Error Message %TI1570-3-UNAVAILABLE: %s block command (code %d) failed, error code %dExplanation An internal hardware or 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: %s receive freeze %dExplanation This message indicates excessive traffic congestion on the ATM interface may have resulted in cell loss. The PCI-ATM interface's cell buffers were full when a cell arrived on the interface, resulting in a receive freeze condition. A small number of freezes might not be a cause for concern.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: %s transmit freeze %dExplanation This message indicates the PCI-ATM interface had to stop the transmitter while waiting for data. A small number of freezes might not be a cause for concern.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: %s tx buffer data start not aligned to 32 bit boundary, data block0x%08x, data start 0x%08xExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TI1570-3-UNAVAILABLE: Bay %d device ID seen as %#x, expected #%xExplanation The ATM-PCI Port Adapter driver found incorrect device ID's on the specified card. This could indicate either a hardware failure or that the software needs to be upgraded to recognize newer hardware.
Recommended Action Power down, reseat the interface card, and reboot. Or investigate if newer software is needed for your hardware. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: Bay %d device ID seen as %#x, expected %#xExplanation The ATM-PCI port adapter driver could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: Found %d out of %d devices (ID %08X) in bay %dExplanation The ATM-PCI Port Adapter software driver found fewer devices than it was configured to expect. This could mean that the missing one(s) failed to start and may have failed.
Recommended Action Try shutting off the power, re-seating the card, and rebooting. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: Interface %s, %s not supportedExplanation An attempt was made to configure a rate queue on an ATM Lite port adapter that does not support rate queues.
Recommended Action Check the configuration and try again, avoiding unsupported features.
Error Message %TI1570-3-UNAVAILABLE: Interface %s, Failed to down vc %d (Cause: %s)Explanation An ATM virtual circuit could not be shut down for the reason shown in the error message. This probably indicates a software 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TI1570-3-UNAVAILABLE: Interface %s, Failed to setup vc %d (Cause: %s)Explanation This probably indicates a hardware failure in the ATM-PCI Port Adapter.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TI1570-3-UNAVAILABLE: RX DMA entry %#x not going inactiveExplanation A receive DMA channel failed to deactivate during shutdown of a virtual circuit. This failure could originate in hardware or software.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TI1570-3-UNAVAILABLE: TI1570 unit %d: PCI memory unavailable.Explanation The system experience memory exhaustion in the PCI/packet memory. This is probably due to heavy traffic congestion but could also be a software error.
Recommended Action Review the configuration for performance bottlenecks. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: TI1570 unit %d: PCI mini buffer unavailable.Explanation An internal hardware or 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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: TI1570 unit %d: PCI parity error (0x%08x)Explanation A parity error occurred on the PCI bus. This probably indicates an existing or developing hardware failure.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TI1570-3-UNAVAILABLE: TI1570 unit %d: Receive Channel HaltExplanation This probably indicates a hardware failure in the ATM-PCI Port Adapter.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TI1570-3-UNAVAILABLE: TI1570 unit %d: SYSTEM memory unavailable.Explanation Memory exhaustion has occurred in the ATM-PCI Port Adapter driver.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: TI1570: received corrupted shadow particle pointerExplanation The ATM-PCI Port Adapter driver experienced an internal error, probably due to software but possibly from a hardware failure.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TI1570-3-UNAVAILABLE: TX DMA not flushedExplanation A transmit DMA channel failed to flush its buffers during shutdown of an ATM interface. This failure could originate in hardware or software.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
TI1570-5
Error Message %TI1570-5-UNAVAILABLE: ti1570_vc_setup failed. (vci %d of the last vpi %d exceeds (vc-per-vp - 3)).Explanation The TI1570 chip reserves 3 RX DMA channels for OAM cells. As a result, the last 3 VCIs of the last VPI block cannot be used for regular traffic.
Recommended Action Avoid try different vci/vpi combinations.
TI1570-7
Error Message %TI1570-7-UNAVAILABLE: TI1500 framer interrupt isr1 0x%02x, isr2 0x%02x, isr3 0x%02xExplanation This is a informational/debugging message indicating that the ATM-PCI Port Adapter driver received and handled a framer interrrupt
Recommended Action LOG_STD_NO_ACTION.
TIB-3
Error Message %TIB-3-UNAVAILABLE: %i/%i, %s; unexpected tag state=%dExplanation An operation on the Tag Information Base (TIB) involving a locally assigned (incoming) tag failed.
Recommended Action ACTION_OMIT_OPER_TIB
Error Message %TIB-3-UNAVAILABLE: %i/%i, peer %s; tag %d; %sExplanation An operation on the Tag Information Base (TIB) involving a tag assigned by a TDP peer failed.
Recommended Action ACTION_OMIT_OPER_TIB
Error Message %TIB-3-UNAVAILABLE: %i/%i; %sExplanation An operation on the Tag Information Base (TIB) data structure failed.
Recommended Action ACTION_COPY_REPORT_TIB
Error Message %TIB-3-UNAVAILABLE: %sExplanation An action attempted by the Tag Information Base (TIB) implementation failed.
Recommended Action ACTION_COPY_REPORT_TIB
Error Message %TIB-3-UNAVAILABLE: Cannot allocate TIBExplanation During initialization for tag switching an attempt to initialize the Tag Information Base (TIB) failed. A probable cause is insufficient memory
Recommended Action ACTION_COPY_REPORT_TIB
Error Message %TIB-3-UNAVAILABLE: TIB revision number wrapped; toggling dynamic tag switching off and on to recover.Explanation The TIB revision number used to manage advertisement of tags to TDP peers overflowed. This will result in faulty tag distribution to TDP peers. The system recovers by toggling dynamic tag switching off and on, which forces the revision number to be re-initialized.
Recommended Action None required.
Error Message %TIB-3-UNAVAILABLE: Unexpected event; state=%s, event=%sExplanation An operation on the Tag Information Base (TIB) state machine failed.
Recommended Action ACTION_COPY_REPORT_TIB.
TIB-5
Error Message %TIB-5-UNAVAILABLE: %i/%i, peer %s; tag %d; Unexpected LDP label release; %sExplanation An operation on the Tag Information Base (TIB) involving a tag assigned by a TDP peer failed.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This will not result in impaired or faulty behavior for tagged packets for this destination.
Error Message %TIB-5-UNAVAILABLE: %i/%i, tag %d; Withdrawn tag record has timed out.Explanation Record associated with a withdrawn label has timed out before receiving acknowledgements from all peers.
Recommended Action This is an informational message. This will not have any operational impact. The system will ignore any subsequently received release messages associated with the label.
TID_HA Messages
This section contains table ID high availability (HA) messages.
TID_HA-3
Error Message %TID_HA-3-ISSUERR: [chars] [chars]Explanation An error occurred during an in-service software upgrade (ISSU) versioning operation.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TID_HA-3-ISSUERRCF: [chars] checkpoint code [dec]Explanation An error occurred during an ISSU versioning operation due to an error in the checkpoint facility.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TID_HA-3-RXFAIL1: [chars]Explanation An error occurred while receiving a table ID synchronization message.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TID_HA-3-RXFAIL2: [chars], type [dec], version [dec], flags [hex]Explanation An error occurred while receiving a table ID synchronization message.
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. 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message %TID_HA-3-RXFAIL3: [chars] type [dec], version [dec],flags [hex], application [dec], action [dec], tableid [dec], name [chars]Explanation An error occurred while receiving a table ID synchronization message.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TID_HA-3-SYNCFAIL: [chars]Explanation Internal table ID information may have not been synchronized to the standby unit correctly.
Recommended Action Reload the standby unit. If the error condition 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://tools.cisco.com/ServiceRequestTool/create, 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 %TID_HA-3-SYNCFAILCF: [chars] checkpoint code [dec]Explanation Internal table ID information may have not been synchronized to the standby unit correctly due to an error in the checkpoint facility.
Recommended Action Reload the standby unit. If the error condition 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://tools.cisco.com/ServiceRequestTool/create, 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 %TID_HA-3-TXFAIL: [chars], name [chars] tableid [dec] action [dec]Explanation An error occurred while sending the internal table ID information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %TID_HA-3-TXFAILCF: [chars], name [chars], tableid [dec], action [dec], checkpoint code [dec]Explanation Failed to send internal table ID information due to an error in the checkpoint facility.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TLV-3
Error Message %TLV-3-UNAVAILABLE: Reading data type %dExplanation An expected field in the TLV buffer was either missing or malformed
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://tools.cisco.com/ServiceRequestTool/create, 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 %TLV-3-UNAVAILABLE: Unable to write type %dExplanation An attempt to update a TLV entry 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://tools.cisco.com/ServiceRequestTool/create, 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.
TMCIPC-4
Error Message %TMCIPC-4-UNAVAILABLE: Received a duplicated IPC record for %s with seq #:%d.Explanation The sequence # on received record is the same as the previous received IPC msg.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TMQ-3
Error Message %TMQ-3-UNAVAILABLE: TMQ, Attempt to delete entry not in queueExplanation An attempt was made to delete an entry not in the queue.
Recommended Action Advisory message only. No action required.
TIDP Messages
This section contains Threat Information Distribution Protocol (TIDP) messages.
TIDP-3
Error Message %TIDP-3-RESTART: Restarting TIDP due to unexpected errorExplanation An unexpected error has occurred in the Threat Information Distribution Protocol (TIDP) process. TIDP has been restarted in an attempt to restore operation.
Recommended Action Enter the debug tidp errors and debug tidp events commands to gather data that may help identify the nature of 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://tools.cisco.com/ServiceRequestTool/create, 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.
TIDP-4
Error Message %TIDP-4-AUTHFAIL: Message from %s, %i failed authenticationExplanation The signature of a received message failed authentication. The message has been dropped.
Recommended Action Check the local and peer configurations to make sure that compatible authentication key sets are used.
Error Message %TIDP-4-REPLAYMSG: Unexpected message from %s, %i receivedExplanation A message with a sequence number outside of the acceptable range was received and has been dropped. The message might be a replay message and might indicate an intrusion attack.
Recommended Action Verify that the peer's hardware and configuration has not been altered. Verify connectivity to the peer.
Error Message %TIDP-4-SRCCHANGED: Address changed was being used by TIDPExplanation An interface IP address was changed, but the former address was being used as the Threat Information Distribution Protocol (TIDP) source address. TIDP cannot operate properly if the address is not local.
Recommended Action Restore the original IP address to the original interface or to a new interface, or change the TIDP source address.
TIDP-5
Error Message %TIDP-5-BADMSG: Message from %s, %i failed validationExplanation A message has failed basic header and range check validation. The message has been dropped.
Recommended Action Check the local and peer configurations to make sure that compatible versions of TIDP and encryption keys are used.
Error Message %TIDP-5-OVERSIZE: Oversized message received from %s, %iExplanation A larger than expected message was received and has been dropped.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TIDP-5-PEERSRCCHANGED: TIDP source address of the connection to peer %i is changedExplanation The Threat Information Distribution Protocol (TIDP) source address changed. The change might be caused by DHCP renewal or by the user manually changing the IP address at the interface.
Recommended Action No action is required.
Error Message %TIDP-5-REGFAIL: Failed to register to peer %s, %i, group %uExplanation Attempts to register with the specified peer have failed. Another attempt will be made after the configured maximum retry interval.
Recommended Action Verify connectivity to the peer and make sure that the configuration between peers is compatible.
TIDP-6
Error Message %TIDP-6-DUPLICATE: Duplicate message from %s, %i receivedExplanation A message was received that had the same sequence number as a previously received message. The message has been dropped.
Recommended Action No action is required.
TINY_FRAG_POLICER Messages
This section contains tiny fragment policer messages.
TINY_FRAG_POLICER-6
Error Message %TINY_FRAG_POLICER-6-AGGREGATE_THRESHOLD_EXCEEDED: [dec] bps: it is recommended to reduce the hi threshold valueExplanation The fragment offset == 1 (fo1) packets aggregate threshold has exceeded the acceptable value.
Recommended Action Reduce the interface high-threshold values.
Error Message %TINY_FRAG_POLICER-6-HI_THRESHOLD_EXCEEDED: [dec] bps: installing rate limiter for vlan [int] on interface [chars]Explanation The fragment offset == 1 (fo1) packets high threshold has exceeded the acceptable value.
Recommended Action This is an informational message only. No action is required.
Error Message %TINY_FRAG_POLICER-6-RATELIMITER_FAILED: could not [chars]install rate limiter for vlan [int] interface [chars]Explanation The fragment offset == 1 (fo1) rate installer failed due to resource issues.
Recommended Action This is an informational message only. No action is required.
Error Message %TINY_FRAG_POLICER-6-RATELIMITER_REMOVED: removing rate limiter for vlan [int] from interface [chars]Explanation The fragment offset == 1 (fo1) packets dropped below the low threshold.
Recommended Action This is an informational message only. No action is required.
TMS Messages
This section contains Threat Management Service (TMS) messages.
TMS-2
Error Message %TMS-2-PROCESS_ERR: Router could not create a TMS controller processExplanation The router was unable to create a TIDP-based Mitigation Services (TMS) controller process.
Recommended Action Reload the device.
TMS-4
Error Message %TMS-4-UNAVAILABLE: %s| Group=%u|%s Type=%d| Flags=%dExplanation This message informs that the controller has received an invalid or unexpected packet from the consumer
Recommended Action Check the specified consumer for the TMS protocol operation
Error Message %TMS-4-UNAVAILABLE: An unknown Timer operational error occurredExplanation The TMS process cannot operate due to an internal system error.
Recommended Action Reload the device
Error Message %TMS-4-UNAVAILABLE: An unknown operational error occurred.Explanation The EOU process cannot operate due to an internal system error.
Recommended Action Reload the device
Error Message %TMS-4-UNAVAILABLE: PROCESS=%s| ACTION=%s.Explanation This message indicates that the specified process is stopped.
Recommended Action Reload the device
Error Message %TMS-4-UNAVAILABLE: UNKNOWN Event for Event=%d.Explanation This is an unknown message for the TMS controller process.
Recommended Action File a ddts with Cisco
Error Message %TMS-4-UNAVAILABLE: Unknown message event reveivedExplanation The TMS process received an unknown message event.
Recommended Action If this message recurs, reload the device.
TMS-6
Error Message %TMS-6-UNAVAILABLE: %sExplanation This messages informs that the consumer has cleared all the stats.
Recommended Action This is an informational message and no action is required.
Error Message %TMS-6-UNAVAILABLE: %sExplanation This messages informs that the tms consumer is configured or unconfigured
Recommended Action This is an informational message and no action is required.
Error Message %TMS-6-UNAVAILABLE: %s| Group=%u|%s Action=%s| Start TID=%d| End TID=%dExplanation This message informs that the controller has sent a reset request for an action to a specific consumer or a group
Recommended Action This is an informational message and no action is required.
Error Message %TMS-6-UNAVAILABLE: %s| Group=%u|%s Start TID=%d| End TID=%dExplanation This message informs that the controller has sent a status request to a specific consumer or a group
Recommended Action This is an informational message and no action is required.
Error Message %TMS-6-UNAVAILABLE: %s| Group=%u|%s Status=%sExplanation This messages informs that a consumer is registered or deregistered on the specifed group
Recommended Action This is an informational message and no action is required.
Error Message %TMS-6-UNAVAILABLE: %s| Group=%u|%s Status=%sExplanation This messages informs that a group is configured or unconfigured on on the specifed host
Recommended Action This is an informational message and no action is required.
Error Message %TMS-6-UNAVAILABLE: %s| Group=%u|%s TID=%dExplanation This message informs that the controller has sent a threat message to a specific consumer or a group
Recommended Action This is an informational message and no action is required.
Error Message %TMS-6-UNAVAILABLE: %s| Group=%u|%s Threat=%d| Version=%d| Action=%sExplanation This messages informs the status of a threat on a consumer in the specifed group
Recommended Action This is an informational message and no action is required.
TN Messages
This section contains Telnet messages.
TN-2
Error Message %TN-2-BADCONN: Bad conn pointer [hex] closing all connections on terminal line [dec]Explanation An internal software 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TN-2-BADLOGIN: Bad login string pointer %#xExplanation An internal software error occurred.
Recommended Action If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
TN-3
Error Message %TN-3-UNAVAILABLE: Illegal state %dExplanation An internal software error occurred.
Recommended Action If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message %TN-3-UNAVAILABLE: Unknown return code %d from telnet_readline()Explanation An internal software error occurred.
Recommended Action If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
TN3270-2
Error Message %TN3270-2-UNAVAILABLE: Input Buffer overflowExplanation A problem in TN3270 protocol was detected. Eight KB (8192) bytes of data were received without a TN3270 end-of-packet indicator. The TN3270 buffer overflowed.
Recommended Action Copy this error message exactly as it appears, and contact your technical support representative for assistance.
TOPN_COUNTERS Messages
This section contains switch TopN report counters messages.
TOPN_COUNTERS-3
Error Message %TOPN_COUNTERS-3-MGMT: %s transmit receive byte count is excessive, 1st poll %llu, 2nd poll %lluExplanation The traffic counter value on the interface is higher than expected. The module might be reporting an erroneous number.
Recommended Action Verify the traffic flow on the interface. If the flow does not match the TOPN report, contact your Cisco technical support representative.
TOPN_COUNTERS-4
Error Message %TOPN_COUNTERS-4-MEM_UNAVAIL: Memory was not available for handling the TopN requestExplanation The system cannot handle the TopN request because of lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
TOPN_COUNTERS-5
Error Message %TOPN_COUNTERS-5-AVAILABLE: TopN report [dec] is availableExplanation The specified report is ready and can be viewed by the users.
Recommended Action This is an informational message only. No action is required.
Error Message %TOPN_COUNTERS-5-DELETED: TopN report [dec] deleted by [chars]Explanation The specified report has been deleted by the specified user.
Recommended Action This is an informational message only. No action is required.
Error Message %TOPN_COUNTERS-5-KILLED: TopN report [dec] task killed by [chars] [chars]Explanation The system was in the process of generating the specified report, but the specified user terminated the report before its completion.
Recommended Action This is an informational message only. No action is required.
Error Message %TOPN_COUNTERS-5-NOPORTS: No interfaces in the system match the interface type for the generation of the topN report [dec]Explanation There were no interfaces in the system that matched the interface type selected in the specified report.
Recommended Action This is an informational message only. No action is required.
Error Message %TOPN_COUNTERS-5-STARTED: TopN collection for report [dec] started by [chars]Explanation The TopN report that was requested by the specified user starts with the specified report number.
Recommended Action This is an informational message only. No action is required.
TPLUS Messages
This section contains Terminal Access Controller Access Control System (TACACS) protocol messages.
TPLUS-3
Error Message %TPLUS-3-FORKFAIL: Failed to fork process for [chars].Explanation A process fork failed, probably due to insufficient memory.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TR-2
Error Message %TR-2-UNAVAILABLE: Unit %d, %s errorExplanation This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-2-UNAVAILABLE: Unit %d, PI %-08x %-08x %-08x %-08x %-08x %-08xExplanation This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-2-UNAVAILABLE: Unit %d, no memory for %sExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %TR-2-UNAVAILABLE: Unit %d, panic %-08x %-08x %-08xExplanation The Token Ring monitor firmware detected a fatal error that indicates an impending interface failure.
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://tools.cisco.com/ServiceRequestTool/create, 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._CRIT
Error Message %TR-3-UNAVAILABLE: %s: Can't set address to a multicast (%e)Explanation An attempt was made to set the Token Ring interface MAC address to a reserved multicast address.
Recommended Action Check your configuration. Make sure that your XNS and/or Novell Token Ring addresses have not inadvertently been set to reserved multicast addresses.
Error Message %TR-3-UNAVAILABLE: Bad unit number %dExplanation This error message pertains only to the IGS. When displayed, it indicates that the system cannot find the chipset registers where it expects them to be. This is most likely a hardware error.
Recommended Action If this message recurs, call your technical support representative for assistance. It will be necessary to determine the hardware unit configuration.
Error Message %TR-3-UNAVAILABLE: Interface %s failed init diags (0x%04x), %sExplanation The microcode attempted to run its diagnostics on the chip and failed.
Recommended Action Issue a clear interface command. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Interface %s, adapter check error (fatal) (%04x %04x %04x %04x)Explanation The Token Ring monitor firmware detected a fatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance. You may need to replace the interface card
Error Message %TR-3-UNAVAILABLE: Interface %s, adapter check error (non-fatal)(%04x %04x %04x %04x)Explanation The Token Ring monitor firmware detected a non-fatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
Error Message %TR-3-UNAVAILABLE: Unit %d interface failure: %#x %#x %#x, idb state %dExplanation The Token Ring Monitor firmware detected a fatal error due either to an internal software problem or to a hardware failure.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, Start completion and wrong idb state - state= %dExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, Tokenring firmware download failed got %#x, expected %#x, at address 0x%04x.%04xExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, bad bridge parameters: bridge_num=%d, max_rd=%d thisring=%d, targetring=%dExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, bad buffersize = %dExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, bad firmware type code during %s. type=%#x, fw=%#xExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, bad functional address=0x%08x, ring mode=0x%08xExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, change mode failed. result code=%#x, error code=%#xExplanation An internal hardware or software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, init failed. result code=%#x, error code=%#xExplanation The Token Ring hardware failed to initialize properly.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, no TMS380 firmware present. eagle=%#x, magic=%#xExplanation An internal hardware or software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, open failed: %s, %sExplanation The Token Ring interface was unable to insert itself into the ring. This is an indication of a busy or broken ring. The first character string in this error message indicates the stage of initialization at which the error occurred, and the second describes the error.
Recommended Action Try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. If the error message recurs, call your Cisco technical support representative for assistance.
Error Message %TR-3-UNAVAILABLE: Unit %d, open failed: check the lobe cable DB-9 connection.Explanation The Token Ring interface was unable to insert itself into the ring, and the error code returned indicates a wiring problem.
Recommended Action Check the cable connecting the router to the Token Ring MAU, and try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, reset failed, error code %-08x.Explanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, ring number (%d) doesn't match established number (%d).Explanation The number you have configured for the local ring does not match the value currently in use on the ring.
Recommended Action Check the configuration to make sure you used the correct ring number. If it is correct, confirm the configuration of all other bridges on the ring to make sure they are using the same ring number.
Error Message %TR-3-UNAVAILABLE: Unit %d, set bridge failed (code %#x).Explanation A hardware error occurred. The source routing accelerator (SRA) chip on the Token Ring card could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, set functional address failed (code %#x).Explanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, set group address failed (code %#x).Explanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TR-3-UNAVAILABLE: Unit %d, wire fault: check the lobe cable MAU connection.Explanation The Token Ring hardware is reporting a wire fault condition.
Recommended Action Check the cable connecting the router to the Token Ring media attachment unit (MAU).
TR-6
Error Message %TR-6-UNAVAILABLE: %s: Ring Status: %sExplanation This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic.
Recommended Action LOG_STD_NO_ACTION
Error Message %TR-6-UNAVAILABLE: TR%d: Ring Status: %s %sExplanation This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic. The meaning of each status code is shown in the Token Ring Status Codes Table. Code Explanation Fatal 0x8000 Signal loss Yes 0x4000 Hard error Yes 0x2000 Soft error No 0x1000 Transmit beacon Yes 0x0800 Lobe wire fault Yes 0x0400 Auto removal error Yes 0x0100 Receive request removed Yes 0x0080 Counter overflow No 0x0040 Single station No 0x0020 Ring recovery No
Recommended Action Check the Token Ring for the indicated condition.
TRACKING Messages
This section contains object tracking (TRACKING) messages.
TRACKING-5
Error Message %TRACKING-5-STATE: %d %s %s %s %s-%sExplanation A tracked object has changed its state.
Recommended Action No action is required.
TRAFFIC_UTIL Messages
This section contains traffic utilization (TRAFFIC_UTIL) messages.
TRAFFIC_UTIL-4
Error Message %TRAFFIC_UTIL-4-MONITOR_BACKPLANE_BELOW_THR: Backplane traffic utilization is %d%%, below threshold(%d%%) within %d second intervalExplanation The backplane traffic utilization is below the utilization threshold.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRAFFIC_UTIL-4-MONITOR_BACKPLANE_REACH_THR: Backplane traffic utilization is %d%%, reached threshold(%d%%) within %d second intervalExplanation The backplane traffic utilization has reached a utilization threshold.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRAFFIC_UTIL-4-MONITOR_FABRIC_EG_BELOW_THR: Module %d, Channel %d egress traffic utilization is %d%%, below or equal threshold(%d%%) within %d second intervalExplanation The fabric channel egress traffic utilization is below a utilization threshold.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRAFFIC_UTIL-4-MONITOR_FABRIC_EG_REACH_THR: Module %d, Channel %d egress traffic utilization is %d%%, reached threshold(%d%%) within %d second intervalExplanation The fabric channel egress traffic utilization has reached a utilization threshold.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRAFFIC_UTIL-4-MONITOR_FABRIC_IG_BELOW_THR: Module %d, Channel %d ingress traffic utilization is %d%%, below or equal threshold(%d%%) within %d second intervalExplanation The fabric channel ingress traffic utilization is below a utilization threshold.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRAFFIC_UTIL-4-MONITOR_FABRIC_IG_REACH_THR: Module %d, Channel %d ingress traffic utilization is %d%%, reached threshold(%d%%) within %d second intervalExplanation The fabric channel ingress traffic utilization has reached a utilization threshold.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TRANGE Messages
This section contains time-range (TRANGE) error messages.
TRANGE-2
Error Message %TRANGE-2-NOMEMORY: Alloc fail for time-range config buffer. Disabling distributed mode on lcExplanation The system was unable to allocate a buffer to send time-range configuration information to the line cards.
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://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show chunks commands and your pertinent troubleshooting logs. show chunks
Error Message %TRANGE-2-WRONGREQUEST: Invalid request to allocate chunk of size %dExplanation A request was made to allocate a time-range chunk greater than the maximum allowed size (TRANGE_LARGE_CHUNK_SZ).
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRANGE-2-WRONGSIZE: Incorrect length trange ipc xdr of len=%d receivedExplanation The RP sent a time-range configuration message of the wrong size.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TRANSCEIVER Messages
This section contains transceiver module messages.
Error Message %TRANGE-2-NOMEMORY: Alloc fail for time-range config buffer. Disabling distributed mode on lcExplanation Unable to malloc a buffer to send time-range configuration down to linecards.
Recommended Action Enter a show chunks command and report the output, along with this error message, to your technical support representative.
TRANSCEIVER-3
Error Message %TRANSCEIVER-3-ATTACH_FAILURE: Detected for transceiver module in [chars], module disabledExplanation A software device driver attach has failed. This condition could be caused by a software, firmware, or hardware problem, but a software or firmware problem is more likely. As a result of the error, the module is disabled.
Recommended Action Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-CHECKSUM_ERROR: Detected in the transceiver module in [chars], module disabledExplanation A checksum error was detected when reading the ID PROM of a transceiver module for the specified interface. As a result of the error, the module is disabled.
Recommended Action Power down and reseat the module. If the problem 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-INIT_FAILURE: Detected for transceiver module in [chars], module disabledExplanation An initialization failure occurred for the transceiver module for the specified interface. This condition could be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled.
Recommended Action Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-INTERNAL_ERROR: [chars]Explanation The transceiver subsystem encountered an internal software error. The message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-NOT_COMPATIBLE: Detected for transceiver module in [chars], module disabledExplanation The transceiver module for the specified interface is not compatible with the interface. As a result of the error, the module is disabled.
Recommended Action Replace the module with a compatible transceiver. If the problem 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-NOT_IDENTIFIED: Detected for transceiver module in [chars], module disabledExplanation The transceiver module for the specified interface could not be identified and may not be compatible with the interface. As a result of the error, the module is disabled.
Recommended Action Replace the module with a compatible transceiver. If the problem 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-NOT_SUPPORTED: Detected for transceiver module in [chars], module disabledExplanation The transceiver module for the specified interface is not a Cisco supported module. As a result of the error, the module is disabled.
Recommended Action Replace the module with a Cisco supported transceiver. If the problem 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-OPER_ENABLE_FAILURE: Detected for transceiver module in [chars], module disabledExplanation Failed to enable the transceiver module for the specified interface. This condition could be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled.
Recommended Action Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-RPC_FAILED: Application error rc = [dec]:Explanation The system failed to retrieve the information required to execute the command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-RPC_LC_PROC_INIT_FAIL: Transceiver RPC init failure: [chars]Explanation The system failed to create the resources required to process user interface commands for transceivers. The error is not fatal but some show commands could fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-RPC_PROCESSING_ERROR: Transceiver RPC error: [chars]Explanation A nonfatal error occurred during the processing of an RPC message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRANSCEIVER-3-SM_CREATION_FAILURE: Transceiver OIR State Machine creation failed for [chars], module disabled.Explanation A state machine could not be created for the transceiver OIR operation. If a memory allocation message was also received with this message, this condition indicates insufficient system memory. Other possible causes include an invalid subblock pointer.
Recommended Action If it is insufficient system memory, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Otherwise, 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://tools.cisco.com/ServiceRequestTool/create, 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.
TRANSCEIVER-6
Error Message %TRANSCEIVER-6-INSERTED: transceiver module inserted in [chars]Explanation The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message.
Recommended Action This is an informational message only. No action is required.
Error Message %TRANSCEIVER-6-REMOVED: Transceiver module removed from [chars]Explanation The online insertion and removal (OIR) facility detected the removal of a transceiver module from the specified interface.
Recommended Action This is an informational message only. No action is required.
TRUNK-3
Error Message %TRUNK-3-UNAVAILABLE: Bad doorbell message type to framer: %dExplanation An invalid or undefined message type was sent to the framer processor.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK-3-UNAVAILABLE: Cannot send message to framer; no more messages availableExplanation The memory buffer for message passing between the trunk card and framer processors has been exhausted. Either the messages are not being picked up or are being generated too quickly.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK-3-UNAVAILABLE: Invalid framer firmware code file.Explanation The software has detected an invalid framer firmware image that cannot be downloaded.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK-3-UNAVAILABLE: Invalid value (%d) for shelf %d; exceeds %dExplanation An internal software error occurred. An attempt was made to reference a shelf number larger than the installed maximum.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK-3-UNAVAILABLE: No longer receiving heartbeats from framer CPU.Explanation Communication from the framer processor to the trunk card processor has stopped. The framer processor is no longer passing status to the trunk card processor nor accepting messages from the trunk card processor.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK-3-UNAVAILABLE: T1 Port %d on slot %d is now in drop-insert mode.Explanation The user has dropped a T1 port on a CT3 card by pressing the pushbutton on the CT3 card. This is a disruptive action in that any existing calls will be dropped.
Error Message %TRUNK-3-UNAVAILABLE: T1 Port %d on slot %d taken out of drop-insert mode.Explanation The user has restored a T1 port on a CT3 card by pressing the pushbutton on the CT3 card. This port was earlier dropped by the user and has now been taken out of dropped mode.
Error Message %TRUNK-3-UNAVAILABLE: Timed out waiting for framer CPU to respond.Explanation The framer processor did not reply to the read request during a specified amount of time.
Error Message %TRUNK-3-UNAVAILABLE: Trunk card initialization failed due to: %sExplanation Trunk card initialization has failed due to the specified reason.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK-3-UNAVAILABLE: Unknown type 0x%x in shelf %d slot %dExplanation The card in the specified slot and shelf was not recognized as either a T1 or E1 interface. This indicates a hardware or software failure.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK-3-UNAVAILABLE: selected clock on slot %d port %d is bad.Accepting the config.Explanation The clock status as reported by the framer is bad. Either no cable is plugged in or the port is indeed bad. Configuration is accepted and as soon as the port in reference turns good, it will be applied.
Recommended Action If user is configuring the clocks configuration in advance while there is no card in the corresponding slot or no cable is plugged in yet and if he is aware of this fact, then there is no action that needs to be taken. Otherwise, choosing another good clock and troubleshooting the bad clock from the port in reference is receommended.
TRUNK_CLOCK-3
Error Message %TRUNK_CLOCK-3-UNAVAILABLE: Failed to allocate memory for the clocksExplanation The clock switching software has failed to allocate memory while adding a clock.
Recommended Action LOG_STD_NO_ACTION
TRUNK_CLOCK-6
Error Message %TRUNK_CLOCK-6-UNAVAILABLE: Switching to the clock on slot %d port %d priority %d as the current primary has gone badExplanation The TDM primary clock has switched to a backup clock coming in via the specified trunk as the current primary clock has gone bad.
Recommended Action LOG_STD_NO_ACTION
Error Message %TRUNK_CLOCK-6-UNAVAILABLE: Switching to the user configured external clock on motherboardExplanation The TDM primary clock is switching from the default clock to the user configured external clock in motherboard.
Recommended Action LOG_STD_NO_ACTION
Error Message %TRUNK_CLOCK-6-UNAVAILABLE: Switching to the user configured freerunning clock on motherboardExplanation The TDM primary clock is switching from the default clock to the user configured free running clock in motherboard.
Recommended Action LOG_STD_NO_ACTION
Error Message %TRUNK_CLOCK-6-UNAVAILABLE: Switching to the user configured trunk clock on slot %d port %d priority %dExplanation The TDM primary clock is switching from the default clock to the user configured trunk clock.
Recommended Action LOG_STD_NO_ACTION.
Error Message %TRUNK_CLOCK-6-UNAVAILABLE: There are no good clocks in the system. Remain in HOLDOVER modeExplanation The clock selection algorithm has failed to select any clock as the TDM primary clock.
Recommended Action LOG_STD_NO_ACTION.
TRUNK_DFC-3
Error Message %TRUNK_DFC-3-UNAVAILABLE: Could not download trunk firmware in slot %dExplanation Cannot download trunk firmware
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRUNK_DFC-3-UNAVAILABLE: Failed to create context for dsx3 controller in %d/%dExplanation This message indicates internal software 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK_DFC-3-UNAVAILABLE: Failed to create controller for %d/%dExplanation This message indicates internal software 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK_DFC-3-UNAVAILABLE: Failed to create trunk slot instance for slot %dExplanation This message indicates internal software 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TRUNK_DFC-3-UNAVAILABLE: Reset failed for Trunk DFC ROM in slot %dExplanation Cannot take Trunk DFC out of reset
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %TRUNK_DFC-3-UNAVAILABLE: Trunk DFC ROM in slot %d failed: %sExplanation Trunk DFC ROM failed to boot properly
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRUNK_DFC-3-UNAVAILABLE: Trunk DFC firmware in slot %d is not readyExplanation Trunk DFC firmware failed to start
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://tools.cisco.com/ServiceRequestTool/create, 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 %TRUNK_DFC-3-UNAVAILABLE: Trunk DFC in slot %d: SDRAM failed [0x%x..0x%x]Explanation Trunk DFC SDRAM test failed indicating bad memory location
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://tools.cisco.com/ServiceRequestTool/create, 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.
TSP-3
Error Message %TSP-3-UNAVAILABLE: %sExplanation Internal Finite State Machine Error.
Recommended Action Contact your technical support representative, include the full text of the error message.
Error Message %TSP-3-UNAVAILABLE: no free event structure available from %s for DSP messageExplanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Check that the voice port for which the event was reported is still operational. If not, clear the voice port.
Error Message %TSP-3-UNAVAILABLE: voice port %s: call connection id [0x%x 0x%x 0x%x 0x%x]Explanation There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.
Recommended Action Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct.
Error Message %TSP-3-UNAVAILABLE: voice port %s: status=0x%x message=0x%xExplanation The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.
Recommended Action Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message.
TSP-5
Error Message %TSP-5-UNAVAILABLE: %s at slot %d, unit %d, channel %dExplanation A PRI signalling channel is added/deleted to TSP's inventory of signalling channels.
Recommended Action This is a notification message only. No action is required.
TTY-3
Error Message %TTY-3-UNAVAILABLE: Cannot create %s processExplanation Failed creating the 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TTY-3-UNAVAILABLE: TTY%t: Modem auto-configuration failedExplanation Modem auto-configuration failed either because the modem rejected the configuration string or because of a timeout. An attempt should be made to apply the configuration string mannually.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TTYDRIVER-2
Error Message %TTYDRIVER-2-UNAVAILABLE: Unable to allocate %d I/O buffersExplanation A buffer memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TTYDRIVER-2-UNAVAILABLE: Unable to allocate break block from I/O memExplanation The router does not have enough I/O memory for buffers.
Recommended Action Consider adding more shared memory. 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://tools.cisco.com/ServiceRequestTool/create, 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.
TTYDRIVER-3
Error Message %TTYDRIVER-3-UNAVAILABLE: No particles available to set up for output on tty %sExplanation A software error occurred resulting in an unexpected exhaustion of the pool of data buffers used by the modem drivers.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TTYDRIVER-3-UNAVAILABLE: Non-zero outcount but no transmit particle on tty %sExplanation A software error occurred and left a software structure in an unexpected state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TTYDRIVER-3-UNAVAILABLE: RTS is incorrectly deasserted for tty %s; reasserting nowExplanation A software error occurred resulting in an invalid state for the RTS modem signal
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TTYDRIVER-3-UNAVAILABLE: Unknown encapsulation on interface %sExplanation A software error occurred resulting in an unknown encapsulation type on the interface specified by the error message.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TTYDRIVER-3-UNAVAILABLE: Unknown port type (%d)Explanation A software error occurred due to an unrecognised port type
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://tools.cisco.com/ServiceRequestTool/create, 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.
TRIFECTA Messages
This section contains Trifecta service module messages.
Error Message %TRIFECTA-6-X86_FPGAVER_MISMATCH: Module [dec]: [chars]Explanation Trifecta X86 FPGA version mismatch.
Recommended Action No action is required.
Error Message %TRIFECTA-6-X86ONLINE: Trifecta X86 in slot [dec] is online.Explanation Trifecta X86 has finished booting up and is online.
Recommended Action No action is required.
Error Message %TRIFECTA-6-X86_RESTART_REASON: Module [dec]: [chars]Explanation Trifecta X86 restart reason.
Recommended Action No action is required.
TTFIB_NP_CLIENT Messages
This section contains Toaster Tag FIB (TTFIB) NP client messages.
TTFIB_NP_CLIENT-3
Error Message %TTFIB_NP_CLIENT-3-ERROR: [chars] [chars] [chars]Explanation Failed to set or clear port mode flags because the NP returned a failure condition.
Recommended Action Reload the Cisco IOS image on the affected card or platform. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TTFIB_NP_CLIENT-3-INFO: [chars]Explanation TTFIB NP client failed to initialize properly, which results in improper operation of the any transport over MPLS (AToM) feature.
Recommended Action Reload the Cisco IOS image on the affected card or platform. 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TTFIB_NP_CLIENT-3-NOMEM: [chars]Explanation TTFIB NP client failed to initialize properly, which results in improper operation of the any transport over MPLS (AToM) feature.
Recommended Action This message may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Reload the Cisco IOS image on the affected card or platform. 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://tools.cisco.com/ServiceRequestTool/create, 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.
TTFIB_NP_CLIENT-4
Error Message %TTFIB_NP_CLIENT-4-HDLC: [chars]Explanation Improper usage of SIP-400 for the HDLC over MPLS (HDLCoMPLS) feature.
Recommended Action This is an informational message only. No action is required.
Error Message %TTFIB_NP_CLIENT-4-PPP: [chars]Explanation Improper usage of SIP-400 for the PPP over MPLS (PPPoMPLS) feature.
Recommended Action This is an informational message only. No action is required.
Error Message %TTFIB_NP_CLIENT-4-VPLS: [chars]Explanation Improper usage of SIP-400 for the Virtual Private LAN Service (VPLS) feature.
Recommended Action This is an informational message only. No action is required.
Error Message %TTFIB_NP_CLIENT-4-WARN: [chars] [dec] [chars]Explanation A TTFIB entry could not be added because the entry passed is invalid.
Recommended Action Reload the Cisco IOS image on the affected card or platform. 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://tools.cisco.com/ServiceRequestTool/create, 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.
TUN Messages
This section contains tunnel messages.
TUN-3
Error Message %TUN-3-API_ARGS: unexpected arguments: [chars], [chars]Explanation A public tunnel component API was called with arguments outside the expected boundaries.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-3-ENDPOINT_ERROR: [chars] [chars]Explanation An internal software error occurred during manipulating the tunnel endpoint database.
Recommended Action No action is required.
Error Message %TUN-3-ENDPOINT_STORE: Operation [chars] failed for [chars]Explanation Manipulation of the tunnel endpoint store has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %TUN-3-ILLEGAL_ARGS: Illegal arguments - [chars]Explanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV4: [chars] IPv4 MTU configured [int] exceeds tunnel maximum MTU [int]Explanation An IPv4 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv4 since IPv4 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.
Recommended Action If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.
Error Message %TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV6: [chars] IPv6 MTU configured [int] exceeds tunnel maximum MTU [int]Explanation An IPv6 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv6 since IPv6 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.
Recommended Action If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.
TUN-4
Error Message %TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV4: [chars] IPv4 MTU configured [int] exceeds tunnel transport MTU [int]Explanation An IPv4 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.
Error Message %TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV6: [chars] IPv6 MTU configured [int] exceeds tunnel transport MTU [int]Explanation An IPv6 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.
Error Message %TUN-4-MTUCONFIGLESSTHAN_MINIPV4MTU: [chars] IPv4 MTU [int] is lesser than the minimum IP MTU [int], fragmentation may occurExplanation The IPv4 MTU value calculated on the tunnel interface is less than the minimum IP MTU. The MTU of the underlying exit interface of the tunnel is too small. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If a specific MTU value is not required for the exit interface, it is recommended that you leave the value at the default by typing no mtu on the exit interface. If a specific value is required, it is recommended that you check the MTU value from the show interface command for the exit interface and adjust mtu on the tunnel exit to be higher than this.
Error Message %TUN-4-UDLR_IDB_ERROR: UDLR [chars] - [chars]Explanation An error was encountered on a unidirectional link routing (UDLR) interface.
Recommended Action No action is required.
TUN-5
Error Message %TUN-5-HW_IF_INDEX_ILLEGAL: Attempt to create tunnel interface for [chars] with illegal index: [dec]Explanation The creation of a tunnel interface failed due to an invalid index.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-INIT_ERROR: A critical error [chars]occurred during initializationExplanation The creation of a tunnel subsystem 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-RECURDOWN_SRC: [chars] linestate down, recursive source interface, next output [chars]Explanation While the tunnel line state was being evaluated, a source interface was revisited.
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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_DB_IF: Operation on tunnel interface table failed for [chars] - [chars]Explanation A manipulation of the tunnel interface table 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_HWIDB_DELETE: Failed to delete hwidb for Tunnel [dec] index [dec]Explanation The deletion of a tunnel interface 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_HWIDB_LIST_DELETE: Failed to delete [chars] from tunnel hwidb listExplanation The deletion of a tunnel from the hardware IDB list 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_HWIDB_LIST_INSERT: Failed to add [chars] to tunnel hwidb listExplanation The insertion of a tunnel into the hardware IDB list 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_HWIDB_RECYCLE: Failed to recycle hwidb for Tunnel [dec] index [dec]Explanation The recycling of a tunnel interface 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_LIST_CREATE: Failed to create tunnel list [chars]Explanation The creation of a tunnel list 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_SWIDB_DELETE: Failed to delete swidb for Tunnel [dec] index [dec]Explanation The deletion of a tunnel interface 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_SWIDB_RECYCLE: Failed to recycle swidb for Tunnel [dec] index [dec]Explanation The recycling of a tunnel interface 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_TABLE: Operation [chars] on tunnel table failed for [chars] - [chars]Explanation The manipulation of the tunnel table 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_UNIT_LIST_DELETE: Failed to delete entry unit [dec] to tunnel unit listExplanation A deletion from the tunnel unit 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://tools.cisco.com/ServiceRequestTool/create, 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 %TUN-5-TUN_UNIT_LIST_INSERT: Failed to add entry unit [dec] to tunnel unit listExplanation The insertion of the tunnel unit 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://tools.cisco.com/ServiceRequestTool/create, 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.
TUNSS Messages
This section contains tunnel security messages.
Error Message %TUNSS-6-PROTECTION_BAD_TUN_MODE: Tunnel mode [chars] not supported by tunnel protection. Protection removed.Explanation The chosen tunnel mode is not supported by tunnel protection interfaces. Protection has been turned off and removed.
Recommended Action Unless protection is desired on this interface, no action is required. If protection is desired, a crypto-map must be used instead.
Error Message %TUNSS-3-PROTECTION_PROCESS_FAIL: Failed to create tunnel security process
Explanation The system failed to start a processes necessary to do tunnel protection.
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://tools.cisco.com/ServiceRequestTool/create, 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.
TWOBIT
Error Message %TWOBIT-3-UNAVAILABLE: %s: Error encountered (fsm rc %d)Explanation A 2bt protocol driver finite state machine error detected. This is not a fatal error.
Recommended Action This error means a 2bt protocol software error. However, this is not fatal since a retry mechanism ensures correct behaviour again. If this error message is repeatedly seen, copy the error message exactly as it appears on the console or in the system log, enter the show diag command to gather additional data, and contact your Cisco technical support representative with the gathered information
Error Message %TWOBIT-3-UNAVAILABLE: %s: Invalid fsm state (%s) (state %d)Explanation A 2bt protocol driver finite state machine error detected. This is not a fatal error.
Recommended Action This means there has been a glitch in the 2bt protocol negotitaion. However, this is not fatal since a retry mechanism ensures correct behaviour again. If this error message is repeatedly seen, copy the error message exactly as it appears on the console or in the system log, enter the show diag command to gather additional data, and contact your Cisco technical support representative with the gathered information
Error Message %TWOBIT-3-UNAVAILABLE: Failed to allocate hardware timerExplanation The 2bt protocol driver finite state machine was unable to allocate a hardware timer that it requires for operation.
Recommended Action This means there has been a glitch in the 2bt protocol negotitaion. This error will cause the 2 bt protocol to malfunction and cause higher layer applications that use this communication mechanism to fail. If this error message is seen, copy the error message exactly as it appears on the console or in the system log, enter the show diag command to gather additional data, and contact your Cisco technical support representative with the gathered information.
TXCONN-3
Error Message %TXCONN-3-UNAVAILABLE: Bad Transaction ID, flushing out request for client %i connected server %s, killing connection.Explanation Bad input stream.
Recommended Action This is an informational message. LOG_STD_NO_ACTION
Error Message %TXCONN-3-UNAVAILABLE: Bad license key configured for Transaction Connection.Explanation The license key configured with the txconn license configuration command is not valid.
Recommended Action Check that the license key was entered correctly in the txconn license configuration command. Refer to the txconn feature documentation for information on how to obtain a valid license key.
Error Message %TXCONN-3-UNAVAILABLE: Bad remote LU '%s' configured for server %sExplanation The remote LU configured for the txconn server is incorrect.
Recommended Action Contact your SNA network administrator to determine the correct name of the remote LU for DB2 on the remote database server. Be sure to check that the SNA network name is correct as well as the LU name.
Error Message %TXCONN-3-UNAVAILABLE: Exception %s from transaction %s to %s from client %iExplanation An unexpected transaction error 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://tools.cisco.com/ServiceRequestTool/create, 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. If possible, also provide the output of the debug txconn data command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.
Error Message %TXCONN-3-UNAVAILABLE: Out of resource, cannot create transaction for client %i connected server %s, killing connection.Explanation The router is out of memory.
Recommended Action This is an informational message. LOG_STD_NO_ACTION
Error Message %TXCONN-3-UNAVAILABLE: Unexpected client data, flushing out the request for client %i connected server %s.Explanation Bad input stream.
Recommended Action This is an informational message. LOG_STD_NO_ACTION
Error Message %TXCONN-3-UNAVAILABLE: Unknown mode '%s' configured for server %sExplanation The mode configured for the txconn server was rejected by the remote database server.
Recommended Action Contact your SNA network administrator to determine the correct name of the mode to use to connect to DB2 on the remote database server.
TXCONN-5
Error Message %TXCONN-5-UNAVAILABLE: APPC security failed, client %i using userid '%s' for server %sExplanation The userid and/or password passed in by the client were rejected by the remote database server.
Recommended Action This is an informational message only. LOG_STD_NO_ACTION
Error Message %TXCONN-5-UNAVAILABLE: CICS server %s has become unavailable. Recovery is in progress.Explanation A CICS server for a configured destination has become unavailable. All client connections to this server will be rejected until it becomes available again.
Recommended Action This is an informational message only. LOG_STD_NO_ACTION
Error Message %TXCONN-5-UNAVAILABLE: CICS server %s is now available.Explanation A CICS server that was previously unavailable has become available. All client connections to this server will now be accepted.
Recommended Action This is an informational message only. LOG_STD_NO_ACTION
Error Message %TXCONN-5-UNAVAILABLE: Client %i connected to server %s has timed out after %TE.Explanation The client was idle for too long, and the idle timeout configured for the txconn server expired.
Recommended Action This is an informational message only. LOG_STD_NO_ACTION
Error Message %TXCONN-5-UNAVAILABLE: Transaction %x of Client %i connected to server %s has timed out after %TE.Explanation The transaction was idle for too long, and the idle timeout configured for the txconn server expired.
Recommended Action This is an informational message only. LOG_STD_NO_ACTION
UAM Messages
This section contains Upgrade Analysis Module (UAM) messages.
UAM-3
Error Message %UAM-3-IMPACT_FAMILY: UAM is unable to get the impact of the upgrade on '%s' linecards family (SR is '%s')Explanation The Upgrade Analysis Module (UAM) is unable to determine the impact of the current upgrade for the line cards belonging to the specified family. An upgrade operation will probably result in the resetting of all line cards in that family.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UAM-3-INVALID_CONTEXT: Trying to stop the upgrade, but there is no upgrade currentlyExplanation An application is trying to stop an upgrade cycle, but there is no upgrade in progress.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UAM-3-INVALID_WB: Trying to set an invalid watched booleanExplanation During runtime, the UAM is trying to release a process using an invalid internal data structure. The command line interface will probably be blocked or the standby supervisor will be unable to boot.
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://tools.cisco.com/ServiceRequestTool/create, 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.
UBR7200
Error Message %UBR7200-0-UNAVAILABLE: %s measured at %s is too high: shutdown temperature %sExplanation Current temperature exceeds the max shutdown temperature
Recommended Action Determine cause of the high temperature and correct if possible.
Error Message %UBR7200-0-UNAVAILABLE: %s measured at %s is too high: shutdown voltage %sExplanation Current voltage exceeds the max shutdown voltage
Recommended Action Determine cause of the high voltage and correct if possible.
Error Message %UBR7200-0-UNAVAILABLE: %s measured at %s is too low: shutdown voltage %sExplanation Current voltage exceeds the min shutdown voltage
Recommended Action Determine cause of the low voltage and correct if possible.
Error Message %UBR7200-0-UNAVAILABLE: CMTS(%d/%d), Init failed, CSR%d=0x%04x.Explanation Most likely Hardware failure
Recommended Action Replace defective Line Card
Error Message %UBR7200-0-UNAVAILABLE: uBR requires CPU card type NPE150 or higherExplanation NPE100 is not supported in uBR
Recommended Action Upgrade CPU card to NPE150 or higher
Error Message %UBR7200-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation Most likely system or hardware failure
Recommended Action Replace Line Card
UBR7200-1
Error Message %UBR7200-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation Most likely system or hardware failure
Recommended Action Replace Line Card
UBR7200-3
Error Message %UBR7200-3-UNAVAILABLE: %sExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %UBR7200-3-UNAVAILABLE: AWACS Slot %d is deadExplanation Daughter board DSP hungs
Recommended Action Reload image, if still fail, replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: CMTS(%d/%d), Buffer ownership error, pak=0x%x.Explanation Most likely hardware failure
Recommended Action Replace defective board
Error Message %UBR7200-3-UNAVAILABLE: Can not remove Burst Profile. Burst Profile is in useExplanation Current Modulation profiles defined currently use this burst profile
Recommended Action Remove the modulation profile(s) that use this burst profile, then reissue the command.
Error Message %UBR7200-3-UNAVAILABLE: Can't allocate MAC address for interface %u/%uExplanation Your system is out of available MAC addresses.
Recommended Action Contact technical support.
Error Message %UBR7200-3-UNAVAILABLE: Cannot send maps as current_map ptr is NULL, ds-%x,current_map-%x: %sExplanation This is an internal error, or may indicate a memory problem.
Recommended Action Check your available memory. If necessary, add more memory to the system.
Error Message %UBR7200-3-UNAVAILABLE: Could not start Spectrum Management processExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %UBR7200-3-UNAVAILABLE: DSP FLASH memory failedExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: DSP SRAM failedExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: DSP SRAM semaphore failedExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: DSP failed for unknown reason(0x%x)Explanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: DSP id read 0x%x,expect 0x%xExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: DSP side dual-port SRAM failedExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: Device reported %#xExplanation Most likely hardware failure
Recommended Action Replace defective hardware
Error Message %UBR7200-3-UNAVAILABLE: Exceeds %d %sExplanation The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.
Error Message %UBR7200-3-UNAVAILABLE: Failed downloading.Explanation Failed DSP downloading
Recommended Action Reload image, if still fail replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: Failed end downloading.Explanation Failed last step of DSP downloading
Recommended Action Reload image, if still fail replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: Interface %s Port U%d invalid, highest port number is U%dExplanation Upstream port number must be valid.
Recommended Action Redo command with valid upstream port number.
Error Message %UBR7200-3-UNAVAILABLE: Interface %s, ARP reply from invalid source. Expected SID=%d, Actual SID=%dExplanation There might be a spoofing attempt going on
Recommended Action Look for possible spoofing attempt
Error Message %UBR7200-3-UNAVAILABLE: Interface %s, ARP request from invalid source. IP=%i, MAC=%e, Expected SID=%d, Actual SID=%dExplanation There might be a spoofing attempt going on
Recommended Action Look for possible spoofing attempt
Error Message %UBR7200-3-UNAVAILABLE: Interface %s, Failed to send intercept packet to server %i:%dExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %UBR7200-3-UNAVAILABLE: Interface %s, IP address %i from MAC %e is already in use. SID = %dExplanation There might be a spoofing attempt going on.
Recommended Action Look for possible spoofing attempt
Error Message %UBR7200-3-UNAVAILABLE: Interface %s, IP packet from invalid source. IP=%i, MAC=%e, Expected Interface=%s SID=%d, Actual Interface=%s SID=%dExplanation There might be a spoofing attempt going on.
Recommended Action Look for possible spoofing attempt
Error Message %UBR7200-3-UNAVAILABLE: Interface %s, IP packet from invalid source. IP=%i, MAC=%e, Expected SID=%d, Actual SID=%dExplanation There might be a spoofing attempt going on.
Recommended Action Look for possible spoofing attempt
Error Message %UBR7200-3-UNAVAILABLE: Invalid Channel ID(%s): chid=0x%02x, cmd=0x%02x, regaddr=0x%02xExplanation An internal software error 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://tools.cisco.com/ServiceRequestTool/create, 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 %UBR7200-3-UNAVAILABLE: Maximum number of SIDS have been allocated for interface %sExplanation The Maxmium number of Cable Modems are on line
Recommended Action Assign Cable Modem to another Line Card
Error Message %UBR7200-3-UNAVAILABLE: Number of slots in chassis is undefined.Explanation Data stored in midplane is bad or incomplete.
Recommended Action Contact technical support to update your system.
Error Message %UBR7200-3-UNAVAILABLE: Plx9050 id read 0x%x,expect 0x%xExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: Plx9080 id read 0x%x,expect 0x%xExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: SPI BUS READ 0x%02x BYTES SHORT(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02xExplanation Read error on PHY chip serial communications bus.
Recommended Action Line card is defective, replace it.
Error Message %UBR7200-3-UNAVAILABLE: SPI PENDING NO READ DATA(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02xExplanation Read error on PHY chip serial communications bus.
Recommended Action Line card is defective, replace it.
Error Message %UBR7200-3-UNAVAILABLE: SPI PENDING READ ERROR(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02xExplanation Read error on PHY chip serial communications bus.
Recommended Action Line card is defective, replace it.
Error Message %UBR7200-3-UNAVAILABLE: SPI PENDING WRITE ERROR(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02xExplanation Write error on PHY chip serial communications bus.
Recommended Action Line card is defective, replace it.
Error Message %UBR7200-3-UNAVAILABLE: Switching to backup dsp image failedExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: Unknown chassis model.Explanation Data stored in midplane is bad or incomplete.
Recommended Action Contact technical support to update your system.
Error Message %UBR7200-3-UNAVAILABLE: XILINX not up, reset reg is 0x%xExplanation Daughter board hardware failure
Recommended Action Replace defective daughter board
Error Message %UBR7200-3-UNAVAILABLE: failed init download.Explanation Failed initiating DSP downloading
Recommended Action Reload image, if still fail replace defective daughter board
UBR7200-4
Error Message %UBR7200-4-UNAVAILABLE: Bad timing offset %ld detected for cable modem %e.Explanation The cable modem is not using the correct starting offset during initial ranging. This causes a zero, negative timing offset to be recorded by the CMTS for this modem. The CMTS internal algorithm(s) that rely on the timing offset parameter, will exclude such modems from any analysis. Such bad modems may or may-not be able to function depending on their physical location on the cable plant
Recommended Action Locate the cable modem based on MAC address and report initial timing offset problem to the CM vendor
Error Message %UBR7200-4-UNAVAILABLE: Cable modem %e is online on both interface %s and interface %s.Explanation The cable modem has been detected on two interfaces.
Recommended Action Check for cable modems with duplicate MAC addresses.
Error Message %UBR7200-4-UNAVAILABLE: Corrupt or missing MAC address cookie using random base %eExplanation Data stored in midplane is bad.
Recommended Action Contact technical support to update your system.
Error Message %UBR7200-4-UNAVAILABLE: Hardware FaultExplanation Hardware fault in Clockcard
Recommended Action Replace clock card
Error Message %UBR7200-4-UNAVAILABLE: Invalid CPU ID, assuming revision 1Explanation CPU Revision ID is unreadable.
Recommended Action Update CPU board.
Error Message %UBR7200-4-UNAVAILABLE: Midplane data version mismatch.Explanation Data stored in midplane is out of date and needs update.
Recommended Action Contact technical support to update your system.
Error Message %UBR7200-4-UNAVAILABLE: Old version NPE-175/225 with Rev = 0x%02x system controller. Contact upgrades-info@cisco.com for replacementExplanation NPE board has been recalled due to an errata in the system controller chip.
Recommended Action Replace NPE-175/225 Board
Error Message %UBR7200-4-UNAVAILABLE: SID cannot be resolved from the leasequery reply for IP %iExplanation Relay-agent option might not be configured.
Recommended Action Make sure relay-agent option is configured. Also make sure save-relay-agent-data is enabled on CNR.
Error Message %UBR7200-4-UNAVAILABLE: Unknown MAC address block size.Explanation Data stored in midplane is bad or incomplete.
Recommended Action Contact technical support to update your system.
UBR7200-5
Error Message %UBR7200-5-UNAVAILABLE: Authorization failed for Cable Modem %e on interface %sExplanation The registration of this modem failed due to an invalid MIC string
Recommended Action Make sure the shared secret in the configuration file matches the shared secret configured in the ubr7200.
Error Message %UBR7200-5-UNAVAILABLE: Bad timer expiry in downstream traffic shaper process, Timer %xError Message %UBR7200-5-UNAVAILABLE: CMTS deleted BPI unauthorized Cable Modem %eExplanation Unauthorized cable modem deleted to enforce CM go through BPI authorization.
Recommended Action Check modem interface configuration for privacy mandatory, or errors in tftp configuration file.
Error Message %UBR7200-5-UNAVAILABLE: CMTS deleted unregistered Cable Modem %eExplanation Unregistered cable modem deleted to avoid unaccounted bandwidth usage.
Recommended Action Check modem i/f config for registration bypass, or errors in tftp config file.
Error Message %UBR7200-5-UNAVAILABLE: Handshake DSP is successful after %d ms delayExplanation DSP is up and running
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Interface %s Current total reservation of %d bps on Port U%d, exceeds its maximum configured reservation limit of %d bps.Explanation The currently reserved capacity on the upstream channel already exceeds the virtual reservation capacity of that upstream channel (based on configured subscription level limit).
Recommended Action Need to load balance modems requesting reserved upstream rate on some other upstream channel, or increase the subscription level limit on current upstream channel at increasing risk of not being able to guarantee the individual reserved rates for modems if this upstream channel is already oversubscribed beyond raw capacity
Error Message %UBR7200-5-UNAVAILABLE: Interface %s Port U%d, changed state to %sExplanation The upstream port was brought up or down.
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Interface %s Port U%d, continuous frequency hop ended at %u.%03u MHzExplanation At least one modem came back online. This message logs the abort of continuous frequency hop.
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Interface %s Port U%d, continuous frequency hop startedExplanation All modems just went offline. This message logs the start of continuous frequency hop.
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Interface %s Port U%d, frequency changed to %u.%03u MHzExplanation The upstream channel frequency was changed.
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Interface %s Port U%d, input power level changed to %d dBmVExplanation The upstream channel input power level was changed.
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Interface %s Port U%d, input power level fixed at %d dBmVExplanation Setting the upstream frequency to a fixed value caused theupstream input power level to assume a fixed value.
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Invalid DOCSIS Message received from a Cable Modem for interface %sExplanation This is a DOCSIS Message, but not an appropriate message for the uBR.
Recommended Action Locate Cable Modem sending this message and replace with DOCSIS compliant modem.
Error Message %UBR7200-5-UNAVAILABLE: New host with IP address %i and MAC %e on SID %d is ignored.Explanation Number of hosts on the SID has been exceeded.
Recommended Action Locate the Cable Modem in question
Error Message %UBR7200-5-UNAVAILABLE: Not implemented DOCSIS MESSAGE received from a Cable Modem for interface %sExplanation This uBR does not support this type of message.The system may be connected to a non-compliant modem.
Recommended Action This message is informational only. To be sure there is no problem,you may contact technical support.
Error Message %UBR7200-5-UNAVAILABLE: Recovering and switching back to regular dsp image succeededExplanation DSP recover operation using backup image succeeded
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Registration failed for Cable Modem %e on interface %s%s: %sExplanation The registration of this modem failed due to an invalid or unsupported Class of Service setting.
Recommended Action Make sure the Class of Service fields in the configuration file are set correctly.
Error Message %UBR7200-5-UNAVAILABLE: Switching to backup dsp image succeededExplanation Switching to backup dsp image succeeded
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Time scheduled event, spectrum group %u, %sExplanation A time scheduled reconfiguration event occurred on an interface.
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Trying to switch to backup dsp imageExplanation Trying to recover DSP using backup image
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-5-UNAVAILABLE: Unable to create downstream traffic shaping queuesError Message %UBR7200-5-UNAVAILABLE: Unable to fork downstream shaper processError Message %UBR7200-5-UNAVAILABLE: Upstream Channel Change not valid for interface %sExplanation The software does not support this command for this interface
Recommended Action Please use this command on a multiple upstream Line card.
UBR7200-6
Error Message %UBR7200-6-UNAVAILABLE: %s burst's preamble length in modulation profile %d is adjusted to the operable value.Explanation The preamble length in the burst profile has adjusted to the valid value.
Recommended Action Informational only
Error Message %UBR7200-6-UNAVAILABLE: Cable Clock primary reference is midplane TDM clockExplanation Clockcard primary reference is from midplane TDM clock
Recommended Action Informational only
Error Message %UBR7200-6-UNAVAILABLE: Cable clock %s reference Loss of SignalExplanation The clock reference was lost
Recommended Action Check reference source
Error Message %UBR7200-6-UNAVAILABLE: Cable clock %s reference activeExplanation The clock reference became active
Recommended Action Informational only
Error Message %UBR7200-6-UNAVAILABLE: Cable clock in Freerun modeExplanation Clockcard is in free run mode
Recommended Action Informational only
Error Message %UBR7200-6-UNAVAILABLE: Cable clock in Holdover modeExplanation Clockcard switched to holdover mode
Recommended Action Check reference source
Error Message %UBR7200-6-UNAVAILABLE: Cable clock locked to %s referenceExplanation Clockcard locked onto clock source
Recommended Action Informational only
Error Message %UBR7200-6-UNAVAILABLE: Cable modem %e has been moved from interface %s to interface %s.Explanation The cable modem has been detected ranging on a new interface.
Recommended Action Informational only
Error Message %UBR7200-6-UNAVAILABLE: Current DSP version : %d, DSP flash version : %dExplanation The current code version and the version DSP booted up with
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-6-UNAVAILABLE: Downloading dsp code completedExplanation Downloading dsp code completed
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-6-UNAVAILABLE: Downloading dsp code initiatedExplanation Downloading dsp code started
Recommended Action LOG_STD_NO_ACTION
Error Message %UBR7200-6-UNAVAILABLE: Midplane TDM clock reference defaults to ClockcardExplanation Clockcard primary reference is from midplane TDM clock
Recommended Action Informational only
UCODE-3
Error Message %UCODE-3-UNAVAILABLE: %s is %s ucode not %s, microcode/hardware mismatchExplanation The specified microcode file is for a different interface processor than specified in the configuration. The user has made a configuration error. The onboard ROM microcode will be loaded.
Recommended Action Reenter your microcode configuration command after confirming the interface type and reload the microcode.
Error Message %UCODE-3-UNAVAILABLE: Bad checksum in %s, found 0x%x expected 0x%xExplanation The microcode file is corrupted in some way; the checksum computed after reading the file from Flash does not match the one in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.
Recommended Action Reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message %UCODE-3-UNAVAILABLE: File %s at length %d is too long for buffer (size %d)Explanation The file is too large for the buffer. The onboard ROM microcode will be loaded.
Recommended Action If the error message recurs after the onboard ROM microcode is loaded, call your technical support representative for assistance.
Error Message %UCODE-3-UNAVAILABLE: Inappropriate version %u.%u for %sExplanation An attempt was made to load an inappropriate version of microcode.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %UCODE-3-UNAVAILABLE: Invalid IPC request (%d) received from (%x)Explanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has received an invalid message.
Recommended Action Verify that the proper revisions of code are selected.
Error Message %UCODE-3-UNAVAILABLE: Invalid Ucode source type (%d)Explanation Microcode source type as specified is not supported on the given platform
Recommended Action Verify that the proper revisions of code are selected.
Error Message %UCODE-3-UNAVAILABLE: Invalid attempt to load ROM ucode in slot %dExplanation Some interface processors cannot load microcode from ROM.
Recommended Action Remove the erroneous configuration statement.
Error Message %UCODE-3-UNAVAILABLE: Ucode file %s not found, system ucode loaded in slot %dExplanation The file specified by the configuration was not found in Flash. The onboard ROM microcode will be loaded so the interface can remain operational.
Recommended Action Use show flash to determine if the file is located in Flash. If the file is there, attempt to reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message %UCODE-3-UNAVAILABLE: Ucode file %s requires %s version %d.x hardwareExplanation A mismatch was detected during an attempt to load a microcode file into an interface processor. The hardware requires a different version than the one specified.
Recommended Action Use the required microcode version.
Error Message %UCODE-3-UNAVAILABLE: Ucode header corrupted in %s, found 0x%x expected 0x%xExplanation The microcode file is corrupted in some way; the checksum computed after reading the file from Flash does not match the one in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.
Recommended Action Reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message %UCODE-3-UNAVAILABLE: Unable to allocate memory during microcode reloadExplanation An attempt at memory allocation failed while downloading microcode to Interface processor.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %UCODE-3-UNAVAILABLE: Unable to allocate memory for ucode bufferExplanation A buffer is required to decompress microcode before loading it into an interface processor. This buffer could not be allocated for some reason.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %UCODE-3-UNAVAILABLE: Unable to download ucode from %s in slot %d, trying %s ucodeExplanation For some reason, the microcode file specified by the configuration is not suitable for downloading, or another error occurred. The onboard ROM microcode will be loaded so the interface can remain operational.
Recommended Action Attempt to reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message %UCODE-3-UNAVAILABLE: Unable to initialize IPC %s servicesExplanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to initialize.
Recommended Action Certain Interface Processors will not load properly. The router must be reloaded to clear the problem.
Error Message %UCODE-3-UNAVAILABLE: Unable to obtain IPC resourcesExplanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to obtain a buffer.
Recommended Action Certain interface processors will not load properly. Try the reload command again. If this message recurs, call your technical support representative for assistance.
Error Message %UCODE-3-UNAVAILABLE: Unable to read ucode file %s from flashExplanation For some reason, the microcode file was not read from Flash. Flash might be locked by another process or otherwise unavailable.
Recommended Action Use the show flash command to determine whether Flash is in use and issue another microcode reload when Flash is free. If the message recurs, call your technical support representative for assistance.
Error Message %UCODE-5-UNAVAILABLE: FDDI unit %d has obsolete microcode: please upgrade itExplanation This message occurs when an FDDI interface processor is found running microcode that does not support microcode CMT, which is required for all software releases from 10.2 on.
Recommended Action Upgrade the microcode on the interface processor.
Error Message %UDLD-3-UNAVAILABLE: UDLD error handling %s interface: %sExplanation A softare error occurred in UDLD processing associated with a specific 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://tools.cisco.com/ServiceRequestTool/create, 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.
UBL Messages
This section contains Universal Boot Loader (UBL) messages.
UBL-2
Error Message %UBL-2-SLAVE_FAIL: Could not download image due to - [chars].Explanation The standby supervisor engine could not carry out its task of downloading an image from the active supervisor engine due to the reason mentioned in the error message. This could be due to an internal error or due to an old image running on the active supervisor engine that does not support UBL. Prior error messages might provide more information about the actual problem.
Recommended Action Ensure the conditions mentioned in the message are met. If preceding error messages in the log indicate that this is an internal error, 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://tools.cisco.com/ServiceRequestTool/create, 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.
UDLD Messages
This section contains UniDirectional Link Detection (UDLD) protocolmessages.
UDLD-3
Error Message %UDLD-3-UDLD_IDB_ERROR: UDLD error handling %s interface: %sExplanation A softare error occurred in UDLD processing associated with a specific interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error: %sExplanation A softare sanity check failed in the course of UDLD processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface %s: %sExplanation A softare sanity check failed in the course of UDLD processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %UDLD-3-UDLD_NOKADIS: UDLD unable to create the kadis timer, status [dec]Explanation A failure occurred during creation of the kadis timer from UDLD pseudo preemptive process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %UDLD-3-UDLD_NOPREEMP: UDLD unable to create pseudo preemptive processExplanation A failure occurred during creation of the UDLD pseudo preemptive process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface %s, %s detectedExplanation An interface was disabled because UDLD protocol detected the cause indicated on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
UDLD-4
Error Message %UDLD-4-UDLD_PORT_FAILURE: UDLD failure reported per user request, interface [chars], [chars] detected,Explanation An interface failure was reported because UDLD protocol detected the cause indicated on the interface. Cause is likely due to bad interface hardware or cable misconfiguration. Interface not err-disabled as user choose to see error-report. User should investigate and take action.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
UDLD-6
Error Message %UDLD-6-UDLD_PORT_LINKDOWN: Fast UDLD cache times out for intf [chars], moves port to linkdown stateExplanation Fast UDLD cache entry for the reported interface times out. This could be due to either remote side port shut, LC OIR, or real link failure. UDLD moved the port to linkdown state for all cases. If this is not caused by a link failure, UDLD should receive a PM linkdown notification within the next 4 seconds. If UDLD does not receive any notification, then it will consider this a link failure and will err-disable the port.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %UDLD-6-UDLD_PORT_RESET: UDLD reset interface %sExplanation A port which had been disabled for UDLD has been reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
UFAST_MCAST_SW-3
Error Message %UFAST_MCAST_SW-3-SW-3-PROC_START_ERROR: No process available for transmitting UplinkFast packets.Explanation UplinkFast packets will not be transmitted as the process could not be created.
Recommended Action UplinkFast will not work unless you reload. If this problem persists even after reload, please contact your Cisco Technical Support representative with the configuration and technical support information.
UFAST_MCAST_SW-4
Error Message %UFAST_MCAST_SW-4-UNAVAILABLE: No memory is available for transmitting UplinkFast packets on Vlan %d.Explanation UplinkFast packets will not be transmitted on Vlan %d due to a lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
UNIX-1
Error Message %UNIX-1-UNAVAILABLE: System abortedExplanation The system aborted. Record the output from the following commands: show proc mem (repeated twice) show memory show buffers show version show runing-config.
Recommended Action Provide this information and the error message to your technical support representative.
UNIXLC_SPA-3
Error Message %UNIXLC_SPA-3-CMDNOINT: HWIDB Null for command %d, port %#xExplanation The Route Processor passed down a port number that is unknown on the carrier card.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXLC_SPA-3-INVALID_IF: Attempted to access HWIDB for port %u on slot %d subSlot %dExplanation The IOU attempted to access the HWIDB associated with a non-existent port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXLC_SPA-3-UNIXIPCALLOCFAIL: Failed to allocate Common IPC buffer %sExplanation The Carrier Card failed to allocate a buffer for communication with the Route Processor.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXLC_SPA-3-UNAVAILABLE:Explanation Pointer to object for bay %d is NULL.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXLC_SPA-3-UNAVAILABLE: Attempted to access HWIDB for port %u on slot %d subSlot %dExplanation The IOU attempted to access the HWIDB associated with a non-existent port.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Bay %d - FCI type not setExplanation An FCI type of zero was detected
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Bay %d - Invalid anyphy number %u for vc %dExplanation Interface has invalid anyphy mumber
Recommended Action Seach 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. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Bay %d 12V power is %sExplanation SPA 12V power fault indicator
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Bay %d initialization failureExplanation Failed to create SPI4 subblock
Recommended Action Seach 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, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Bay %d, spi4 configuration failure, error %dExplanation Failed to configure SPI4 interface
Recommended Action Seach 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, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Bay %d: %sExplanation An unexpected error has occurred.
Recommended Action Seach 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, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Creation: port %d vc %dExplanation Failed to create a hwidb.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXLC_SPA-3-UNAVAILABLE: EFC error - interface %s, vc %d, anyphy %d, err_code %d : %sExplanation Failed to configure efc channel/parameters
Recommended Action Seach 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, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Failed to %s SPA reference clock on %sExplanation The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error.
Recommended Action No action is required.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Failed to allocate Common IPC buffer %sExplanation The Carrier Card failed to allocate a buffer for communication with the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Failed to initialize SPA main c2w bus for subslot %d (status = %d)Explanation The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error.
Recommended Action No action is required.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Failed to provision EFC for interface %s (status = %d)Explanation The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error.
Recommended Action No action is required.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Failed to unprovision EFC for VC %s (status = %d)Explanation The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error.
Recommended Action No action is required.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Failed to update EFC flow control identifier for interface %s (status = %d)Explanation The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error.
Recommended Action No action is required.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: HWIDB Null for command %d, port %#xExplanation The Route Processor passed down a port number that is unknown on the carrier card.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: ISR return code out of range. rc=%dExplanation The ISR error return code is out of range.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXLC_SPA-3-UNAVAILABLE: Link record error - Bay %d vc %d, error code %dExplanation Error processing link record structure
Recommended Action Seach 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. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
Error Message %UNIXLC_SPA-3-UNAVAILABLE: SPA Sonet clock has failed (status = 0x%08x)Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM will be affected.
Recommended Action If the SPA Sonet clock does not recover, perform an OIR. 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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXLC_SPA-3-UNAVAILABLE: SPA Sonet clock has recovered (status = 0x%08x)Explanation SPA Sonet clock has recovered
Recommended Action No action is required.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Subslot %d, spa controller initialisation failure, error %dExplanation Failed to initialise SPA controller
Recommended Action Seach 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, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: Subslot, spa controller EFC configuration failure, error %dExplanation Failed to configure SPA controller EFC
Recommended Action Seach 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, 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-3-UNAVAILABLE: subSlot %d, spatype 0x%x. Device error: %sExplanation An error related to a device on the SPA is detected.
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://tools.cisco.com/ServiceRequestTool/create, 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.
UNIXLC_SPA-4
Error Message %UNIXLC_SPA-4-UNAVAILABLE: Subslot %d SPA BUS access failed. No SPA present errorExplanation SPABUS has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-4-UNAVAILABLE: Subslot %d, %s SPA BUS access failed. timeout=%u err=%u par=%u err_c=0x%x addr=0x%08x data =0x%xExplanation SPABUS has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXLC_SPA-4-UNAVAILABLE: Total SPA bandwidth exceeds line card capacity of %lu MbpsExplanation The total bandwidth of SPAs exceeds the rated capacityof this line card.
Recommended Action Refer to the line card guidelines for the maximum allowedaggregated SPA bandwidth for the line card
Error Message %UNIXLC_SPA-4-UNAVAILABLE: Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supportedExplanation The total bandwidth of SPAs exceeds the rated capacityof this line card.
Recommended Action Refer to the line card guidelines for the maximum allowedaggregated SPA bandwidth for the line card
UNIXLC_SPA-6
Error Message %UNIXLC_SPA-6-UNAVAILABLE: Bay %d %s changed to %sExplanation SPA OIR Sequence
Recommended Action No action is required.
UNIXRP-3
Error Message %UNIXRP-3-CARDERR: %sExplanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXRP-3-UNAVAILABLE: %s %u (%s)Explanation Failed to create IPC seat for line card
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXRP-3-UNAVAILABLE: %s (%u)Explanation IPC slot 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXRP-3-UNAVAILABLE: %sExplanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIX_SPA-3-POWER_CYCLE: %s occurred on Shared Port Adapter %u/%uExplanation An error has occurred which will cause the Shared Port Adapter to be power cycled
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXRP_SPA-3-UNAVAILABLE:Explanation Pointer to object for slot %d, bay %d is NULL.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXRP_SPA-3-UNAVAILABLE: Creation: slot %d subSlot %d port %d vc %dExplanation Failed to create an interface hwidb.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXRP_SPA-3-UNAVAILABLE: Failed to allocate IPC buffer %sExplanation The RP failed to allocate a buffer for communication with a SPA
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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: Failed to allocate a flow control identifier for interface %sExplanation The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: Failed to initialize data structure for SPA port %d/%d/%dExplanation A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error.
Recommended Action No action is required.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: Failed to provision interface %sExplanation The SPA driver is not able to provision the interfacespecified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise, this indicates a hardware error.
Recommended Action No action is required.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: Failed to release a flow control identifier for interface %s (status = %d)Explanation The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: Failed to retrieve datapath identifier for interface %sExplanation The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: Failed to update connection identifier for interface %sExplanation The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: HWIDB not found: slot %d, bay %d, port %dExplanation A NULL hwidb is encountered
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXRP_SPA-3-UNAVAILABLE: NULLExplanation A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error.
Recommended Action No action is required.
Error Message %UNIXRP_SPA-3-UNAVAILABLE: Power to IPSEC-SPA-2G in %s is denied because it has exceeded the number allowed(%d)Explanation The number of IPSEC-SPA-2G in a chassis is limited.This message is displayed when the number of IPSEC-SPA-2G inthe chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2G
Error Message %UNIXRP_SPA-3-UNAVAILABLE: slot %d subSlot %d, PID %sExplanation Failed to get information about the host linecard.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXRP_SPA-3-UNAVAILABLE: slot %d subSlot %d, spaType 0x%xExplanation Failed to get information about the host linecard.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXRP_SPA-3-UNAVAILABLE: slot=%d port=%d, hwidbType=0x%x, max_port_num=%d, LCtype=0x%xExplanation The port number is out of range.
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://tools.cisco.com/ServiceRequestTool/create, 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.
UNIXRP_SPA-4
Error Message %UNIXRP_SPA-4-UNAVAILABLE: %s: Expecting response to interface configuration command %u but received response to command %u.Explanation An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message is repeatable, please 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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIXRP_SPA-4-UNAVAILABLE: %s: No response for interface configuration command %uExplanation A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.
Recommended Action No action is required.
UNIXRP_SPA-6
Error Message %UNIXRP_SPA-6-UNAVAILABLE: Module %u reload due to SPA insert in %u/%u.Explanation When inserting a SPA on this carrier card, the cardis reset.
Recommended Action No action is required.
UNIX_BPD-3
Error Message %UNIX_BPD-3-UNAVAILABLE: %s: (%d)Explanation HWIDB Lookup 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIX_BPD-3-UNAVAILABLE: %s: (%s)Explanation Packet Not Available
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://tools.cisco.com/ServiceRequestTool/create, 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.
UNIX_IFUTIL-3
Error Message %UNIX_IFUTIL-3-UNAVAILABLE: %s Pool Creation Error for hwidb: %sExplanation POOL Creation 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://tools.cisco.com/ServiceRequestTool/create, 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.
Error Message %UNIX_IFUTIL-3-UNAVAILABLE: Pak not available, %s: %sExplanation The running configuration was too big to be synced
Recommended Action No action is required.
UNIX_SPA-3
Error Message %UNIX_SPA-3-UNAVAILABLE:Explanation Pointer to a SPA object is NULL.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: %sExplanation Memory allocation 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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: %s called with NULL hwidbExplanation A NULL hwidb is encountered
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: %s did not complete %d/%dExplanation An error has occured during diagnostic test.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: %s occurred on Shared Port Adapter %u/%uExplanation An error has occurred which will cause the Shared Port Adapter to be power cycled
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: %s vector is not initialized. spaType=0x%xExplanation A required function vector is not initialized
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: %s virtual function table is not initialized. spaType=0x%xExplanation A required function table is not initialized
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: Data conversion error (%s, 0x%X)Explanation An internal software error has occured when converting the data specified in the message from one representation to another.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: Failed to create SPA SBExplanation Failed to create a SPA subblock.
Error Message v%UNIX_SPA-3-UNAVAILABLE: Failed to send configuration for %s to carrier-card for subslot=%d/%dExplanation Sending configuration 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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: IPC failure while %sExplanation An error has occurred while prepareing or sending an IPC message.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: cardwide-port = %d, max cardwide-port = %dExplanation Invalid cardwide-port number.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: index1= %d, index2= %d, maxIndex= %dExplanation Invalid index range.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: index= %d, spaType=0x%x, slot %d subSlot %d slotunit %d vc %dExplanation Index for the interface is not valid.
Error Message v%UNIX_SPA-3-UNAVAILABLE: interface type %s, slot %d port %d vc %d : %sExplanation Data required to support the interface is not available.
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://tools.cisco.com/ServiceRequestTool/create, 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 %UNIX_SPA-3-UNAVAILABLE: slot= %d, max slot = %dExplanation &