Table Of Contents
SSSMGR Messages
The following are Subscriber Service Switching (SSS) Manager messages.
Error Message%SSSMGR-5-IFCFG_NOTALLWED_IN_SVC : Interface-config not allowed at service config level, ignoring
Explanation Interface-config attribute is not allowed while in a service profile. It is supported only in user profiles.
Recommended Action Remove the interface-config attribute from the service profile and reconfigure using a user profile.
Error Message%SSSMGR-3-INVALID_SERVICE_TYPE : Received an INVALID service type ([dec])[chars].
Explanation An internal SSS Manager 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%SSSMGR-3-UNSUPPORTED_CFG : Unsupported configuration detected: [uid: [int]] [chars]
Explanation Unsupported configuration 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SSSMGR-5-UNSUPPORTED_CFG_NOTICE : Unsupported configuration detected, [chars]
Explanation The value of the specified configuration parameter was out of range. This is not considered an error as the value was adjusted to be within the supported range. Update the configuration source to a value within the supported range to avoid this message.
Recommended Action No action is required.
STP_ISSU Messages
The following are STP In Service Software Upgrade/Downgrade messages.
Error Message%STP_ISSU-3-BUFFER : STP ISSU client failed to get buffer for message, error [dec]
Explanation STP ISSU client failed to get buffer for building a negotiation message. Thus, it can send the negotiation message to the standby unit. When there is a problem in the negotiation, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-CAPABILITY : STP ISSU client [chars]
Explanation STP ISSU client observed an error during capability negotiation. When this error happens there is a mismatch between 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. Enter the show issu capability entries <client_id>,
show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-INIT : STP ISSU client initialization failed at [chars], error [chars]
Explanation STP ISSU client could not be initialized, this will cause catastrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-MSG_NOT_OK : STP ISSU client message [dec] is not compatible
Explanation STP ISSU client received an incompatible message from the peer unit. Since the message is not compatible, it cannot be processed by this unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message group <client_id>,
show issu session <client_id> and
show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-MSG_SIZE : STP ISSU client failed to get the message size for message [dec]
Explanation STP ISSU client failed to calculate message size for the message specified. The OIR ISSU client will not be able 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. Enter the show issu message group <client_id>,
show issu session <client_id> and
show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-POLICY : STP ISSU client message type [dec] is [chars]
Explanation STP ISSU client received an message type which it does not support. The 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. Enter the show issu session <client_id> command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-SEND_FAILED : STP ISSU client failed to send a negotiation message, error [dec]
Explanation STP ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-SESSION : STP ISSU client [chars]
Explanation STP ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id>,
show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-SESSION_UNREGISTRY : STP ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The STP ISSU client failed to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%STP_ISSU-3-TRANSFORM : STP ISSU client [chars] transform failed, error [chars]
Explanation STP ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message cannot be applied on the standby unit. In both cases the STP 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. Enter the show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.STP_SP Messages
The following are STP Platform messages.
Error Message%STP_SP-3-STP_MODE_CHANGE_NOT_ALLOWED : Unable to program port ASIC MAC match register on one or more slots. Can't run change STP mode.
Explanation STP attempted to reserve and program the port ASIC MACmatch registers and there are insufficient match registers available. PVST and rapid-PVST cannot be run.
Recommended Action To free MAC match registers, disable protocols that use the MAC match register. Protocols using port ASIC match registers can be viewed with remote command switch show platform mrm info.
SVCLC Messages
The following are Service Line Card (SVCLC) firewall SP notice messages.
Error Message%SVCLC-5-SVCLCMULTI : Group [dec] being tied to more than one module
Explanation The specified group is tied to multiple service modules. A group should not be tied to more than one service module unless a failover configuration is being used.
Recommended Action If a failover configuration is in use, no action is required. Otherwise enter the show svclc module command to find out which group is being tied to more than one module. Then remove multiple associations by entering the no svclc module <mod> vlan-group <group> command.
Error Message%SVCLC-5-SVCLCNTP : Could not update clock on the module [dec], rc is [dec]
Explanation Either the line card or the Cisco IOS software encountered some problems while sending a clock update from IOS to the linecard.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SVCLC-5-SVCLCSCP : Service module SCP communication failed for module [dec], subopcode is [dec]
Explanation Either the line card or the Cisco IOS software encountered some problems while communicating through SCP channels.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SVCLC-5-SVCLCVTPMODE : VTP mode is set to non-transparent
Explanation VTP mode is not transparent, thus VTP might dynamically modify VLANs, including those that are tied to the Service Modules.
Recommended Action Change the VTP to transparent mode by entering the vtp mode transparent command.
SW_DAI Messages
The following are Dynamic ARP Inspection messages.
Error Message%SW_DAI-4-PACKET_BURST_RATE_EXCEEDED : [dec] packets received in [dec] seconds on [chars].
Explanation The switch has received the given number of ARP packets in the specified burst interval. The interface is errdisabled when the switch receives packets at a rate higher than the configured packet rate every second over the configured burst interval. The message is logged just before the interface is err-disabled, and if the configured burst interval is more than a second.
Recommended Action LOT_STD_NO_ACTION.
Error Message%SW_DAI-4-PACKET_RATE_EXCEEDED : [dec] packets received in [dec] milliseconds on [chars].
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.This message is logged when the burst interval is set to 1 second.
Recommended Action LOT_STD_NO_ACTION.
SWITCH_SPAN_ISSU Messages
The following are Span Switch In Service Software Upgrade/Downgrade messages.
Error Message%SWITCH_SPAN_ISSU-3-BUFFER : span switch ISSU client failed to get buffer for message, error [dec]
Explanation Span switch ISSU client failed to get buffer for building a negotiation message. Thus, it cannot send the negotiation message to the standby unit. When there is a problem in the negotiation, 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-CAPABILITY : span switch ISSU client [chars]
Explanation Span switch ISSU client observed an error during capability negotiation. When this error happens, 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. Enter the show issu capability entries <client_id>, show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-INIT : span switch ISSU client initialization failed at [chars], error [chars]
Explanation Span switch ISSU client could not be initiailzed, this will cause catastrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-MSG_NOT_OK : span switch ISSU client message [dec] is not compatible
Explanation Span switch ISSU client received an incompatible message from the peer unit. Since the message is not compatible it cannot be processed by this unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message group <client_id>, show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-MSG_SIZE : span switch ISSU client failed to get the message size for message [dec]
Explanation Span switch ISSU client failed to calculate message size for the message specified. The span switch ISSU client will not be able 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. Enter the show issu message group <client_id>, show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-POLICY : span switch ISSU client message type [dec] is [chars]
Explanation Span switch ISSU client received a message type which it does not support. The 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. Enter the show issu session <client_id> command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-SEND_FAILED : span switch ISSU client failed to send a negotiation message, error [dec]
Explanation Span switch ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation, the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-SESSION : span switch ISSU client [chars]
Explanation Span switch ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id>, show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SWITCH_SPAN_ISSU-3-TRANSFORM : span switch ISSU client [chars] transform failed, error [chars]
Explanation Span switch ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message cannot be applied on the standby unit. In both cases 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. Enter the show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SW_MGR Messages
The following Segment Switch Manager messages.
Error Message%SW_MGR-3-SSM_SEG_ISSU : SSM Segment ISSU: [chars] not supported.
Explanation ISSU of this SSM Segment is not supported.
Recommended Action No action is required.
SW_VLAN Messages
The following are VLAN manager messages.
Error Message%SW_VLAN-4-BAD_VLAN_DOMAIN_NAME_LENGTH : VLAN configuration file contained incorrect domain name length: [int]
Explanation The VLAN configuration file read by the VLAN manager did not contain a valid domain name length. Thus, it has been rejected.
Recommended Action Provision VTP domain name again.
Error Message%SW_VLAN-4-BAD_VLAN_PASSWORD_LENGTH : VLAN configuration file contained incorrect VTP password length: [int]
Explanation The VLAN configuration file read by the VLAN manager did not contain a valid VTP password length. Thus, it has been rejected.
Recommended Action Provision VTP password again.
Error Message%SW_VLAN-4-MAX_SUB_INT : The number of sub-interfaces allocated for interface [chars] has exceeded recommended limits of [dec]
Explanation The number of sub-interfaces allocated for the interface has exceeded recommended limits.
Recommended Action Reduce the number of sub-interfaces allocated for the interface as it has exceeded the recommended limit.
Error Message%SW_VLAN-4-VLANMGR_INVALID_DATABASE_DATA : VLAN MANAGER received bad data of type [chars]: value [dec] from function [chars]
Explanation Invalid data was received by the VLAN MANAGER from a VLAN configuration database routine.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN-6-VTP_DOMAIN_NAME_CHG : VTP domain name changed to [chars].
Explanation The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.
Recommended Action No action is required.
Error Message%SW_VLAN-6-VTP_MODE_CHANGE : VLAN manager changing device mode from [chars] to [chars].
Explanation Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is.
Recommended Action No action is required.
Error Message%SW_VLAN-4-VTP_PRIMARY_SERVER_CHG : [enet] has become the primary server for the [chars] VTP feature
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.
SW_VLAN_ISSU Messages
The following are Switch VLAN ISSU messages.
Error Message%SW_VLAN_ISSU-3-CAP_INVALID_SIZE : Switch Vlan ISSU client capability list is empty.
Explanation The Switch Vlan ISSU client capability exchange list size is invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entires <Client_ID> command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-3-CAP_NOT_COMPATIBLE : Switch Vlan ISSU client capability exchange result incompatible.
Explanation The Switch Vlam ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu negotiated capability <Session_ID> command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-2-GET_BUFFER : Switch Vlan ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Switch Vlan ISSU client failed 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. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-2-INIT : Switch Vlan ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Switch Vlan ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-3-INVALID_SESSION : Switch Vlan ISSU client does not have a valid registered session.
Explanation The Switch Vlan ISSU client does not have a valid registered session.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id>, show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER : 'Message Type [dec]' is not supported by Switch Vlan ISSU client at peer
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. Enter the show issu message group <client_id>, show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-3-MSG_NOT_OK : Switch Vlan ISSU client 'Message Type [dec]' is not compatible
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. Enter the show issu message group <client_id>, show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-3-MSG_SIZE : Switch Vlan ISSU client failed to get the MTU for Message Type [dec].Error: [dec] ([chars])
Explanation The Switch Vlan ISSU client failed to calculate the MTU for the specified message. The Switch Vlan ISSU client is not able 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. Enter the show issu message group <client_id>, show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-2-SEND_NEGO_FAILED : Switch Vlan ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Switch Vlan ISSU client failed 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. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-2-SESSION_NEGO : Switch Vlan ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
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. Enter the show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-2-SESSION_REGISTRY : Switch Vlan ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Switch Vlan ISSU client failed 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. Enter the show issu capability entries <client_id>, show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-3-SESSION_UNREGISTRY : Switch Vlan ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Switch Vlan ISSU client failed to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SW_VLAN_ISSU-3-TRANSFORM_FAIL : Switch Vlan ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
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 both cases, 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. Enter the show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SYS Messages
The following are operating system messages.
Error Message%SYS-3-ABRUPTTERM : Abrupt termination of tty session for [chars] [t-line]
Explanation An internal software error 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-2-ALREADYFREE : Buffer [hex] already in free pool [chars]
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 the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-2-ASSERTION_FAILED : Assertion failed: "[chars]"
Explanation An internal state consistency check failed. Correct operation cannot be guaranteed, and the system has been halted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADBLOCK : Bad block pointer [hex]
Explanation A block of memory at the indicated location is corrupt. An internal check of memory block pointers indicates an inconsistency.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, then the router will need to reloaded manually.Error Message%SYS-2-BAD_BM_ARG : Invalid BM index boolean used as argument ([dec])
Explanation An illegal boolean manager index argument was referenced.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-2-BAD_BM_NAME : Invalid BM name
Explanation An illegal name string was registered with the BM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-2-BADBUFFER : Attempt to use [chars] buffer as [chars], ptr= [hex], pool= [hex]
Explanation A hardware or software error occurred. An inconsistency was encountered while processing a packet 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADDISP : Bad disposal code [hex] in [chars]
Explanation An invalid status code has been passed to a buffer deletion routine. The buffer will be correctly returned to the free pool, but will not be correctly counted in the per-protocol statistics. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADFREEMAGIC : Corrupt free block at [hex] (magic [hex])
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.Error Message%SYS-3-BADFREEPTRS : Bad [chars] pointer [hex] at [hex] ([chars] = [hex])
Explanation A pointer in the block header at the indicated location is corrupt. An inconsistensy was detected in the free memory pool.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.Error Message%SYS-2-BADLIST : Regular expression access check with bad list [dec]
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, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADLIST_DESTROY : Removed a non-empty list([hex], name: [chars]), having [int] elements
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 a 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADMAGIC : Corrupt block at [hex] (magic [hex])
Explanation The free memory pool is corrupt.An inconsistensy was detected in the free memory pool.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually.Error Message%SYS-3-BADPARAM : Function [chars]: value [hex] passed in parameter [chars]
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-2-BADPID : Bad pid [dec] for tty [t-line]
Explanation An internal software error 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-2-BADPOOL : Attempt to use buffer with corrupt pool pointer, ptr= [hex], pool= [hex]
Explanation An memory management function attempted an operation that could not be performed due to invalid memory pool descriptors.
Recommended Action If the memory management function was trying to allocate memory, the feature or system component that needed the memory will also report the failure. If the memory management function was trying to free memory, it will have failed and a memory leak will result. The severity of that leak is a function of how frequently the message occurs and the size of the memory block that was not freed. In reporting this 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-2-BADPOOLMAGIC : Attempt to use pool pointer with corrupt header, pool= [hex]
Explanation An internal software error 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADPRINT : Process has no associated tty (in [chars]).
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADPROCESS : Bad process ID ([dec]) when [chars] process table
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADPTRVAL : Bad pointer value ([chars] = [hex]) in function [chars]
Explanation Corrupted pointer value is encountered.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADREFCOUNT : Bad reference count at [hex] (refcount [hex])
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BAD_RESET : Questionable reset of process [dec] on tty[t-line]
Explanation A process was reset without giving it a chance to clean itself 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%SYS-3-BADRESID : Clock hardware returned bad residual [dec].
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet