Cisco IOS Release 15.x SY System Message Guide

SWEPA-6

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-6

Explanation 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-5

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.

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-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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

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

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

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

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

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

Explanation The switch has received ARP packets that have been permitted as a result of ACL match.

Recommended Action LOG_STD_NO_ACTION

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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation ISSU of this SSM Segment is not supported.

Recommended Action Not Available.

SW_VLAN-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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.

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.

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.

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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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-2

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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--

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.

SYS-1

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

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.

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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

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.

Explanation 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.

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.

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.

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.

Explanation 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

Explanation 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.

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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation A software error occurred.

Recommended Action Copy the message exactly as it appears, and report it your technical support representative.

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.

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.

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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation 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.

Explanation 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.

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.

Explanation 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.

Explanation 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.

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

Explanation 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.

Explanation 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.

Explanation 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.

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.

Explanation 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.

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.

Explanation 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.

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.

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.

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.

Explanation 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.

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.

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.

Explanation 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.

Explanation 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.

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.

Explanation 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.

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.

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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

Explanation 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.

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

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.

Explanation 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.

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

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.

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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

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.

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.

Explanation 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.

Explanation 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

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

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.

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.

Explanation 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.

Explanation 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.

Explanation 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.

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.

Explanation 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

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation 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.

Explanation 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/cgi-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.

Explanation This message indicates that the semaphore creation for the specified mempool failed.

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.

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation 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.

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.

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

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.

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

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.

Explanation 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

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.

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.

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

Explanation 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.

Explanation 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.

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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

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.

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.

Explanation 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/cgi-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.

Explanation 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/cgi-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.

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.

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.

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.

Explanation 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.

Explanation 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.

Explanation Redirection of output to URL failed.

Recommended Action Check for free space on destination URL and retry.

Explanation 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

Explanation 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.

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

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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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

Explanation 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

Explanation 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

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.

Explanation SNMP is writing the current configuration to a network host.

Recommended Action These are notification messages only. No action is required.

Explanation SNMP is reading the host configuration from a network host.

Recommended Action This is a notification message only. No action is required.

Explanation SNMP is reading the network configuration from a network host.

Recommended Action This is a notification message only. No action is required.

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation 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.

Explanation A software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Explanation 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.

Explanation 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

Explanation 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.

Explanation The owner of this string must have freed their structure without letting the string database know

Recommended Action No action is required

SYS-5

Explanation A scheduled reload that was requested for the router has been cancelled.

Recommended Action No action is required.

Explanation An internal table entry became corrupt.

Recommended Action Copy the message exactly as it appears, and report it your technical support representative.

Explanation 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.

Explanation The router’s configuration was changed.

Recommended Action This is a notification message only. No action is required.

Explanation The router’s configuration was changed.

Recommended Action This is a notification message only. No action is required.

Explanation 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

Explanation 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

Explanation The configuration was written successfully.

Recommended Action This is a notification message only. No action is required.

Explanation The configuration was written successfully.

Recommended Action This is a notification message only. No action is required.

Explanation 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.

Explanation A scheduled reload has been requested for the router.

Recommended Action No action is required.

Explanation A reload or restart was requested.

Recommended Action This is a notification message only. No action is required.

Explanation A switchover was requested.

Recommended Action This is a notification message only. No action is required.

Explanation A switchover was requested.

Recommended Action This is a notification message only. No action is required.

Explanation A reload or restart was requested.

Recommended Action This is a notification message only. No action is required.

SYS-6

Explanation 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.

Explanation 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.

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.

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.

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

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

Explanation 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.

Explanation 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.

Explanation Your system is not configured to be a bridge.

Recommended Action Configure the bridging software.

Explanation 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.

Explanation Syslog logging to specified server or host(vrf) has started or stopped

Recommended Action LOG_STD_NO_ACTION

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.

Explanation 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.

Explanation 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

Explanation 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

Explanation 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.

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.

Explanation This message indicates that the system clock has been modified.

Recommended Action This is informational message.

Explanation 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.

Explanation 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.

Explanation 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

Explanation The Embedded Syslog Manager has been shut down

Recommended Action LOG_STD_NO_ACTION

Explanation 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

Explanation Health monitor failed to setup the monitoring command on that particular shelf

Explanation An internal software error occurred.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation An internal software error occurred.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

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.

Explanation Two shelves with same shelf-id are configured in the system.

Recommended Action Change the shelf-id for one of the shelf.

Explanation An internal software error occurred.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation Most likely the performance collector process has terminated.

Explanation An internal software error occurred.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation An internal software error occurred.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation SDP protocol on system controller has detected that a particular shelf configuration has changed.

Explanation No SDP hello packets were received from the particular shelf, this could indicate that particular router shelf is down or is mis-configured.

Explanation 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.

Explanation SDP protocol on system controller has detected that a particular shelf has reload.

Explanation SDP protocol on system controller didn’t receive hello packets from particular shelf.

Explanation 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

Explanation 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

Explanation SDP protocol on system controller has detected a particular shelf.

Explanation System Controller found a Shelf with an invalid ip address

Recommended Action Check the IP address set on the Shelf

Explanation SDP protocol on system controller has detected a particular shelf.

SYSLOGD-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation Exceeded the maximum Syslog files allowed.

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

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

Explanation Failed to read a file.

Explanation Failed to write a syslog file.

Explanation Illegal file system.

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

Explanation Unknown command or device name, or unable to find device address.

SYSLOG_SERVER-4

Explanation There is no configuration change to the syslog-server

Explanation No memory left.

Recommended Action The System Controller is running very low on memory.

Explanation No syslog file.

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

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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation A process was restarted through the CLI.

Recommended Action This is an informational message only. No action is required.

SYSMGR_PLATFORM-5

Explanation 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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

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.

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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

Explanation The server configuration failed.

Recommended Action Please configure the server properly.

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/cgi-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.

Explanation The server is not configured.

Recommended Action Please configure a server before un-configuring it.

Explanation 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

Explanation 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

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.

Explanation 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

Explanation 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.

Explanation 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.

Explanation Migration from tacacs-server host CLI to tacacs server CLI.

Recommended Action Please try to use the new CLI.

TAGCON-3

Explanation A problem was encountered in clean up following termination of a Tag Distribution Protocol (TDP) session.

Recommended Action ACTION_COPY_REPORT_TAGCON

Explanation An operation on the TDP Directed Adjacency data structure failed.

Recommended Action ACTION_COPY_REPORT_TAGCON

Explanation 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.

Explanation EXPLANATION_ADDR_TBL_TAGCON

Recommended Action ACTION_TOGGLE_TAG_IP_TAGCON

Explanation 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

Explanation An attempt to allocate a label switching data structure failed because of a low memory condition.

Recommended Action ACTION_STD_LOW_MEMORY_TAGCON

Explanation 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.

Explanation 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.

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.

Explanation An operation involving the state machine for a TDP peer failed.

Recommended Action ACTION_COPY_REPORT_TAGCON

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

Explanation 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.

Explanation 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

Explanation An operation on the state machine for the tag distribution and control process failed.

Recommended Action ACTION_COPY_REPORT_TAGCON

Explanation EXPLANATION_ADDR_TBL_TAGCON

Recommended Action ACTION_TOGGLE_TAG_IP_TAGCON

Explanation 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.

Explanation The tag distribution and control process failed to initialize itself. The probable cause is insufficient memory.

Recommended Action ACTION_STD_LOW_MEMORY_TAGCON

Explanation An attempt to create the tag distribution and control process failed. The probable cause is insufficient memory.

Recommended Action ACTION_STD_LOW_MEMORY_TAGCON

Explanation 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

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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

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-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation Transparent bridging was configured on an interface that does not support it.

Recommended Action Remove transparent bridging from the configuration on the specified interface.

Explanation 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.

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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation This is a configuration problem. The specified extended access list either does not exist or contains an error.

Recommended Action Correct the configuration problem.

Explanation 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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-2

Explanation An internal software error occurred.

Recommended Action If this message recurs, copy the message exactly as it appears and contact your technical support.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation An internal software error occurred.

Recommended Action If this message recurs, contact your technical support representative.

Explanation An internal software error occurred.

Recommended Action If this message recurs, contact your technical support representative.

Explanation 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.

Explanation 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation TCP initialization failed.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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

Explanation The clock source has failed.

Recommended Action If alternate source is available, it will be used.

Explanation This warning message indicates a change in the clock source.

Recommended Action No action required.

Explanation This debug message indicates a clock state change

Recommended Action No action required.

Explanation This warning message indicates a invalid clock event

Recommended Action No action required.

TDP-3

Explanation An action attempted by the Tag Distribution Protocol (TDP) encountered an unexpected condition.

Recommended Action ACTION_COPY_REPORT_TDP

Explanation An action attempted by the Tag Distribution Protocol (TDP) implementation failed.

Recommended Action ACTION_COPY_REPORT_TDP

Explanation 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.

Explanation 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.

Explanation 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.

Explanation An error occurred while attempting to read a TDP PDU received from a peer.

Recommended Action ACTION_NEW_SESSION_TDP

Explanation 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

Explanation 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

Explanation 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

Explanation 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

Explanation 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

Explanation 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

Explanation 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

Explanation 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

Explanation 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

Explanation An unknown Tag Distribution Protocol (TDP) protocol information element (PIE) type has been received from a peer.

Recommended Action ACTION_IGNORE_PIE_TDP

Explanation An operation on the state machine for a TDP peer failed.

Recommended Action ACTION_COPY_REPORT_TDP.

TDP-4

Explanation 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.

Explanation 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

Explanation 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

Explanation 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.

Explanation A violation of the TDP protocol by a TDP peer has been detected.

Recommended Action ACTION_NEW_SESSION_TDP

TDP-5

Explanation This is an informational message generated by the Tag Distribution Protocol (TDP) implementation.

Recommended Action No action is required.

Explanation EXPLANATION_ACL_TDP

Recommended Action No action is required.

TEMUX84-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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.

Explanation A DMA failure occurred.

Recommended Action Verify that the port adapter is properly seated in the bay.

Explanation 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.

Explanation 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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

Explanation 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

Explanation An operation on the Tag Information Base (TIB) involving a locally assigned (incoming) tag failed.

Recommended Action ACTION_OMIT_OPER_TIB

Explanation An operation on the Tag Information Base (TIB) involving a tag assigned by a TDP peer failed.

Recommended Action ACTION_OMIT_OPER_TIB

Explanation An operation on the Tag Information Base (TIB) data structure failed.

Recommended Action ACTION_COPY_REPORT_TIB

Explanation An action attempted by the Tag Information Base (TIB) implementation failed.

Recommended Action ACTION_COPY_REPORT_TIB

Explanation 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

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.

Explanation An operation on the Tag Information Base (TIB) state machine failed.

Recommended Action ACTION_COPY_REPORT_TIB.

TIB-5

Explanation 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.

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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation An attempt was made to delete an entry not in the queue.

Recommended Action Advisory message only. No action required.

TIDP-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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.

Explanation 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.

Explanation 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

Explanation 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

Explanation 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

Explanation 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-6

Explanation The fragment offset == 1 (fo1) packets aggregate threshold has exceeded the acceptable value.

Recommended Action Reduce the interface high-threshold values.

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.

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.

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-2

Explanation The router was unable to create a TIDP-based Mitigation Services (TMS) controller process.

Recommended Action Reload the device.

TMS-4

Explanation 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

Explanation The TMS process cannot operate due to an internal system error.

Recommended Action Reload the device

Explanation The EOU process cannot operate due to an internal system error.

Recommended Action Reload the device

Explanation This message indicates that the specified process is stopped.

Recommended Action Reload the device

Explanation This is an unknown message for the TMS controller process.

Recommended Action File a ddts with Cisco

Explanation The TMS process received an unknown message event.

Recommended Action If this message recurs, reload the device.

TMS-6

Explanation This messages informs that the consumer has cleared all the stats.

Recommended Action This is an informational message and no action is required.

Explanation This messages informs that the tms consumer is configured or unconfigured

Recommended Action This is an informational message and no action is required.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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.

Explanation 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-2

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

TN-3

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.

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

Explanation 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-3

Explanation 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

Explanation 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

Explanation The specified report is ready and can be viewed by the users.

Recommended Action This is an informational message only. No action is required.

Explanation The specified report has been deleted by the specified user.

Recommended Action This is an informational message only. No action is required.

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.

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.

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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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.

Explanation 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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

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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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

Explanation 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

Explanation 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

Explanation A tracked object has changed its state.

Recommended Action No action is required.

TRAFFIC_UTIL-4

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-2

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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.

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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

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.

Explanation The framer processor did not reply to the read request during a specified amount of time.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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

Explanation The clock switching software has failed to allocate memory while adding a clock.

Recommended Action LOG_STD_NO_ACTION

TRUNK_CLOCK-6

Explanation 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

Explanation The TDM primary clock is switching from the default clock to the user configured external clock in motherboard.

Recommended Action LOG_STD_NO_ACTION

Explanation 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

Explanation The TDM primary clock is switching from the default clock to the user configured trunk clock.

Recommended Action LOG_STD_NO_ACTION.

Explanation The clock selection algorithm has failed to select any clock as the TDM primary clock.

Recommended Action LOG_STD_NO_ACTION.

TRUNK_DFC-3

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation Internal Finite State Machine Error.

Recommended Action Contact your technical support representative, include the full text of the error message.

Explanation 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.

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.

Explanation 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

Explanation 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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

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.

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.

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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation An internal software error occurred during manipulating the tunnel endpoint database.

Recommended Action No action is required.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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.

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

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.

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.

Explanation 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.

Explanation An error was encountered on a unidirectional link routing (UDLR) interface.

Recommended Action No action is required.

TUN-5

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

TWOBIT

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

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

Explanation 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

Explanation Bad input stream.

Recommended Action This is an informational message. LOG_STD_NO_ACTION

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.

Explanation 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.

Explanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.

Explanation The router is out of memory.

Recommended Action This is an informational message. LOG_STD_NO_ACTION

Explanation Bad input stream.

Recommended Action This is an informational message. LOG_STD_NO_ACTION

Explanation 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

Explanation 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

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

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

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

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-3

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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center 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.