Cisco IOS Release 15.x SY System Message Guide

CONST_V6-5

Explanation The IPv6 CEF table successfully reloaded to the hardware FIB TCAM. All IPv6 packets will be switched by the hardware.

Recommended Action No action is required.

Explanation The switch failed to insert an IPv6 entry into the hardware FIB TCAM because the total number of software-forwarding entries exceeded the hardware FIB TCAM limit. Some IPv6 packets might be switched by the 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CONTROLLER-2

Explanation A software or hardware 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 A controller stopped responding to commands over the cBus, so it was put into shutdown mode.

Recommended Action Re-enable the controllers by issuing the no shut configuration command on all controllers on the card, or hotswap out the bad card and install the new one. You must still manually no shut the controllers.

CONTROLLER-5

Explanation A configurable controller clock changed its state.

Recommended Action No action is required.

Explanation A configurable controller loopback status.

Recommended Action No action is required.

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 A configurable controller changed its state.

Recommended Action No action is required.

Explanation A configurable controller changed its state.

Recommended Action No action is required.

Explanation A configurable controller entered remote loopback.

Recommended Action No action is required.

Explanation Limited number of HDLC channels can be allocated for this trunk

Recommended Action Please check the number of HDLC resources supported for this trunk card. Please contact your technical support representative

COPTMONMIB-3

Explanation An entry in the OPTICAL MONITORING MIB is already existing for the registering interface

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 attemt to make an entry for the registering 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.

CPU_INTF_FPGA-2

Explanation The CPU interface FPGA initialization was not successful due to a hardware problem. This condition will cause packet drops.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 fatal interrupt has occurred and the device has been reinitialized.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 location of the CPU Interface FPGA device object is invalid. The CPU interface FPGA operation is disabled and the device interrupt is now masked.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CPU_INTF_FPGA-3

Explanation An attempt to unpause traffic from the CPU interface FPGA to the backplane interface ASIC has timed out. This failure may lead to traffic disruption.

Recommended Action If normal traffic processing does not resume, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 a queue for the SPA in the given bay. This failure may lead to traffic disruption.

Recommended Action If normal traffic processing does not resume, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CPU_INTF_FPGA-4

Explanation The CPU interface FPGA received a nonfatal interrupt. This event should not affect the normal operation of the device.

Recommended Action No action is required.

CPU_INTF_FPGA-5

Explanation An attempt to pause traffic from the CPU interface FPGA to the backplane interface ASIC has timed out. This event may lead to traffic disruption.

Recommended Action If normal traffic processing does not resume, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CPU_MONITOR-2

Explanation CPU monitor messages have not been detected for a significant amount of time. A timeout is likely to occur soon, which will reset the system.

Recommended Action No action is required.

Explanation This message provides additional debugging information for the NOT_RUNNING message. The message displays the traceback of the interrupted functions.

Recommended Action No action is required.

CPU_MONITOR-3

Explanation A CPU_MONITOR kernel operation required to identify supect threads has failed.

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

Explanation The CPU monitor messages failed on the peer processor. The system is no longer operational.

Recommended Action No action is required.

Explanation The CPU monitor messages have failed on the peer process and the system is no longer operational.

Recommended Action No action is required.

Explanation The CPU monitor messages failed and the system is no longer operational.

Recommended Action No action is required.

CPU_MONITOR-6

Explanation CPU monitor messages have not been detected for a significant amount of time. [dec] is the number of seconds. A timeout is likely to occur soon, which will reset the system. This error can be caused by a badly seated module or by high traffic in the EOBC channel.

Recommended Action Verify that all modules are seated properly in the chassis. Pull out the module mentioned in the message and inspect the backplane and module for bent pins or hardware damage. If the message persists after reseating all the modules, a hardware problem may exist, such as a defective module or chassis.

CRYPTO-3

Explanation An IKE initialization 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 An 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 The packet has its engine_id set to something otherthan software crypto or hardware crypto.Unable to determine which crypto engine to useThe packet will be default sent to software crypto engine.

Recommended Action No action required

Explanation The crypto engine has exhausted all available connection IDs or is otherwise malfunctioning.

Recommended Action Decrease the number of concurrent connections or inspect the crypto engine.

Explanation Crypto policy checksum failure has been detected in this router whose traffic is protected by the crypto policy. This event may be caused by memory corruption occuring in crypto policy data, or the memory area has been illegally modified. It may also be caused by software defects. As a result of this event, the router has been forced to reload.

Recommended Action Contact your Cisco support representatives.

Explanation The cryptographic token has rejected the administrator PIN offered bythe router

Recommended Action Issue ’crypto pki token admin-pin’ command to enter correct PIN

Explanation The cryptographic token returned an unexpected 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 The cryptographic token has disabled the Admin PIN due to too many login failures

Recommended Action If the user PIN is also locked out, it will be necessary to reinitialize the card.The data on the card will be lost

Explanation The cryptographic token has rejected the new PIN offered bythe router

Recommended Action Be sure you are logged in to the token as admin. Try a longer PIN.

Explanation The cryptographic token has rejected the PIN offered bythe router

Recommended Action Issue ’crypto pki token user-pin’ command to enter correct PIN

Explanation The cryptographic token has disabled the user PIN due to too many login failures

Recommended Action Issue ’crypto pki token admin-pin’ command to enter correct ADMINISTRATOR PIN

Explanation The virtual-interface feature will not work without a virtual-access interface. The EzVPN configuration is unusable. You can choose to remove virtual-interface configuration from ezvpn as a workaround

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

Explanation An automatic test of the newly generated RSA keypair %s failed. That RSA key was automatically deleted.

Recommended Action File a DDTS. As an immediate workaround, attempt to create another pair

Explanation IKE failed to allocate memory for the IKE peer tree

Recommended Action More DRAM may be required in order to run the image.

Explanation An error occurred attempting to write a new keypair out to the cryptographic token

Recommended Action Try logging in to the token. If the error persists, try logging in as admin

Explanation An attempt was made to enqueue a command to the crypto mtree manager process even though IPsec is currently operating in HAPX mode.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 incoming IKE packet spent too much time in the IKE input queues. This can happen when the IKE subsystem is under heavy load, due to a lot of peers trying to setup SAs simultaneously, and IKE is not able to handle all the incoming packets, in a timely manner.

Recommended Action It is important to understand why many peers are simultaneously trying to setup SAs at the same time. If possible, try to avoid or minimize such network conditions.

Explanation Querying public key/private key using subject name failed

Recommended Action Check the subject name in the certificate.

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 and restart crypto isakmp process

CRYPTO-4

Explanation Transform set entry removed from crypto-map as it is no longer validwith hardware crypto engine enabled.

Recommended Action Create and apply valid transform set to cryptomap

Explanation System configuration modified.Some ipsec transforms which were earliervalid with software crypto are no longer valid now after switchinghardware crypto.

Recommended Action Create valid transform sets & update cryptomaps

Explanation The limit for maximum no of ezvpn tunnels that can be setup on the platform, has reached. Active SAs shall not be terminated, but no additional SAs can be established until the number of existing SAs decreases.

Explanation Decapsulated IPSEC packet not maching negotiated identity The peer is sending other traffic through this SA. It may be due to an SA selection error by the peer. Some might consider this a hostile event.

Recommended Action Contact the peer’s administrator to compare policy settings.

Explanation Replay processing failed. This may be a temporary condition due to waiting for new SAs to be established. In the inbound case, this may also be due to an actual replay attack. Some might consider this a hostile event.

Recommended Action If the problem appears to be more than a transient one, contact the peer’s administrator.

Explanation The audit check verifying encryption entitlement within the IOS image could not be performed due to incompete system configuration.

Recommended Action Manually verify that this IOS image is entitled to contain encryption.

Explanation The IKE SA limit that was set is less than the number of active IKE SA. Active SA will not be terminated but no additional IKE SAs can be established unless the limit is increased or the number of active SAs decreases.

Recommended Action Increase the IKE SA limit if necessary to establish connectivity

Explanation Call Admission Control is configured globally or at the IKE level on this device. Consequently an IKE SA request was denied do to the reason described in the error message.

Recommended Action Depending on the reason that the request was denied, either reduce the load on the system so that it can handle new IKE SA requests, or increase the maximum allowed IKE sessions if more are needed.

Explanation The IKE in-negotiation SA limit that was set is less than the current number of in-negotiation IKE SA. As of a result of this, no more new IKE SAs can be created. However, those already in negotiation are allowed to finish.

Recommended Action Increase the IKE SA limit if necessary to establish connectivity

Explanation A quick sanity check is done on all received ISAKMP messages toverify that all component payload types are valid, and that thesum of their individual lengths equals the total length of thereceived message. This message failed the sanity check.Persistantly bad messages could be a denial of service attackor bad decryption.

Recommended Action Contact the remote peer’s administrator.

Explanation IKE maintains state for a communication in the formof security associations. No security association existsfor this packet and it is not an initial offer from the peerto establish one.This situation could denote a denial of service attack.

Recommended Action Contact the remote peer and/or his administrator

Explanation INVALID SPI RECOVERY SAs maximum limit has been reached.

Recommended Action Possibly the local box reloaded.

Explanation The AAA subsystem was unable to send the accounting starton behalf of IPSec. This could be due to the AAA Server being unreachable.

Recommended Action Ensure that the AAA server is reachable and enabledfor accounting.

Explanation The AAA subsystem was unable to send the accounting stopon behalf of IPSec. This could be due to the AAA Server being unreachable.

Recommended Action Ensure that the AAA server is reachable and enabledfor accounting.

Explanation ISAKMP messages are carried in UDP packets.They have their own message length field. The message length fieldof this message was greater than the length of the UDP packet!This situation could denote a denial of service attack.

Recommended Action Contact the remote peer and/or his administrator

Explanation rsa-encr is not supported by Hifn based crypto HW accelerators

Recommended Action Use ISAKMP policy rsa-sig

Explanation Configured encryption method is not supported

Recommended Action Use any of the valid encryption methods for the ISAKMP policy

Explanation Router RSA keypairs and associated IPSEC sessionswill be deactivated when the timeout expires

Recommended Action Re-insert the crypto token before the timeout expires

Explanation Router RSA keypairs and associated IPSEC sessionsare being deactivated because the token containing them was removed

Recommended Action Re-insert the crypto token

Explanation Rec’d packet either udp encapsulated, but is not correct negotiation transform. Or it expected an udp encapsulated packet, but it received a non-udp packet. There may simply be a policy setup error on the peer. Some might consider this a hostile event.

Recommended Action Contact the peer’s administrator to compare policy settings.

Explanation Rec’d packet matched crypto map ACL, but is not IPSEC-encapsulated. IPSEC Peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. Some might consider this a hostile event.

Recommended Action Contact the peer’s administrator to compare policy settings.

Explanation Currently, the router has the CRYPTO IPSEC OPTIONAL ENABLE setting, which allows data which normally would be encrypted to be sent in the clear.

Recommended Action If you did not intend to configure the crypto optional setting, you should reconfigure the box to turn it off

Explanation The crypto engine may be oversubscribed by priorityclass traffic. This happens when the user tries toprovision more priority class bandwidth than what thecrypto engine can handle. If each class is sendingat its max rate, some priority packets may be dropped

Recommended Action Reduce the priority class bandwidth or reducethe number of priority classes in the policy-map

Explanation Configured encryption algorithm not uable with IKE with current hardware configuration

Recommended Action If you need to negotiate this with IKE, specify a valid encryption algorithm for the ipsec transform

Explanation Configured encryption algorithm not supported

Recommended Action Specify a valid encryption algorithm for the ipsec transform

Explanation Configured encryption algorithm will not run on the hardware encryption card. The transform is still usable, but will run with reduced performance.

Recommended Action If you need to use the full performance of the encryption card, specify another encryption algorithm for the ipsec transform

Explanation Cleartext traffic is passing through an interface that is configured for encryption. This traffic is accepted because the router has the CRYPTO IPSEC OPTIONAL ENABLE setting, which allows such traffic.

Recommended Action If you did not intend to configure the crypto optional setting, you should reconfigure the box to turn it off

Explanation Rec’d IPSEC packet specifies SPI that doesn’t exist in SADB. This may be a temporary condition due to slight differences in aging of SAs between the IPSEC peers, or it may be because the local SAs have been cleared. It may also be because of bogus packets sent by the IPSEC peer. Some might consider this a hostile event.

Recommended Action If the local SAs have been cleared, the peer may not know this. In this case, if a new connection is established from the local router, the two peers may reestablish successfully. Otherwise if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer’s administrator.

Explanation Rec’d IPSEC packet is malformed: possibly encapsulation error? The peer is sending malformed packets. It may be due to a decryption error. Some might consider this a hostile event.

Recommended Action Contact the peer’s administrator.

Explanation Rec’d IPSEC packet missing an expected AH or ESP header The peer is sending packets that don’t match the negotiated security policy. Some might consider this a hostile event.

Recommended Action Contact the peer’s administrator.

Explanation MAC verify processing failed. This may be due to the use of the wrong key by either party during the MAC calculations. Some might consider this a hostile event.

Recommended Action Contact the peer’s administrator.

Explanation An encrypting peer attempted to establish an IPSec session with an interface which it was not authorized for. Some might consider this a hostile event.

Recommended Action Check if the peer should be authorized to connect with the IPSec connection. If he should be allowed, it may be a configuration issue. Otherwise, you should contact the peer’s administrator.

Explanation After all is said and done, the decaps packet fails the ACL check The peer is sending other traffic through this SA. It may be due to an SA selection error by the peer. Some might consider this a hostile event.

Recommended Action Contact the peer’s administrator to compare policy settings.

Explanation The received IPPCP packet failed to decompress.This may be due to a decompression buffer error.

Explanation The receive IPPCP packet had an improper CPI.This may be due to use of an old IPPCP security association.

CRYPTO-5

CRYPTO-5

Explanation The certificate given by remote peer has either been revoked orexpired (certificate invalid) or the signature check on thecertificate failed (bad signature)

Recommended Action Contact the CA of the remote peer. Possibly bad CA certificate.

Explanation This is a notification message for IPSEC tunnel status

Recommended Action No action is required

Explanation This is a notification message for crypto ike sa’schanging their HA status

Recommended Action No action is required

Explanation This is a notification message for crypto ipsec sa’schanging their HA status

Recommended Action No action is required

Explanation Start registration for one group

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 is configured not to accept or respond to ISAKMP aggressive mode with any peer

Recommended Action If you did not intend to disable aggressive-mode then remove the command

CRYPTO-6

Explanation Ezvpn connection is being closed. The IPsec and IKE security associations will also be brought down along with it.

Explanation Ezvpn connection is up for the client mentioned. Both IPsec and IKE security Associations are up now.

Explanation VPN tunnel status.

Explanation While showing a list, the list was changed or elements changed. This can happen if SA’s are re-negotiated at the time the show-command was paused, or if someone reconfigured or cleared SA’s, amongst other things. This is not an error, but a side-effect of a dynamic system.

Recommended Action In general, this is merely a warning, that the output from the show command is most likely incomplete. Re-running the show-command should provide the newest information. On a busy system, with ever-changing SA’s, this may appear frequently.

Explanation A pseudo-random number generator produced the same number twice in succession.

Recommended Action Under normal circumstances a pseudo-random number generator will occasionally produce the same number twice in succession and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative.

Explanation The IKE process was unable to authenticate its securityAssociation with its remote peer.

Recommended Action Contact the remote peer’s administrator.

Explanation CET has been End-of-lifed in IOS release 12.2(1)

Explanation The IKE security association with the remote peer was notauthenticated yet the peer attempted to begin a Quick Modeexchange. This exchange must only be done with an authenticatedsecurity association

Recommended Action Contact remote peer

Explanation X.509v3 certificates can contain usage restrictions.These can restrict use of the certificate only for signaturesor only for key exchange (encryption). The peer attempted touse his certificate in a manner which violated these restrictions.

Recommended Action Contact the remote peer, and the remote peer’s CA

Explanation The cryptographic token has accepted the administrator PIN offered bythe router

Recommended Action Informational message only. No action required.

Explanation The cryptographic token has accepted the new administrator PIN offered bythe router

Recommended Action Informational message only. No action required.

Explanation The cryptographic token has accepted the PIN offered bythe router

Recommended Action Informational message only. No action required.

Explanation The router has logged out from the cryptographic token

Recommended Action Informational message only. No action required.

Explanation The cryptographic token has accepted the new PIN offered bythe router

Recommended Action Informational message only. No action required.

Explanation A cryptographic token containing private keyfiles has been re-inserted in time.Router RSA keypairs and associated IPSEC sessionswill be NOT be deactivated

Recommended Action Informational message only. No action required.

Explanation A cryptographic token has been detected

Recommended Action Informational message only. No action required.

Explanation A cryptographic token has been detected

Recommended Action Informational message only. No action required.

Explanation The DOI field in notify messages give the receiver a contextin which to understand the message being notified. This DOIvalue is not understood and the message therefore cannot beunderstood.

Recommended Action If this situation persists contact the remote peer.

Explanation The DOI field of an SA offer defines how to parse the fieldsSAs with an unknown DOI cannot be parsed

Recommended Action If this situation persists contact the remote peer’s administrator

Explanation Auto-Enroll has generated a new router key pair

Recommended Action No action required. Informational message

Explanation ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the distinguished name of the peer’s certificate.

Recommended Action Contact the remote peer if this situation persists

Explanation ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the ip address of the peer’s certificate.

Recommended Action Contact the remote peer if this situation persists

Explanation ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the fqdn of the peer’s certificate.

Recommended Action Contact the remote peer if this situation persists

Explanation ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the user fqdn of the peer’s certificate.

Recommended Action Contact the remote peer if this situation persists

Explanation Encryption or decryption on a particular IKE thread failed.

Recommended Action Contact remote peer

Explanation The IKE SA was deleted by user command. However, keepalives this connection are enabled, and IPSec SA’s covered by this IKE SA still exist. Since this IKE SA is now deleted, these IPSec SA’s have no IKE SA covering them. The recommended action is to manually delete this IPSec SA’s.

Recommended Action Use parser command clear crypto sa to clear IPSec SA’s.

Explanation A portion of the IKE exchange takes place in the clearand a portion is encrypted. This message should have beenencrypted but was not.

Recommended Action Contact remote peer

Explanation IKE preforms actions on messages based on defined exchanges.The message received had an unknown exchange.

Recommended Action Contact the remote peer’s administrator

Explanation The ISAKMP process has been switched on or off either by CLI or because no crypto map or EzVPN configuration is applied to any interface.

Recommended Action No action required.

Explanation A new keypair has been written out to the cryptographic token

Recommended Action Informational message only. No action required.

Explanation Negotiation with the remote peer failed.

Recommended Action If this situation persists contact the remote peer

Explanation The X9.17 random number specification requires us to check for the same value appearing as the seed and the seed key. This message indicates that the condition was discovered.

Recommended Action The X9.17 random number will occasionally produce this condition, and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative.

Explanation Rec’d TED reply that does not match a TED probe we currently have outstanding. This may be a one time occurance due to the TED reply being delayed. It may also be because of ill-formed packets sent by the peer. Some might consider this a hostile event.

Recommended Action If the problem occurs more than once, contact the peer’s administrator.

Explanation IKE peers negotiate policy by the initiator offering a listof possible, alternate, protection suites. The responderresponded with one that the initiator did not offer

Recommended Action Contact the remote peer

Explanation Keys are stored in keyrings on the router. An attempt toadd another key to the ring failed.

Recommended Action Check local key rings. This is probably due to other failures.

CRYPTO_HA-3

Explanation An attempt to insert an SA entry transferred from the active device has failed. The SA database is no longer synchronized with that on the active device.

Recommended Action Initiate a manual resynchronization of the ISAKMP SA table.

Explanation An attempt to delete an SA entry that was removed on the active device has failed. The SA database is no longer synchronized with that on the active device.

Recommended Action Initiate a manual resynchronization of the ISAKMP SA table.

Explanation An attempt to insert keys for a new SA entry on the standby device has failed. The standby device will not receive this entry.

Recommended Action Initiate a manual resynchronization of the ISAKMP SA table from the standby device.

Explanation An attempt to query an SA entry for key information to send to the standby device has failed. The standby device will not receive this entry.

Recommended Action Initiate a manual resynchronization of the ISAKMP SA table from the standby device.

Explanation An attempt to insert an SA entry transferred from the active device has failed. The SA database is no longer synchronized with the database on the active device.

Recommended Action Initiate a manual resynchronization of the IPsec SA table.

Explanation An attempt to delete an SA entry that was removed on the active device has failed. The SA database is no longer synchronized with the database on the active device.

Recommended Action Initiate a manual resynchronization of the IPsec SA table.

CRYPTO_HA-6

Explanation This is a normal notification message when HA is unconfigured for this failover group, or a tracked interface is shut down. However, it may also be a result of a failure.

Recommended Action If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the redundancy protocol (HSRP, for example) that may have lead to the Down state notification to the high availability framework.

Explanation This is a normal notification message when an active device is first elected. Alternatively, it is triggered when a failover occurs within the high availability group. In that case, the formerly active device within the ISAKMP failover group has gone down and this device is taking over as the new active device for the group.

Recommended Action If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the previous active device to troubleshoot the reason for failure and take appropriate action.

Explanation HA IKE SSP message processing seems to be looping on this message. The processing of this message will be dropped to prevent an infinite loop.

Recommended Action Turning on detailed IKE HA debugs on both HA pairs can help determine what message may be causing this problem.

Explanation IKE HA received a state notification or an SSP message for a VIP that does not have HA enabled.

Recommended Action Verify that IKE stateful failover is configured for the interface with this VIP.

Explanation This is a normal notification message after the standby has received either REPLY_ENTRY or DELETE_ENTRY messages for all requests during synchroniztion.

Recommended Action No action is required.

Explanation This is a normal notification message after a standby device comes up.

Recommended Action No action is required.

Explanation An attempt to update an SA entry as specified by the active device has failed. The SA entry will be missing the latest packet level update until another update entry is sent by the active device.

Recommended Action Normally, a subsequent update entry message will self-correct the problem. Manual resynchronization of the ISAKMP SA table by the standby device may be necessary if this message appears repeatedly.

Explanation This is a normal notification message when HA is unconfigured for this failover group, or a tracked interface is shut down. However, it may also be a result of a failure.

Recommended Action If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the redundancy protocol (HSRP, for example) that may have lead to the Down state notification to the high availability framework.

Explanation This is a normal message when a device first becomes active, or when failover occurs within the high availability group. In the failover case, the former active device within the IPsec failover group has gone down and this device is taking over as the new active device for the group.

Recommended Action If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the previous active device to troubleshoot the reason for failure and take appropriate action.

Explanation The device is normally out of resources for short periods of time, and retries will automatically occur. In this case, however, the retries have not succeeded and have stopped. Action is required from the administrator.

Recommended Action Verify that both devices in the HA pair are identical and that the hardware is working properly.

Explanation IPsec HA received a state notification or an SSP message for a VIP that does not have HA enabled.

Recommended Action Verify that IPsec stateful failover is configured for the interface with this VIP.

Explanation This is a normal notification message after the standby has received either a REPLY_ENTRY or a DELETE_ENTRY message for all requests during synchroniztion.

Recommended Action No action is required.

Explanation This is a normal notification message when a standby device comes up.

Recommended Action No action is required.

Explanation An attempt to update an IPsec SA entry as specified by the active device failed. The SA entry will be missing the latest packet level update, until another update entry is sent by the active device.

Recommended Action Normally, a subsequent update entry message will self-correct the problem. Manual resynchronization of the IPsec SA table by the standby device may be necessary, if this message appears repeatedly.

CRYPTO_HA_IKE-3

Explanation The HA active device attempted to checkpoint the state of an IKE SA to the standby device, but the standby device was unable to create the standby IKE SA.

Recommended Action Search for other error messages at WARNING log level or turn on debugging messages to find the specific cause of the failure.

CRYPTO_HA_IKE-4

Explanation Crypto hardware is enabled, but the hardware does not support HA operations such as insertion and extraction of keys.

Recommended Action Replace the crypto module with one that supports HA operations, or disable the hardware and use the software crypto engine.

CRYPTO_HA_IPSEC-3

Explanation The HA active device attempted to checkpoint the state of an IKE SA to the standby device, but the standby device was unable to create the standby IKE SA.

Recommended Action Search for other error messages at log level WARNING or turn on debugging messages to find the specific cause of the failure.

Explanation The IPsec HA process failed to start. Updates will not be sent from the active device to the standby device.

Recommended Action The module may need to be rebooted if this is a part of an IPsec HA setup.

CRYPTO_HA_IPSEC-4

Explanation Crypto Hardware is enabled, but the hardware does not support HA operations such as insertion and extraction of keys.

Recommended Action Replace the crypto module with one that supports HA operations, or disable the hardware and use the software crypto engine.

CRYPTO_RSA_ISSU-3

Explanation The crypto RSA ISSU client was unable to obtain a buffer for building a negotiation message. As a result, the client 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, and show checkpoint client commands and your pertinent troubleshooting logs.

Explanation The crypto RSA 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 crypto RSA ISSU client does not have a valid registered session. This condition will prevent the standby unit from coming 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 crypto RSA ISSU client received an incompatible message from the peer unit. Because 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. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with 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 crypto RSA ISSU client was unable to calculate the MTU for the message specified. The 802.1X ISSU 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 crypto RSA ISSU client failed to send a session negotiation message to the peer. This condition will prevent the standby unit from coming 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 crypto RSA ISSU client encountered an unexpected ’client negotiation done’. 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 crypto RSA ISSU client failed to register session information. This condition will prevent the standby unit from coming 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 crypto RSA ISSU client failed 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 crypto RSA 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 crypto RSA state will not match 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.

CSG-3

Explanation An error occurred in a CSG 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 This informational message appears whenever a CSG configuration is reloaded as a result of power cycling a CSG card.

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

CSG-4

Explanation An undesired event has occurred in a CSG 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.

CSG-6

Explanation The CSG lawful intercept (LI) configuration was reloaded because of the power cycling of a CSG module.

Recommended Action No action is required.

Explanation This informational message appears whenever a CSG configuration is reloaded as a result of power cycling a CSG card.

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

CSM_SLB-4

Explanation There is a mismatch between the configuration and the specified environment variable.

Recommended Action Check the documentation for any caveats regarding the use of the specified environment variable.

CTS-0

Explanation A Cisco TrustSec (CTS) process failed due to insufficient system memory.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 A Cisco TrustSec (CTS) process failed due to insufficient system memory.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CTS-1

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.

CTS-2

Explanation An internal software error occurred.

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.

CTS-3

Explanation An error occurred while the Cisco TrustSec (CTS) authorization attempted to build its database.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization was unable to create an internal data 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 you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization data exceeded the maximum allowed limit.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization was unable to get or create a data 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 you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization encountered an unexpected NULL pointer or 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 Cisco TrustSec (CTS) authorization unexpectedly encountered uninitialized 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 error occurred while the standby unit was receiving synchronization data from 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 and show tech-support commands and your pertinent troubleshooting logs.

Explanation Cisco TrustSec (CTS) authorization encountered an internal 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 you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization attempted to build its database.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization encountered an invalid data 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 you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization encountered an unsupported data type or feature, possibly due to incompatibility.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to install a fallback authorization policy.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to acquire or install an ingress policy from the access control server.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to acquire or install a policy due to an 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 you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to acquire a peer policy from the access control server.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to acquire a role-based access control list (RBACL) policy from the access control server.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to acquire a wildcard policy from the access control server.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization was performing a synchronization of 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 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 Cisco TrustSec (CTS) was unable to configure 802.1X for a CTS link.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) authorization was unable to FORCE AUTHORIZED an 802.1X port on a CTS link.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to initialize 802.1X for a CTS link.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to start or stop an 802.1X Port Access Entity (PAE) for a CTS link.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) encountered an internal 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 you have gathered. Attach the following information to 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 Because global 802.1X is not enabled, Cisco TrustSec (CTS) will not run.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to decode the data descriptor in order to obtain the software interface descriptor block (SWIDB).

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) was unable to encode the software interface descriptor block (SWIDB) into the data descriptor.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) encountered an unexpected NULL pointer or 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 Cisco TrustSec (CTS) IFC was unable to access the link object.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) IFC was performing a synchronization of 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 and show tech-support commands and your pertinent troubleshooting logs.

Explanation An error occurred while Cisco TrustSec (CTS) IFC was performing a synchronization of 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 and show tech-support commands and your pertinent troubleshooting logs.

Explanation Cisco TrustSec (CTS) encountered an unexpected invalid HA/ISSU message ID.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 port could not be authorized on a Cisco TrustSec (CTS) link.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 physical port cannot join the channel group (port channel) because its Cisco TrustSec (CTS) configuration does not match the channel group’s CTS 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 A physical port cannot join the port channel because its Cisco TrustSec (CTS) mode does not match the port channel’s CTS mode.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 physical port cannot join the port channel because its Cisco TrustSec (CTS) reauthentication timer value does not match the port channel’s timer value.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 physical port cannot join the channel group (port channel) because its Cisco TrustSec (CTS) configuration does not match the channel group’s CTS 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 An error occcured while CTS attempts to to send a message event to the core 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 SXP binding update 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 you have gathered. Attach the following information to 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 SXP Connection with the specified instance number changed state.

Recommended Action No action is required.

Explanation The Security Exchange Protocol (SXP) process could not start after a restart.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 parsing SXP 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.

CTS-4

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 CTS SXP system encountered internal 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.

CTS-5

Explanation Normal but significant conditions

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Binding added to the SXP database.

Recommended Action No action is required.

Explanation Binding changed in the SXP database.

Recommended Action No action is required.

Explanation Binding deleted in the SXP database.

Recommended Action No action is required.

Explanation SXP forwarded binding to the peer.

Recommended Action No action is required.

Explanation SXP received a binding forwarding request.

Recommended Action No action is required.

Explanation SXP updated binding manager with the binding change.

Recommended Action No action is required.

Explanation The SXP system password has been changed.

Recommended Action No action is required.

Explanation SXP default source IP is changed on this device.

Recommended Action No action is required.

Explanation SXP feature is functioning only when the feature is enabled.

Recommended Action No action is required.

Explanation A VRF is removed, the connections configured in this VRF should be removed.

Recommended Action No action is required.

Explanation Received empty tlv list during capability negotiation.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CTS-6

Explanation Cisco TrustSec (CTS) authorization caused FORCE AUTHORIZED on an 802.1X port on a CTS link.

Recommended Action No action is required.

Explanation The specified interface has been configured to be an 802.1X Port Access Entity (PAE).

Recommended Action No action is required.

Explanation The Cisco TrustSec (CTS) link was brought up using cache data.

Recommended Action No action is required.

Explanation Informational messages

Recommended Action No action is required.

Explanation A port was authorized on a Cisco TrustSec (CTS) link.

Recommended Action No action is required.

Explanation A port has become unauthorized on a Cisco TrustSec (CTS) link.

Recommended Action No action is required.

Explanation A SXP configuration error occurred. The connection can not be setup correctly.

Recommended Action Ensure that the connection configure on both ends have the matched mode, IP addresses.

Explanation SXP Connection with the specified instance number changed state.

Recommended Action No action is required.

Explanation An error occurred while using this source IP address to set up SXP connection.

Recommended Action Re-configure SXP connection to have a valid source IP address.

Explanation The specified SXP timer started.

Recommended Action No action is required.

Explanation The specified SXP timer stopped.

Recommended Action No action is required.

CTS-7

Explanation An internal software error occurred.

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.

CTS_HA-3

Explanation The Cisco TrustSec (CTS) high availability (HA) process failed to add a checkpoint client. No CTS data will be synchronized with 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 and show tech-support commands and your pertinent troubleshooting logs.

Explanation The Cisco TrustSec (CTS) high availability (HA) client on the standby device failed to process a checkpoint message from the active device. The CTS 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 and show tech-support commands and your pertinent troubleshooting logs.

Explanation The Cisco TrustSec (CTS) high availability (HA) client on the active device failed to send a checkpoint message to the standby device. The CTS 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 and show tech-support commands and your pertinent troubleshooting logs.

CTS_HA_ISSU-3

Explanation Received empty tlv list during capability negotiation.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 CTS HA failed during capability negotiation.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Cisco TrustSec (CTS) high availability (HA) 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. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with 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 Cisco TrustSec (CTS) high availability (HA) 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 Message 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 and show tech-support commands and your pertinent troubleshooting logs.

Explanation The Cisco TrustSec (CTS) high availability (HA) 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. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with 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 Cisco TrustSec (CTS) high availability (HA) 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. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with 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 Cisco TrustSec (CTS) high availability (HA) ISSU client failed 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.

CTS_HA_ISSU-6

Explanation The Cisco TrustSec (CTS) high availability (HA) ISSU client message version is not compatible on the active and standby devices. As a result, no CTS data will be synchronized 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 capability entries, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

CWAN_ALARM-6

Explanation This message provides alarm assertion or deassertion information.

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

Explanation This message is generated whenever an alarm is present in the system (and the alarm status has been reported to the RP) or an alarm has been removed from the system (and the alarm status has been reported to the RP.

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

Explanation The Cisco TrustSec (CTS) Security Exchange Protocol (SXP) system password has been changed.

Recommended Action No action is required.

Explanation The Cisco TrustSec (CTS) Security Exchange Protocol (SXP) system component has changed its operational state.

Recommended Action No action is required.

CWAN_ATM-3

Explanation Memory is running low.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Explanation The specified port does not exist.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 port VCD does not exist.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 VC does not exist on the port.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Either the port or the VCD 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.

CWAN_ATM-5

Explanation An unknown VCD has been received in the egress path of the module. This condition is most likely a transient condition, and it is usually caused by VCs that are being disassembled and reassembled while traffic is being passed.

Recommended Action No action is required.

CWAN_ATOM-HA-2

Explanation Platform ATOM HA ISSU client 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.

CWAN_ATOM-HA-3

Explanation Platform ATOM HA CF client 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 Platform ATOM HA RF client 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.

CWAN_CHOC-4

Explanation Incorrect parameters were detected internally.

Recommended Action This is only a debug warning message. The unexpected value is discarded.

CWAN_CHOC_DSX-3

Explanation A software error occurred. This message displays when IDB subblocks cannot be removed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_CT3-3

Explanation Incorrect parameters were detected internally.

Recommended Action This is only a debug warning message. The unexpected value is discarded.

CWAN_FWD_TABLES-3

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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 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.

CWAN_HA-2

Explanation The high availability component for WAN modules failed to synchronize new state information for the specified slot.

Recommended Action Reload the redundant supervisor engine to force a fresh bulk synchronization. If this error 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. Examine both the active supervisor engine and the redundant supervisor engine for messages.

Explanation The high availability component for WAN modules failed to record new state information for the specified slot. The system is falling back to RPR mode for high availability.

Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 high availability component for WAN modules failed to synchronize new state information for the specified slot. The redundant system is no longer synchronized with the active system. The redundant supervisor engine was reloaded shortly after this error was 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 high availability component for WAN modules failed to record some new state information for the specified slot. The system is falling back to RPR mode for high availability.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_HA-3

Explanation The high availability component for WAN modules failed to properly initialize state information for the specified slot. The system is falling back to RPR mode for high availability.

Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 high availability component for WAN modules is unable to properly synchronize state information for the current configuration due to a conflict in command identifiers.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 high availability component for WAN modules failed to properly initialize state information for the specified slot. The system is falling back to RPR mode for high availability.

Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Examine both the active supervisor engine and the redundant supervisor engine for messages.

Explanation The high availability component for WAN modules is unable to properly synchronize state information for the current configuration. The system is falling back to RPR mode for high availability.

Recommended Action Examine both the active supervisor engine and the redundant supervisor engine for messages. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_HA-4

Explanation The high availability component for WAN modules failed to synchronize some new state information for the specified slot.

Recommended Action Reload the standby supervisor engine to force a fresh bulk synchronization. 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 high availability component for WAN modules failed to record some new state information for the specified slot.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 high availability (HA) component for WAN modules failed to synchronize new state information for the specified slot.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show platform redundancy if-config default-retvals commands and your pertinent troubleshooting logs.

Explanation The high availability component for WAN modules failed to synchronize some new state information for the specified slot.

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 The high availability component for WAN modules failed to record some new state information for the specified slot.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 Some local target logic (LTL) data did not synchronize correctly from the active to the standby RP.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 synchronization of RP bulk data and SRP bulk data failed from the active supervisor engine to the redundant supervisor engine.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 dynamic synchronization of SRP packets failed from the active supervisor engine to the redundant supervisor engine.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 error occurred while synchronizing the SRP states from the active supervisor engine RP to the redundant supervisor engine RP.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_HAL-3

Explanation There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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 There is a problem with internal software coding. This message should not appear under 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.

CWAN_HAL-4

Explanation The configuration of the WAN module is not supported. A common cause is configuring TE on a GRE tunnel.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_IFMGR-4

Explanation Driver failed to create an interface with the interface manager.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Explanation Driver failed to destroy the interface with the interface manager.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Explanation Driver failed to register with the interface manager.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

CWANLC-3

Explanation This FPD package does not contain images that are compatible with the current line card revision.

Recommended Action Perform the FPD upgrade operation with a newer version of an FPD image package that is compatible with the Cisco IOS software that is operating on the switch. Consult with the FPD image package section of the Cisco IOS software release note to confirm that your line card revision is supported for a particular release.

Explanation The RP determined through an SCP find operation that the version of the EARL switching engine on the module has changed. This message occurs during a switchover operation. The version of the EARL switching engine is specified in the message text.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 OSM encountered a fatal 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 you have gathered. Attach the following information to 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 FPD package does not contain images that are compatible with the current board revision.

Recommended Action Perform the FPD upgrade operation with a newer version of the FPD image package that is compatible with the running Cisco IOS software. Consult with the FPD image package section of the Cisco IOS software release note to confirm if your board revision is supported for a particular release.

Explanation The line card failed to create a port for communication with the route processor.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 line card software initialization was not completed correctly.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 OSM could not start VPN due to insufficient memory.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. 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.

CWANLC-5

Explanation The SCP ping mechanism is used by the RP and SP processors to monitor whether the line card that is executing Cisco IOS is in a healthy state. This SCP ping response has not been sent by the line card for a long time; the line card has exported its context information to the RP and may be power cycled. The exported context is available in the output of the show diag command.

Recommended Action Save the show diag command output and contact your Cisco technical support representative if the line card is reset.

CWANLC_ATM-3

Explanation Out of virtual paths (VPs) on the segmentation and reassembly (SAR) engine.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 remove a virtual circuit on the module 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.

CWAN_QINQ-3

Explanation The port channel QinQ Ether VC subinterface being configured contains an invalid egress port assignment. The egress traffic of the OSM port will be stopped for this EVC.

Recommended Action Copy the message exactly as it appears on the console or in the system log. At the line card, enter the show cwan qinq 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 data integrity error related to QinQ was detected while a trunk was being configured for the bridge VLAN that is indicated in the message text. The error will be ignored, and the QinQ update will proceed normally.

Recommended Action Enter the show cwan qinq command on the module. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_RP-0

Explanation An error has occurred on a module. The slot and CPU number are indicated after the CWAN_RP-0-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_RP-1

Explanation An error has occurred on a module. The slot and CPU number are indicated after the CWAN_RP-1-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 issued an override MAC address that does not match the MAC address of the MSFC. This condition can occur if the configuration was moved to new hardware or the MAC address command was used on another interface. While the system automatically corrects this condition, the configuration needs to be adjusted.

Recommended Action Modify the override MAC address command in the configuration.

CWAN_RP-2

Explanation An error has occurred on a module. The slot and CPU number are indicated after the CWAN_RP-2-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_RP-3

Explanation The RP could not send the specified configuration message to the line card.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 on the RP sent a configuration command to the slot specified in the message and a different process waited for the result. This condition could cause incorrect line card configuration states.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 on a module. The slot and CPU number are indicated after the CWAN_RP-3-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 while the system was detecting the module type in the specified slot. The module operation will be affected.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 send a process message failed for the specified 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 error occurred during the upgrade process.

Recommended Action If the module reloads successfully, examine the file and try the upgrade process. 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 user attempted to configure more VPLS, EoMPLS, and bridging VCs than the number that is supported by the platform.

Recommended Action Review the configuration guidelines for the features that are being configured, and reduce the number of VPLS, EoMPLS, and bridging VCs to the number that is supported by the platform.

CWAN_RP-4

Explanation An unexpected configuration difference exists between the active and standby supervisor engines.

Recommended Action The standby supervisor engine is being reloaded. No action is required.

Explanation The FlexWAN in the specified slot does not contain any port adapters.

Recommended Action The FlexWAN should be removed. This is an unsupported configuration.

Explanation The RP sent a configuration command to the slot specified in the message and received no confirmation for the command.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 7600 series router incremental running configuration synchronization has failed.

Recommended Action Power cycle the redundant supervisor engine.

Explanation The specified 7600 series router slot and CPU are beyond the chassis limit.

Recommended Action Power cycle the redundant supervisor engine.

Explanation An error has occurred on a module. The slot and CPU number are indicated after the CWAN_RP-4-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Some information is missing regarding the configuration of the module in the specified slot. Any startup configuration for the interfaces will not be applied. If the module in the specified slot is a FlexWAN, details about the port adapters in the FlexWAN are missing from the configuration information. This information is missing from the SLOTCACHE ROMMON variable.

Recommended Action If the module in the slot specified in the error message has not previously been inserted, it has no previous configuration; therefore, no action is required. If the configuration for the specified slot in the startup configuration is suitable for the module in that slot, after the module has loaded, manually apply the configuration by using one of the following two methods. The second method requires a system reload.

– Enter the copy nvram:startup-config system:running-config command to reapply your saved configuration and then enter the no shutdown command on all interfaces whose configuration was rejected. Enter the copy system:running-config nvram:startup-config command to save your configuration and the WAN module slot configuration.

– Enter the copy command to copy your startup configuration to a temporary location (for example, copy nvram:startup-config bootflash:tmp-config), and then enter the copy system:running-config nvram:startup-config command to update the WAN module slot configuration. Enter the copy command to restore the temporary copy of the startup configuration (for example, copy bootflash:tmp-config nvram:startup-config), and then enter the reload command to reload the system.

After using the second method, you may want to use the delete command to remove the temporary copy of the startup configuration. To prevent this condition from recurring, ensure that the SLOTCACHE variable is updated whenever modules that require it (FlexWANs, but not OSMs) are moved between slots in the chassis. The SLOTCACHE variable is updated when the running configuration is written to the startup configuration using the copy system:running-config nvram:startup-config command (or the deprecated write memory equivalent). The two methods of restoring the configuration for the module ensure that the SLOTCACHE variable is updated.

CWAN_RP-5

Explanation An error has occurred on a module. The slot and CPU number are indicated after the CWAN_RP-5-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_RP-6

Explanation The system is booting the specified upgrade image for the VPN Services Module.

Recommended Action No action is required.

Explanation The file specified in the message was found and will be loaded instead of the bundled image by the VPN Services Module.

Recommended Action No action is required.

Explanation An error has occurred on a module. The slot and CPU number are indicated after the CWAN_RP-6-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 If the system is running Catalyst operating system software on the supervisor engine and Cisco IOS software on the MSFC, the WAN line cards that power up before the RP powers up will be reset automatically.

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

Explanation The line card in the specified slot will be powered down to prevent it from running an image that is not supported by the RP. If the line card image is compatible with the image running on the RP, there might be another problem with the software.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 resources required for configuration are no longer available. They may have been acquired by another application.

Recommended Action If the requested resources have not been allocated to another application, contact your Cisco technical support representative for further assistance.

Explanation The specified image will be used instead of the bundled image.

Recommended Action No action is required.

Explanation The ROMMON upgrade has completed successfully. The module must be reloaded for the changes to take effect.

Recommended Action No action is required.

CWAN_RP-7

Explanation An error has occurred on a module. The slot and CPU number are indicated after the CWAN_RP-7-LCLOG_MSG text. The error message that appears after the slot number is the original message from the module.

Recommended Action Follow any instructions provided in the error message text. If no instructions are provided, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWAN_SLOT-1

Explanation The checkpoint facility client could not be 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 you have gathered. Attach the following information to 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 checkpoint facility could not obtain buffer memory.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

CWAN_SP-3

Explanation A memory allocation failure has occurred during initialization of WAN SP module.

Recommended Action Upgrade to a higher memory size on the switch processor (SP).

CWAN_SP-4

Explanation An unknown WAN pseudowire is being used.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWPA-2

Explanation The module software cannot read the module hardware version. This condition indicates a hardware 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 you have gathered. Attach the following information to 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 OIR operation occurred on the port adapters of the specified module, but OIR is not supported on the port adapter. This error has caused the module to fail and reload.

Recommended Action Do not attempt OIR on the port adapters of the specified module.

Explanation The module encountered an error involving power delivery to the module. Probable causes for this error are an environmental condition, an overtemperature condition, or inconsistent voltage to the module.

Recommended Action Verify that the input voltage and the temperature of the module are within acceptable ranges.

Explanation The module specified in the error message has encountered an unexpected interrupt.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWPA-3

Explanation The module failed to execute a diagnostics command.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 module failed to create a process that is necessary for proper functioning of the module.

Recommended Action If a statistics export process was not created, check the I/O rate and the bytes that are getting incremented in the show interface command output for the nonchannelized interfaces on the FlexWAN and Enhanced FlexWAN modules. You can also get the statistics from the show interface acc command output or the show interface stats command output. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWPA-4

Explanation A packet was sent from the port adapter to either the route processor or the line card. That packet did not have enough available space to append the header. A new particle has been linked to the packet to store the header.

Recommended Action No action is required.

CWRPSPA-3

Explanation Failed to create a hardware interface descriptor block (HWIDB).

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 number is out of range.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 of IPSEC-SPA-2G port adapters in a chassis is limited. This message displays when the number of IPSEC-SPA-2G port adapters in the chassis has exceeded the limit.

Recommended Action Use only the number of supported IPSEC-SPA-2G port adapters.

Explanation Failed to get information about the host line card.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWRPSPA-4

Explanation A timeout occurred while the RP was waiting for a response from the line card. This condition may occur when the line card CPU is too busy to respond to the configuration command.

Recommended Action Retry the configuration command.

Explanation An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.

Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message 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.

CWRPSPA-6

Explanation When inserting a SPA on the specified module, the module resets.

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

CWSLC-3

Explanation The module failed to execute a diagnostics command.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 module skipped diagnostics for the specified port.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 DIP switches need to be set properly.

Recommended Action Refer to the 7600 SIP and SPA Hardware Installation Guide for information about how DIP switches must be set.

Explanation An Enhanced FlexWAN module failed to allocate a buffer for communication with the route processor (MSFC).

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Enhanced FlexWAN module failed to send a message to the route processor (MSFC).

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 line card failed to update the new encapsulation that was requested. The interface data structures could not be temporarily locked to perform the encapsulation change

Recommended Action If the interface does not come up with the new encapsulation, remove and reconfigure the encapsulation on the interface. If the error persists after a few attempts at reconfiguration, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWTLC-0

Explanation The OSM encountered a fatal exception.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWTLC-2

Explanation The OSM encountered a fatal line management interrupt. This error is not recoverable and will cause the system to 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.

Explanation The OSM encountered a PCI timeout.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 OSM encountered an FPGA error that caused a sequence 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 you have gathered. Attach the following information to 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 OSM encountered a PCI 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 you have gathered. Attach the following information to 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 entered a command that caused the module to fail.

Recommended Action No action is required.

CWTLC-3

Explanation The OSM encountered an error with the FPGA that has caused the FIFO queue to exceed the maximum limit. This condition will cause the system to 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.

Explanation The CWTLC switching bus interface ASIC received an error.

Recommended Action If traffic recovers, no action is required. 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.

Explanation The CWTLC switching bus interface ASIC received a hardware error and will be reset.

Recommended Action If traffic recovers, no action is required. 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.

Explanation The CWTLC DMA engine ASIC received an error.

Recommended Action If traffic recovers, no action is required. 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.

Explanation The CWTLC DMA engine ASIC received a fatal 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 provides additional error details for a previous message, which may be of use to your technical support representative.

Recommended Action Follow the instructions for any system messages preceding this one and be sure to include the text from this error.

Explanation The OSM encountered an error exception.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 OSM fabric interface ASIC received a fatal error.

Recommended Action If traffic recovers, no action is required. 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.

Explanation An ASIC device on the OSM has detected that the designated PXF client is not 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 This is an unexpected update from the route processor and should be ignored.

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

Explanation Some feature code mistakenly invoked the module Frame Relay handler, which is designed to run at process level. This condition may lead to data corruption and a module 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 The port selection information stored in the database is not valid.

Recommended Action Shut down the interface VLAN and restart the interface VLAN.

Explanation The OSM multicast replication engine ASIC received a fatal error.

Recommended Action If traffic recovers, no action is required. 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.

Explanation The OSM Medusa ASIC received the specified fatal error.

Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 ASIC device on the OSM has detected that the specified PXF client is not 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 you have gathered. Attach the following information to 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 OSM could not obtain statistics due to depleted memory.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. 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 OSM has used up all resources for statistics collection. No additional resources are available for further statistics collection.

Recommended Action Reduce the number of features configured on the specified PXF. If conditions warrant, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 OSM has an earlier release of the I/O FPGA software.

Recommended Action Contact your Cisco technical support representative to upgrade the I/O FPGA software.

Explanation The OSM encountered an FPGA error that caused a sequence error. The module will attempt to recover from the error.

Recommended Action If the system recovers, no action is required. If the system does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 control command function 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 The OSM experienced an unexpected interrupt.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 OSM Titan ASIC received a fatal error.

Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 WAN module received inconsistent statistics from the PXF. The PXF reported that a packet was dropped, but the PXF did not report the correct packet count.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 encountered an error while it was attempting to allocate memory from a WAN OSM component.

Recommended Action Reduce the number of routes associated with a VRF identifier or upgrade the WAN OSM to a higher version.

Explanation The MPLS label range configured for this system is not supported. The maximum label range limit is specified in the message.

Recommended Action Change the maximum MPLS label range by entering the mpls label range command.

Explanation The OSM could not schedule the wheel entry. The reason for the error is specified in the error message text.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 VTMS queue was in the process of being modified for a change in QoS configuration, but packets were still going through the queue. When the queue is being modified, there is usually no traffic in the 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWTLC-4

Explanation The ASICs on the OSM are resetting. System traffic should recover and continue normally after the module resets.

Recommended Action No action is required.

Explanation The CWTLC switching bus interface ASIC failed to be configured correctly.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 CWTLC Medusa ASIC received a recoverable error.

Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 detected an earlier release of the I/O FPGA software. The I/O FPGA software needs to be upgraded to the latest release.

Recommended Action Upgrade the I/O FPGA software to the newest release. If you require assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 earlier version of the I/O FPGA software has been detected.

Recommended Action Upgrade the I/O FPGA software to the latest version. If you require assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 OSM has encountered an internal error while setting up the statistics system.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWTLC-5

Explanation The SP detected a sequence error on the backplane bus of the OSM. The system called a reset sequence from the EARL to recover from this error. System traffic should recover and continue normally.

Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 ASICs on the OSM were reset so that the module could recover from a bus sequence error. This condition usually occurs under heavy traffic with HA-related switchover or a module OIR operation. System traffic should recover and continue normally.

Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 OSM fabric interface ASIC is being reinitialized because of a system backplane bus sequence error, a fatal ASIC error, or a line card error.

Recommended Action If traffic recovers, no action is required. 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.

Explanation The OSM Medusa ASIC is being reinitialized because of a system backplane bus sequence error or a fatal ASIC error on the module itself.

Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 ASICs on the OSM line card has been reset so that it can recover from backplane switching bus sequence errors or local hardware ASIC errors. This condition is usually occurs under stress trafficwith HA-related switchover or a line card OIR operation. System traffic should recover and continue normally.

Recommended Action If traffic recovers, no action is required. 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.

CWTLC-6

Explanation The supervisor engine has changed the CWTLC fabric interface ASIC switching bus mode.

Recommended Action No action is required.

CWTLC_ATOM-3

Explanation The internal interface ID that is required by the OSM to establish an AToM connection is either invalid or is mismatched with the control plane MPLS data structure for this connection. The current interface ID of the OSM has lost its synchronization with the interface ID of the control plane for this connection. This condition is usually caused by unfavorable network conditions such as a failover operation and can occur during normal system operation.

Recommended Action Enter the appropriate AToM commands for either the Frame Relay over MPLS, Cell Relay over MPLS, AAL5 over MPLS, or Frame Relay local switching to remove the AToM connection, then add the connection again. Performing this action once should successfully reestablish the connection.

Explanation Frame Relay over MPLS and Frame Relay local switching features are supported only on enhanced Optical Services Modules. Nonenhanced OSMs do not support these features.

Recommended Action Remove the configuration of the unsupported features, or upgrade this module to an enhanced OSM.

CWTLC_CHOC-3

Explanation The module hardware has experienced the specified 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWTLC_CHOCX-3

Explanation The module hardware has experienced the specified 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 you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWTLC_GEWAN-3

Explanation The FPGA could not be initialized. The cause of this condition is specified in the message text on the console or in the system log. As a result of this condition, the device is not operational and has been disabled.

Recommended Action Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module 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 An error has occurred while the system was setting the GEMAC component of the Gigabit Ethernet WAN module in 9,000-buffer mode (a buffer mode that supports jumbo frames). This condition occurred on the port specified in 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 error occurred during initialization of the GEMAC 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 and show tech-support commands and your pertinent troubleshooting logs.

Explanation The port number could not be determined from the given interface number.

Recommended Action Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module 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 specified MAC address operation is unknown and cannot be performed.

Recommended Action Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module 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 enabling/disabling of the auto-negotiation functionality on a GE-WAN port 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 GE-WAN port command 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 The addition or removal of a MAC address from the MAC address table has failed.

Recommended Action Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module 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 An error occurred during initialization of the protocol converter FPGA.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

CWTLC_RP-3

Explanation The last PXF select operation was not followed by a deselect 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.

DATACORRUPTION-1

Explanation Data corruption has been 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.

DATA_DESCR-3

Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 data descriptor could not be encoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to 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 Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor controller. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor hwidb. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor [hwidb|swidb|controller]. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor [hwidb|swidb|controller]. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.