-
Cisco IOS Release 12.4 System Messages, Volume 1 of 2
-
System Messages Overview
-
AAA through ASPP
-
AT through BGP
-
BIT through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBUS
-
DCV through DSCREDCLK
-
DSI through ENT
-
ENV_MON through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFINDEX through ISA
-
ISDN through LCCOREDUMP
-
LCINFO through MBRI
-
Volume 1 Glossary
-
Table Of Contents
CPAD Messages
The following are compression service adapter (CSA) messages.
Error Message%CPAD-1-ERROR : [chars]: [chars]
Explanation An error has occurred in the application that is using the CSA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPAD-1-INITFAIL : Slot [dec]: [chars]
Explanation The CSA driver has failed to initialize at the specified point.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPAD-1-NOMEMORY : [chars] creation failed for slot [dec]
Explanation The CSA driver, in its initialization phase, could not allocate memory for the specified data structure.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPAD-1-PLXINIT : bay [dec] Invalid vendor/device id [dec]
Explanation The CSA driver, in its initialization phase, has encountered a communication failure with the CSA in the specified bay.
Recommended Action Consider reseating the specified CSA. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPAD-1-SHUTCARD : bay [dec]: Deactivating card
Explanation An error has occurred during initialization. The CSA is being deactivated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPAD-6-SHUTDOWN : [chars] shutting down
Explanation The specified CSA is shutting down. It may have been physically removed.
Recommended Action No action is required.
Error Message%CPAD-6-STARTUP : [chars] starting up
Explanation The specified CSA has initialized successfully.
Recommended Action No action is required.
CPE_MMI Messages
The following are CPE MMI messages.
Error Message%CPE_MMI-6-CONTXENGINEID : Get cdcpEntityContextEngineID from proxy element
Explanation The system has performed and SNMP get on the cdcpEntityContextEngineID from the proxy element.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-6-DISCOVER : Discover proxy element's engine ID
Explanation The system has performed an SNMP get to discover the engine ID of the proxy element.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-6-DISCOVERFAIL : Discover proxy element's engine ID failed
Explanation The system has performed an SNMP get to discover the engine ID of the proxy element; however, the SNMP get has failed.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-6-KILLMMI : CPE MMI not needed, delete process
Explanation The MMI process has removed itself. This removal was caused by either the unavailability of a Proxy Element, a user or proxy element command, or a failure.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-6-MMIENABLE : Get cdcpEntityMmiEnable from proxy element
Explanation The system has performed an SNMP get on the cdcpEntityMmiEnable from the proxy element.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-6-MMINOTENABLE : cdcpEntityMmiEnable from proxy element is set to false
Explanation The cdcpEntityMmiEnable from the proxy element is set to false, which means that the system should not obtain configuration data from the proxy element.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-6-MMIPVCDOWN : Wait for interface atm to come up
Explanation This MMI PVC (the default ILMI PVC or one entered by the user) is required to be set up at the start of the configuration process. The MMC PVI has failed to come up and is waiting for the PVC to be set up. This failure can be caused by a bad connection, a bad configuration in the connecting DSLAM, or a different PVC used by the proxy element. The self-configuration will fail. This message was the result of either a mmi pvc command entered by the user or part of the system configuration process.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-6-NOCONTXENGINEID : Get cdcpEntityContextEngineID failed
Explanation The system has performed an SNMP get on the cdcpEntityContextEngineID from the proxy element; however, the SNMP get has failed, and the local engine ID has not been updated.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPE_MMI-4-NOMMIPVC : Set up MMI PVC failed
Explanation The system failed to set the ATM PVC for the MMI.
Recommended Action This is a debug message only. If the system has successfully configured itself, no action is required. If the system has failed to configure itself, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CPM Messages
The following are Combination Port Module (CPM) device driver messages.
Error Message%CPM-3-DISCOVER : CPM at slot [dec]: PCI discovery failed count = [dec]
Explanation One of the interface controller devices on the module did not initialize properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CPM-3-INCORRECT_ID : CPM at slot [dec]: PCI device not supported
Explanation An interface controller device did not report the correct PCI device ID.
Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CPOS Messages
The following are common Packet over SONET messages.
Error Message%CPOS-3-HW_FAULT : POS HW error, [chars], error_code=[hex]
Explanation A PoS operation error has occurred in the hardware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CPOS-3-INTERNAL : POS internal error, [chars]
Explanation An internal PoS error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CPOS-3-MAJOR_FAULT : POS unrecoverable error, [chars], error_code=[hex]
Explanation A unrecoverable PoS operation error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CPOS-3-MIBINITFAIL : POS MIB initialization failed, [chars]
Explanation The MIB initialization for PoS has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CPOS-5-PERIODIC_STATS : POS periodic stats collection not run for [dec] seconds
Explanation There is a delay in collecting PoS statistics. This delay usually occurs when the RP is busy with high-priority tasks and can trigger line alarms for a short period of time. The time-based statistics for this interface can also become skewed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CPOS-3-POSMISMATCH : [chars], expected [hex], actual [hex]
Explanation PCI initialization for POS has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CRYPTO Messages
The following are encryption messages.
Error Message%CRYPTO-0-AUDITFAIL : Encryption audit check found the wrong level of encryption in this image
Explanation The audit check verifying encryption entitlement within the Cisco IOS software image found either encryption in a nonencryption image or the wrong strength within a Cisco IOS software image that contains encryption. Use of the encryption may violate U.S. export laws and regulations.
Recommended Action Obtain a replacement Cisco IOS software image, either by opening a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or by contacting your Cisco technical support representative.
Error Message%CRYPTO-4-AUDITWARN : Encryption audit check could not be performed
Explanation The audit check verifying encryption entitlement within the Cisco IOS software image could not be performed because of incomplete system configuration.
Recommended Action Manually verify that this Cisco IOS software image is entitled to contain encryption.
Error Message%CRYPTO-6-AUTOGEN : Generated new [dec] bit key pair
Explanation An auto-enroll operation has generated a new router key pair.
Recommended Action This is an informational message only. No action is required.
Error Message%CRYPTO-6-AUTOSAVE : Running configuration saved to NVRAM
Explanation An auto-enroll operation has obtained a new router key pair and certificate and has automatically written information to NVRAM to save them.
Recommended Action This is an informational message only. No action is required.
Error Message%CRYPTO-3-BADFP : Certificate fingerprint mismatch for certificate - certificate not accepted
Explanation The fingerprint of a certificate received from a certificate authority did not match a fingerprint that was saved in NVRAM. The certificate may not be valid.
Recommended Action Contact the certificate authority administrator to manually compare the certificate fingerprint.
Error Message%CRYPTO-3-BADMAGIC : Bad [chars] magic number ([hex]).
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CRYPTO-6-CERT_FATAL_ERR : [chars]
Explanation A fatal error has occurred while a certificate was being enrolled. The operation has been canceled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-3-CERTCHECK : Certificates with invalid status have been detected!!!
Explanation Certificates saved in memory have been checked with the certificate revocation list. Some certificates have been detected as having an invalid status.
Recommended Action Check the status of the certificate. If necessary, contact the certificate authority administrator. Certificate enrollment may be required.
Error Message%CRYPTO-6-CERTFAIL : Certificate enrollment failed.
Explanation A fatal error occurred while a certificate was being enrolled.
Recommended Action Contact the CA administrator.
Error Message%CRYPTO-6-CERTIFSRECV : Could not receive router's Certificate from file system.
Explanation The certificate for the router could not be received from file system.
Recommended Action Verify the enrollment URL. Also verify that the router can read from the file system.
Error Message%CRYPTO-6-CERTIFSSEND : Could not send Certificate enrollment request to file system.
Explanation The certificate enrollment request could not be sent to the file system.
Recommended Action Verify the enrollment URL. Also verify that the router is able to read from the file system.
Error Message%CRYPTO-6-CERTPENDING : Enter manual authentication ...
Explanation The CA has detected that the router requires manual authentication.
Recommended Action Follow the manual authentication procedure.
Error Message%CRYPTO-6-CERTREJECT : Certificate enrollment request was rejected by Certificate Authority
Explanation A previous certificate enrollment request was received by the certificate authority. It has rejected the enrollment request.
Recommended Action Contact the certificate authority administrator.
Error Message%CRYPTO-6-CERTRET : Certificate received from Certificate Authority
Explanation A previous certificate enrollment request was received by the certificate authority. It has issued the certificate and sent back a copy.
Recommended Action This is an informational message only. No action is required.
Error Message%CRYPTO-3-CERTRETFAIL : Certificate enrollment failed.
Explanation The certificate enrollment transaction has failed because of an internal error.
Recommended Action Contact a CE administrator. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CRYPTO-6-CERTTFTPRECV : Could not tftp router's Certificate.
Explanation The certificate for the router could not be received using TFTP.
Recommended Action Verify that the TFTP enrollment URL is valid. Also verify that the router is able to read from the TFTP server.
Error Message%CRYPTO-6-CERTTFTPSEND : Could not tftp Certificate enrollment request.
Explanation The certificate enrollment request could not be sent using TFTP.
Recommended Action Verify that the TFTP enrollment URL is valid. Also verify that the router is able to write to the TFTP server.
Error Message%CRYPTO-6-CET_END_OF_LIFE : CET connection msg in an IPSEC_ONLY_IMAGE
Explanation CET is not available for all Cisco IOS releases after and including Cisco IOS release 12.2(1).
Recommended Action No action is required.
Error Message%CRYPTO-3-CONNID_ALLOC_FAIL : Crypto engine failed to allocate a connection ID for negotiation from [IP_address] to [IP_address]
Explanation The encryption (crypto) engine has exhausted all its available connection IDs or is malfunctioning.
Recommended Action Decrease the number of concurrent connections or inspect the crypto engine.
Error Message%CRYPTO-4-ENC_METHOD_NOT_SUPPORTED : Invalid encryption method for IKE policy [int]
Explanation The configured encryption method is not supported.
Recommended Action Use any of the encryption methods that are valid for the ISAKMP policy.
Error Message%CRYPTO-3-ENGINE_BAD_ID : Crypto Engine id [dec] is invalid
Explanation The packet has its engine ID set to something other than "software crypto" or "hardware crypto". The system cannot determine which encryption (crypto) engine to use. The packet will be sent to the default crypto engine, which is the "software crypto" engine.
Recommended Action No action is required.
Error Message%CRYPTO-6-ENROLL_CANCEL : Certificate enrollment is cancelled.
Explanation The current certificate enrollment has been canceled.
Recommended Action This message occurs as a response to the no crypto ca enroll or no crypto ca trust-point commands. If this was a manually initiated enrollment, use the crypto ca enroll command to reenter the enrollment process at a later time. Entering the no crypto ca enroll command to cancel an enrollment session does not turn off automatic enrollment if it was on. The router does not need to be restarted.
Error Message%CRYPTO-6-EZVPN_CONNECTION_DOWN : [chars]
Explanation The EZVPN connection is being closed. The IPsec and IKE security associations will also be brought down.
Recommended Action No action is required.
Error Message%CRYPTO-6-EZVPN_CONNECTION_UP : [chars]
Explanation The EZVPN connection is up for the client mentioned. Both IPsec and IKE security associations are up now.
Recommended Action No action is required.
Error Message%CRYPTO-3-GETCACERT : Failed to find CA cert in memory.
Explanation The CA certificate was not found in system memory.
Recommended Action Check the status of the certificate and contact the CA administrator.
Error Message%CRYPTO-3-GETCARACERT : Failed to receive RA/CA certificates.
Explanation An error occurred while CA or RA certificates were being parsed and processed.
Recommended Action Check the status of the system or contact the certificate authority administrator.
Error Message%CRYPTO-6-GETCERTINITIAL : Certificate enrollment failed in manual mode
Explanation The current certificate enrollment has failed in manual mode.
Recommended Action Contact the CA administrator.
Error Message%CRYPTO-3-GETCRL : Query the Certificate Revocation List from CA failed.
Explanation The attempt to query the CRL from the CA server has failed for one of several possible reasons.
Recommended Action Contact the CA administrator.
Error Message%CRYPTO-3-HTTPSEND : Failed to send out message to CA server.
Explanation A failure to send out a message to the CA server was caused by an HTTP transaction.
Recommended Action Check the HTTP connection to the CA server.
Error Message%CRYPTO-4-IA_CLEARTEXT : Unencrypted traffic [chars] [IP_address] because crypto optional is configured
Explanation Clear text 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 enabled, which allows such traffic.
Recommended Action If you did not intend to configure the "CRYPTO IPSEC OPTIONAL ENABLE" setting, reconfigure the router to disable this setting.
Error Message%CRYPTO-4-IA_ENABLE : Security warning: crypto ipsec optional is configured
Explanation Currently, the router has the "CRYPTO IPSEC OPTIONAL ENABLE" setting enabled. This setting allows data that normally would be encrypted to be sent unencrypted.
Recommended Action If you did not intend to configure the "CRYPTO IPSEC OPTIONAL ENABLE" setting, reconfigure the router to disable this setting.
Error Message%CRYPTO-4-IKE_DENY_SA_REQ : IKE denied an [chars] SA request from [IP_address] to [IP_address] due to [chars]
Explanation The call admission control component has been configured globally or at the IKE level on this device. Because of this configuration, an IKE SA request was denied for of the reason given in the error message.
Recommended Action Depending on the reason for denial of the request, either reduce the load on the system so that it can process new IKE SA requests or increase the maximum allowed IKE sessions if more are needed.
Error Message%CRYPTO-3-IKE_PAK_IN_Q_TIME_LIMIT_EXCEED : Pak spent too much time in the IKE input queues
Explanation An incoming IKE packet has spent too much time in the IKE input queues. This condition can occur when the IKE subsystem is under a heavy load because a lot of peers are trying to set up SAs at the same time and IKE is not able to handle all the incoming packets in a timely manner.
Recommended Action Attempt to determine why so many peers are simultaneously trying to set up SAs at the same time and, if possible, try to avoid or minimize this type of network condition.
Error Message%CRYPTO-4-IKE_QUICKMODE_BAD_CERT : encrypted connection attempted with a peer without the\nconfigured certificate attributes
Explanation An encrypting peer has attempted to establish an IPSec session with an interface for which it was unauthorized. This condition might be considered a hostile event.
Recommended Action Check that the peer is authorized to connect with the IPSec connection. If the peer is authorized to connect with the IPSec connection, this condition may be the result of a configuration issue. If the peer is not authorized to connect with the IPSec connection, contact the peer administrator.
Error Message%CRYPTO-5-IKE_SA_HA_STATUS : IKE sa's if any, for vip [IP_address] will change from [chars] to [chars]
Explanation A cryptographic IKE SA has changed its HA status.
Recommended Action No action is required.
Error Message%CRYPTO-4-IKE_SA_LIMIT : IKE active SA count is [int] but SA limit has been set to [int].
Explanation The IKE SA limit that was set is lower than the number of active IKE SAs. Active SAs 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 required to establish connectivity.
Error Message%CRYPTO-6-IKE_TED_BAD_REPLY : Received TED reply that did not correspond to a TED probe
Explanation The received TED reply does not match the TED probe that is currently outstanding. This error might be a one-time occurrence caused by a delay of the TED reply or by ill-formed packets that were sent by the peer. Ill-formed packets sent by the peer may indicate a hostile event.
Recommended Action If the problem occurs more than once, contact the administrator of the peer.
Error Message%CRYPTO-3-IKEINIT : [chars]
Explanation An IKE initialization error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-6-IKMP_ADD_KEY_FAIL : Unable to add public key for [chars] ([IP_address]) to key ring
Explanation Keys are stored in key rings on the router. An attempt to add another key has failed.
Recommended Action Check local key rings.
Error Message%CRYPTO-5-IKMP_AG_MODE_DISABLED : Unable to initiate or respond to Aggressive Mode while disabled
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, remove the command.
Error Message%CRYPTO-6-IKMP_AUTH_FAIL : Authentication method [dec] failed with host [IP_address]
Explanation The IKE process was unable to authenticate its security association with its remote peer.
Recommended Action Contact the administrator of the remote peer.
Error Message%CRYPTO-6-IKMP_BAD_CERT_USE : Certificate for peer at [IP_address] prohibits attempted use ([chars]).
Explanation X.509v3 certificates can contain usage restrictions that limit the use of the certificate for signatures or for key exchange (encryption). The peer attempted to use the certificate in a manner that violated these usage restrictions.
Recommended Action Contact the remote peer and the CA of the remote peer.
Error Message%CRYPTO-6-IKMP_BAD_DOI_NOTIFY : DOI of [dec] in notify message from [IP_address]
Explanation The DOI field in notify messages gives the receiver a context in which to understand the message being notified. This DOI value is not understood, and therefore the message cannot be understood.
Recommended Action If this situation persists, contact the remote peer.
Error Message%CRYPTO-6-IKMP_BAD_DOI_SA : DOI value [dec] from SA offer from [IP_address] is invalid
Explanation The DOI field of an SA offer defines how to parse the fields. The SAs that have an unknown DOI cannot be parsed.
Recommended Action If this situation persists, contact the administrator of the remote peer.
Error Message%CRYPTO-4-IKMP_BAD_MESSAGE : IKE message from [IP_address] failed its sanity check or is malformed
Explanation A quick verification check is done on all received ISAKMP messages to ensure that all component payload types are valid and that the sum of their individual lengths equals the total length of the received message. This message indicates a failed verification check. Persistently bad messages could mean a denial-of-service attack or bad decryption.
Recommended Action Contact the administrator of the remote peer.
Error Message%CRYPTO-6-IKMP_CRYPT_FAILURE : IKE (connection id [dec]) unable to [chars] packet
Explanation Encryption or decryption on a particular IKE thread has failed.
Recommended Action Contact the administrator of the remote peer.
Error Message%CRYPTO-5-IKMP_INVAL_CERT : Certificate received from [IP_address] is bad: [chars]
Explanation The certificate given by the remote peer either has been revoked or has expired (the certificate is invalid) or the signature check on the certificate has failed (invalid signature).
Recommended Action Contact the CA of the remote peer. The CA certificate may be invalid.
Error Message%CRYPTO-4-IKMP_INVALID_POLICY : ISAKMP policy rsa-encr not supported by crypto HW accelerator [chars]
Explanation RSA encryption is not supported by Hi-Fn compression-based encryption (crypto) hardware accelerators.
Recommended Action Specify the authentication method using the isakmp command and the rsa-sig keyword.
Error Message%CRYPTO-4-IKMP_ISR_LIMIT_MAX : INV SPI RECOV LIMIT [dec] maxed [chars] [IP_address] [IP_address]
Explanation The maximum limit of "INVALID SPI RECOVERY" SAs has been reached.
Recommended Action It might be necessary to reload the local system.
Error Message%CRYPTO-6-IKMP_MODE_FAILURE : Processing of [chars] mode failed with peer at [IP_address]
Explanation Negotiation with the remote peer has failed.
Recommended Action If this situation persists, contact the remote peer.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_ADDR_MATCH : ID of [IP_address] (type [dec]) and certificate addr with [IP_address]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information taken from the IP address of the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_DN_MATCH : ID of [chars] (type [dec]) and certificate DN with [chars]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information taken from the name on the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_FQDN_MATCH : ID of [chars] (type [dec]) and certificate fqdn with [chars]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information taken from the FQDN of the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_USER_FQDN_MATCH : ID of [chars] (type [dec]) and certificate user fqdn with [chars]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information taken from the FQDN of the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message%CRYPTO-4-IKMP_NO_SA : IKE message from [IP_address] has no SA and is not an initialization offer
Explanation IKE maintains the current state for a communication in the form of security associations. No security association exists for the specified packet, and it is not an initial offer from the peer to establish one. This situation could indicate a denial-of-service attack.
Recommended Action Contact the remote peer and the administrator of the remote peer.
Error Message%CRYPTO-6-IKMP_NOT_ENCRYPTED : IKE packet from [IP_address] was not encrypted and it should've been.
Explanation A portion of the IKE is unencrypted, and a portion is encrypted. This message should have been encrypted but was not.
Recommended Action Contact the remote peer.
Error Message%CRYPTO-3-IKMP_PEER_INIT_FAILURE : IKE failed to create IKE peer tree or leaf node.
Explanation IKE has failed to allocate memory for the IKE peer tree.
Recommended Action More DRAM may be required in order to run the image.
Error Message%CRYPTO-4-IKMP_PKT_OVERFLOW : ISAKMP message from [IP_address] larger ([dec]) than the UDP packet length ([dec])
Explanation ISAKMP messages are carried in UDP packets and have their own message length field. The message length field of this message was greater than the length of the UDP packet. This situation could indicate a denial-of-service attack.
Recommended Action Contact the remote peer and the administrator of the remote peer.
Error Message%CRYPTO-3-IKMP_QUERY_KEY : Querying key pair failed.
Explanation A public key or private key query attempt that used a subject name has failed.
Recommended Action Check the subject name in the certificate.
Error Message%CRYPTO-6-IKMP_SA_NOT_AUTH : Cannot accept Quick Mode exchange from [IP_address] if SA is not authenticated!
Explanation Although the IKE security association with the remote peer was not authenticated, the peer attempted to begin a Quick Mode exchange. This exchange can be performed only with an authenticated security association.
Recommended Action Contact the remote peer.
Error Message%CRYPTO-6-IKMP_SA_NOT_OFFERED : Remote peer [IP_address] responded with attribute [chars] not offered or changed
Explanation IKE peers negotiate policy by having the initiator offer a list of possible protection suites. The responder has returned a type of protection suite that the initiator did not offer.
Recommended Action Contact the remote peer.
Error Message%CRYPTO-6-IKMP_UNITY_BUT_NO_OU_IN_CERT : Cert presented by peer [IP_address] contains no OU field. Unable to obtain group identity.
Explanation The certificate presented by the Unity peer contains no organizational unit field. The organizational unit field is necessary to determine the policy information based on the group identity. As a result of the lack of an organizational unit field, IKE or IPSec negotiation may fail.
Recommended Action Check with the administrator of the certification authority for the organizational unit of this certificate. If necessary, request a new certificate with an organizational unit that corresponds to the group name defined in the router configuration.
Error Message%CRYPTO-6-IKMP_UNK_EXCHANGE : IKE peer at [IP_address] sent a message with unknown exchange [dec]
Explanation IKE performs actions on messages based on defined exchanges. The message that was received had an unknown exchange.
Recommended Action Contact the administrator of the remote peer.
Error Message%CRYPTO-3-INVALID_INPUT : The input to the parser command is not correct
Explanation An internal software error has occurred.
Recommended Action Reload the router, and reenter the command. File a bug report; to do so, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-3-INVALIDCACERT : Failed to process CA certificate.
Explanation The CA certificate received from the CA server could not be processed.
Recommended Action Enter the parser command and try again to process the certificate.
Error Message%CRYPTO-4-IPSEC_AAA_START_FAILURE : IPSEC Accounting was unable to send start record
Explanation The AAA subsystem was unable to send the accounting start record for IPSec. This condition could be due to the unreachable status of the AAA server.
Recommended Action Ensure that the AAA server is reachable and enabled for accounting.
Error Message%CRYPTO-4-IPSEC_AAA_STOP_FAILURE : IPSEC Accounting was unable to send stop record
Explanation The AAA subsystem was unable to send the accounting stop record for IPSec. This condition could be due to the unreachable status of the AAA server.
Recommended Action Ensure that the AAA server is reachable and enabled for accounting.
Error Message%CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED : Transform [chars] not valid under IPSec transform [chars]
Explanation The configured encryption algorithm is not supported.
Recommended Action Specify a valid encryption algorithm for the IPSec transform.
Error Message%CRYPTO-5-IPSEC_SA_HA_STATUS : IPSec sa's if any, for vip [IP_address] will change from [chars] to [chars]
Explanation A cryptographic IPSec SA has changed its HA status.
Recommended Action No action is required.
Error Message%CRYPTO-6-ISAKMP_MANUAL_DELETE : IKE SA manually deleted. Do 'clear crypto sa peer [IP_address]' to manually clear IPSec SA's covered by this IKE SA.
Explanation The IKE SA was deleted by user command. However, keepalives for this connection are enabled, and IPSec SAs covered by this IKE SA still exist. Because this IKE SA is now deleted, these IPSec SAs have no IKE SA covering them.
Recommended Action Enter the parser command to manually delete these IPSec SAs.
Error Message%CRYPTO-6-ISAKMP_ON_OFF : ISAKMP is [chars]
Explanation The ISAKMP process has been switched on or off. This condition occurred either by user-entered CLI or because no encryption (crypto) map or EzVPN configuration is applied to any interface.
Recommended Action No action is required.
Error Message%CRYPTO-4-LLQ_OVERSUBSCRIBE : Sum of priority class bandwidth exceeds crypto engine's throughput for small packets (crypto b/w=[int] kbps, allocated b/w=[int] kbps). Some priority traffic may be dropped.
Explanation The CRYPTO engine may be oversubscribed by priority class traffic. This condition occurs when the user attempts to provision more priority class bandwidth than the CRYPTO engine can process. If each class is sending at its maximum rate, some priority packets might be dropped.
Recommended Action Reduce the priority class bandwidth or reduce the number of priority classes in the policy map.
Error Message%CRYPTO-3-MTREE_CMD_BLOCK : Mtree command [dec] was blocked from the the mtree process queue.
Explanation An attempt was made to enqueue a command to the encryption (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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CRYPTO-4-NAMED_KEY_DNS_FAIL : DNS lookup for peer [chars] \n failed. Use the "addressed-key" command instead.
Explanation The named-key command has attempted to resolve the entered DNS name. DNS resolution has failed, and as a result, the named-key command has failed.
Recommended Action Enter the addressed-key command to assign the public key on the basis of the IP address of the peer.
Error Message%CRYPTO-4-NOAUTOSAVE : Configuration was modified. Issue "write memory" to save new certificate
Explanation Auto-enroll has obtained a new router key pair and certificate. However, the running configuration was previously modified.
Recommended Action Issue the write memory command to save the new certificates and keys.
Error Message%CRYPTO-3-NOSOCKET : Unable to open [chars]
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 the "crypto isakmp" process.
Error Message%CRYPTO-6-PKCS12EXPORT_FAIL : PKCS #12 Export Failed.
Explanation An attempt to generate and export a PKCS#12 key and certificate file has failed.
Recommended Action No action is required. This is an informational message only.
Error Message%CRYPTO-6-PKCS12EXPORT_SUCCESS : PKCS #12 Successfully Exported.
Explanation A PKCS #12 key and certificate file has been generated and successfully exported.
Recommended Action No action is required. This is an informational message only.
Error Message%CRYPTO-6-PKCS12IMPORT_FAIL : PKCS #12 Import Failed.
Explanation An attempt to import a PKCS#12 key and certificate file has failed.
Recommended Action No action is required. This is an informational message only.
Error Message%CRYPTO-6-PKCS12IMPORT_SUCCESS : PKCS #12 Successfully Imported.
Explanation A PKCS#12 key and certificate file has been successfully imported.
Recommended Action No action required. This is an informational message only.
Error Message%CRYPTO-3-PKIINPUT : Wait response from server ....
Explanation The PKI client is waiting for the response from the server.
Recommended Action No action is required.
Error Message%CRYPTO-4-PKT_REPLAY_ERR : [chars] connection id=[dec]
Explanation The replay processing has failed. The failed replay processing may be a temporary condition caused by the wait for new SAs to be established. In the inbound case, this error might also be caused by an actual replay attack. This activity can be considered a hostile event.
Recommended Action If the problem appears to be more than a transient one, contact the peer administrator.
Error Message%CRYPTO-3-POLICY_CKSUM_ERROR : Crypto policy checksum failure. Crypto access list [chars], crypto map [chars], interface [chars]
Explanation An encryption (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 occurring in crypto policy data or a memory area that 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CRYPTO-3-POLLCACERT : Polling CA certificate .....
Explanation The system is polling the CA certificate.
Recommended Action Check if the CA or LDAP server is online.
Error Message%CRYPTO-3-POLLING : Polling for certificate response...
Explanation GetCertInitial is polling for a certificate response.
Recommended Action Wait for the server response or cancel the polling.
Error Message%CRYPTO-3-POLLRACERT : Polling RA certificate .....
Explanation Polling for an RA certificate.
Recommended Action Check if the CA or IDAP server is online.
Error Message%CRYPTO-3-POLLROUTERCERT : Polling Router certificate .....
Explanation Polling for a router certificate.
Recommended Action Check if the CA or IDAP server is online.
Error Message%CRYPTO-6-PRINTABORT : [chars] caused early termination of show output[chars]
Explanation While a list was being shown, the list or the elements changed. The list or the elements can change if the SAs were renegotiated at the time that the show command was paused, or if a user reconfigured or cleared the SAs. This change is not an error but rather a side effect of a dynamic system.
Recommended Action In general, this message is a warning that the output from the show command is probably incomplete. Reentering the show command should provide the newest information. On a busy system, with SAs that change often, this message may appear frequently.
Error Message%CRYPTO-6-PRNG_SEED_KEY_ERROR : Pseudo-random number generator seed and seed key was identical
Explanation The X9.17 random number specification requires that the system check for the same value appearing as the seed and the seed key. This message indicates that that 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.
Error Message%CRYPTO-3-QUERY_KEY : Querying key pair failed.
Explanation An attempt to query the public key and private key using the subject name has failed.
Recommended Action Check the subject name, and resubmit the enrollment request.
Error Message%CRYPTO-3-QUERYCACERT : Failed to query CA certificate.
Explanation A query against the CA certificate from the CA server has failed.
Recommended Action Enter the parser command to verify the CA trusted-root or identity configuration. Ensure that the appropriate server, either the CA or LDAP server, is reachable and that the server is properly configured to respond to the query from the router.
Error Message%CRYPTO-3-QUERYRACERT : Failed to query RA certificate.
Explanation A failure to get RA certificates has occurred.
Recommended Action Check if the CA or IDAP server is online.
Error Message%CRYPTO-3-QUERYROUTERCERT : Failed to query router certificate.
Explanation A query against the router certificate has failed.
Recommended Action Check if the CA or IDAP server is online.
Error Message%CRYPTO-6-RANDOM : A pseudo-random number was generated twice in succession
Explanation A pseudorandom number generator produced the same number twice in succession.
Recommended Action Under normal circumstances, it is not a problem if a pseudorandom number generator occasionally produces the same number twice in succession. If this message occurs frequently, manually reload the system. If the message is persistent across reloads, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-4-RECVD_PKT_FAIL_DECOMPRESS : pcp: [dec] byte packet failed to decompresspcp: dest_addr=[IP_address], src_addr=[IP_address]
Explanation The received IPPCP packet failed to decompress because of a decompression buffer error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-4-RECVD_PKT_INV_IDENTITY : [chars] (ip) dest_addr= [IP_address], src_addr= [IP_address], prot= [dec] (ident) local=[IP_address], remote=[IP_address] local proxy=[IP_address]/[IP_address]/[dec]/[dec], remote_proxy=[IP_address]/[IP_address]/[dec]/[dec]
Explanation A decapsulated IPSec packet does not match the negotiated identity. An SA selection error is causing the peer to send other traffic through this SA. This activity could be considered a hostile event.
Recommended Action Contact the peer administrator to compare policy settings.
Error Message%CRYPTO-4-RECVD_PKT_INV_IDENTITY_ACL : ipsec check access: identity not allowed by ACL (ip) dest_addr= [IP_address], src_addr= [IP_address], prot= [dec]
Explanation A decapsulated packet has failed the ACL check. The peer is sending other traffic through this SA. The activity may be caused by an SA selection error by the peer and could be considered a hostile event.
Recommended Action Contact the peer administrator to compare policy settings.
Error Message%CRYPTO-4-RECVD_PKT_INV_PROT : decapsulate: packet missing [chars], destadr=[IP_address], actual prot=[dec]
Explanation A received IPSec packet was missing an expected AH or ESP header. The peer is sending packets that do not match the negotiated security policy. This activity could be considered a hostile event.
Recommended Action Contact the peer administrator.
Error Message%CRYPTO-4-RECVD_PKT_INV_SPI : decaps: rec'd IPSEC packet has invalid spi for destaddr=[IP_address], prot=[dec], spi=[hex]([dec])
Explanation A received IPSec packet specifies an SPI that does not exist in SADB. This may be a temporary condition because of slight differences in the aging of SAs between the IPSec peers or because the local SAs have been cleared. It may also be caused by invalid packets sent by the IPSec peer. This activity could be considered a hostile event.
Recommended Action If the local SAs have been cleared, the peer may not know. In this case, if a new connection is established from the local router, the two peers may reestablish successfully. If the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer administrator.
Error Message%CRYPTO-4-RECVD_PKT_INV_UDP_WRAPPER : Rec'd packet has invalid udp wrapper protocol.\n\ncryptoflags = [hex], sa->udp_wrapper_support = [dec],transform = [hex]
Explanation Either a UDP or encapsulated packet was received that is not a correct negotiation transform. Or the system expected an UDP-encapsulated packet, but it received a non-UDP packet. There might be a policy setup error on the peer. This activity could be considered a hostile event.
Recommended Action Contact the administrator of the router or host that sent the packet to compare policy settings.
Error Message%CRYPTO-4-RECVD_PKT_MAC_ERR : decrypt: mac verify failed for connection id=[dec]
Explanation The MAC verify processing failed. This might be caused by the use of the wrong key by either party during the MAC calculations. This activity could be considered a hostile event.
Recommended Action Contact the peer administrator.
Error Message%CRYPTO-4-RECVD_PKT_MSG_LEN_ERR : decapsulate: packet has bad [chars] length destadr=[IP_address], prot=[dec], len=[dec]
Explanation The received IPSec packet is malformed, possibly because of an encapsulation error. The peer is sending malformed packets. This activity could be considered a hostile event.
Recommended Action Contact the peer administrator.
Error Message%CRYPTO-4-RECVD_PKT_NO_CPI : pcp: wrong CPI, [hex], in packet from [IP_address]
Explanation The received IPPCP packet had an improper CPI. This might be caused by the use of an old IPPCP security association.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-4-RECVD_PKT_NOT_IPSEC : Rec'd packet not an IPSEC packet.\n\n(ip) vrf/dest_addr= [chars]/[IP_address], src_addr= [IP_address], prot= [dec]
Explanation The received packet matched the encryption (crypto) map ACL, but the packet is not IPSec-encapsulated. The IPSec peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. This activity could be considered a hostile event.
Recommended Action Contact the peer administrator to compare policy settings of the IPSec peer.
Error Message%CRYPTO-4-REM_CRYPTOMAP_TS : \nPlease recheck your crypto map [chars].
Explanation A transform set entry has been removed from the encryption (crypto) map because the entry is no longer valid when the hardware crypto engine is enabled.
Recommended Action Create and apply a valid transform set to the crypto map.
Error Message%CRYPTO-3-REQCERT : Certificate enrollment message send out ...
Explanation The certificate enrollment message is being sent.
Recommended Action No action is required.
Error Message%CRYPTO-3-RSA_SELFTEST_FAILED : Generated RSA key failed self test
Explanation An automatic test of the newly generated RSA key pair has failed, and the RSA key has been automatically deleted.
Recommended Action Retry the operation and attempt to create another RSA key pair. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-0-SELF_TEST_FAILURE : Encryption self-test failed ([chars])
Explanation One of the encryption self-tests has failed. The encryption engine is not operable in this state.
Recommended Action If the failure persists, contact a Cisco technical support representative to obtain a replacement Cisco IOS image.
Error Message%CRYPTO-5-SESSION_STATUS : Crypto tunnel is [chars]. Peer [IP_address]:[dec] [chars] [chars] [chars] [chars] [chars] [chars] [chars] [chars]
Explanation This is a notification message for IPSec tunnel status.
Recommended Action No action is required.
Error Message%CRYPTO-3-SOCKETSELECT : Failed to select the socket.
Explanation A socket selection has caused a failure.
Recommended Action Check the TCP or socket debugging message.
Error Message%CRYPTO-3-SOCKETSEND : Failed to send out message to CA server.
Explanation An HTTP transaction has caused a failure.
Recommended Action Check the HTTP connection to the CA server.
Error Message%CRYPTO-6-TOKENADMINCHANGEPIN : Cryptographic Token [chars] ADMIN PIN change Successful
Explanation The cryptographic token has accepted the new administrator PIN offered by the router.
Recommended Action No action is required.
Error Message%CRYPTO-3-TOKENADMINLOCKEDOUT : Cryptographic Token [chars] Administrator PIN Locked due to too many unsuccessful login attempts
Explanation The cryptographic token has disabled the administrator 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.
Error Message%CRYPTO-6-TOKENADMINLOGIN : Cryptographic Token [chars] ADMIN Login Successful
Explanation The cryptographic token has accepted the administrator PIN offered by the router.
Recommended Action No action is required.
Error Message%CRYPTO-3-TOKENADMINLOGINFAILED : Cryptographic Token [chars] ADMIN Login FAILED
Explanation The cryptographic token has rejected the administrator PIN offered by the router.
Recommended Action Enter the crypto pki token admin-pin command to enter the correct PIN.
Error Message%CRYPTO-3-TOKENAPIFAILURE : Cryptographic Token [chars] API FAILED, error = [dec]
Explanation The cryptographic token returned an unexpected error .
Recommended Action Submit a bug report.
Error Message%CRYPTO-6-TOKENCHANGEPIN : Cryptographic Token [chars] PIN change Successful
Explanation The cryptographic token has accepted the new PIN offered by the router.
Recommended Action No action is required.
Error Message%CRYPTO-3-TOKENCHANGEPINFAILED : Cryptographic Token [chars] Change PIN FAILED
Explanation The cryptographic token has rejected the new PIN offered by the router.
Recommended Action Be sure that you are logged in to the token as administrator. Try a longer PIN.
Error Message%CRYPTO-6-TOKENINSERTED : Cryptographic token [chars] inserted in [chars]
Explanation A cryptographic token has been detected.
Recommended Action No action is required.
Error Message%CRYPTO-4-TOKENKEYSDEACTIVATED : RSA keypairs from token [chars] and associated IPSEC sessions being deactivated now
Explanation Router RSA keypairs and associated IPsec sessions are being deactivated because the token containing them was removed.
Recommended Action Re-insert the crypto token.
Error Message%CRYPTO-4-TOKENKEYTIMEOUT : RSA keypairs for token [chars] and associated IPSEC sessions will be deactivated in [dec] seconds
Explanation Router RSA keypairs and associated IPsec sessions will be deactivated when the timeout expires
Recommended Action Re-insert the crypto token before the timeout expires
Error Message%CRYPTO-3-TOKENLOCKEDOUT : Cryptographic Token [chars] PIN Locked due to too many unsuccessful login attempts
Explanation The cryptographic token has disabled the user PIN due to too many login failures.
Recommended Action Enter the crypto pki token admin-pin command to enter the correct administrator PIN.
Error Message%CRYPTO-6-TOKENLOGIN : Cryptographic Token [chars] Login Successful
Explanation The cryptographic token has accepted the PIN offered by the router
Recommended Action No action is required.
Error Message%CRYPTO-3-TOKENLOGINFAILED : Cryptographic Token [chars] Login FAILED
Explanation The cryptographic token has rejected the PIN offered by the router
Recommended Action Enter the crypto pki token user-pin command to enter the correct PIN.
Error Message%CRYPTO-6-TOKENLOGOUT : Cryptographic Token [chars] Logout Successful
Explanation The router has logged out from the cryptographic token.
Recommended Action No action is required.
Error Message%CRYPTO-6-TOKENREMOVED : Cryptographic token [chars] removed from [chars]
Explanation A cryptographic token has been detected.
Recommended Action No action is required.
Error Message%CRYPTO-6-TOKENSTOREKEY : Key [chars] stored on Cryptographic Token [chars] Successfully
Explanation A new keypair has been written out to the cryptographic token.
Recommended Action No action is required.
Error Message%CRYPTO-3-TOKENSTOREKEYFAILED : Key [chars] store on Cryptographic Token [chars] Failed
Explanation An error has occurred while 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 administrator.
Error Message%CRYPTO-6-TOKENTIMEOUTCANCELLED : Cryptographic Token [chars] re-inserted. removal timeout cancelled
Explanation A cryptographic token containing private key files has been re-inserted in time. The router RSA keypairs and associated IPsec sessions will NOT be deactivated.
Recommended Action No action is required.
Error Message%CRYPTO-4-TRANSFORM_NOT_SUPPORTED : Transform [chars] is not supported with the current hardware configuration. Global transform [chars] will be deleted.
Explanation The system configuration has been modified. Some IPSec transform operations that were valid earlier with software encryption (crypto) are no longer valid now that the system has switched to hardware crypto.
Recommended Action Create valid transform sets and update the crypto maps.
CRYPTO_HA_IKE Messages
The following are Crypto High Availability messages.
Error Message%CRYPTO_HA_IKE-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW : Crypto hardware is enabled and it does not support HA operation '[chars]'
Explanation Cryptographic hardware is enabled, but the hardware does not support HA operations (for example, insertion or extraction of keys).
Recommended Action Replace the cryptographic hardware with hardware that supports HA operations, or disable the hardware so that the software cryptographic engine is used instead of the hardware cryptographic engine.
Error Message%CRYPTO_HA_IKE-3-FAILOVER_ERROR : Attempt to failover IKE SA ([IP_address]:[IP_address]) failed due to [chars]. No stateful failover available for this SA.
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 Look for other error messages with a severity of "warning" (level 4), or enable debugging to determine the specific reason for the failure.
CRYPTO_HA_IPSEC Messages
The following are Crypto High Availability messages.
Error Message%CRYPTO_HA_IPSEC-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW : Crypto hardware is enabled and it does not support HA operation '[chars]'
Explanation Cryptographic hardware is enabled, but the hardware does not support HA operations (for example, insertion or extraction of keys).
Recommended Action Replace the cryptographic hardware with hardware that supports HA operations, or disable the hardware so that the software cryptographic engine is used instead of the hardware cryptographic engine.
Error Message%CRYPTO_HA_IPSEC-3-FAILOVER_ERROR : Attempt to failover IPSec SA ([IP_address]:[IP_address]) failed due to [chars]. No stateful failover available for this SA.
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 Look for other error messages with a severity of "warning" (level 4), or enable debugging to determine the specific reason for the failure.
Error Message%CRYPTO_HA_IPSEC-3-HA_IPSEC_UPDATE_PROC_FAIL : Start of HA IPSec update process failed
Explanation The IPSec HA process could not be started. Updates will not be sent from the active device to the standby device.
Recommended Action Reboot the system if this message was received while the IPSec HA component was being set up.
CSM Messages
The following are call switching module (CSM) messages.
Error Message%CSM-1-CAS_ALLOC_FAIL : Fail to add new signal channel [dec]/[dec] timeslot [dec]
Explanation The call switching module failed to allocate memory for the new CAS signaling channel that is specified in the error message. This condition might have been caused by either a low-memory condition or a software failure.
Recommended Action Check the minimum memory requirements for your system configuration. If a memory problem is suspected, reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If your system meets the minimum memory requirements, this message is most likely caused by a software failure. If the problem persists, copy the error message text exactly as it appears on the console or in the system log. Enter the show tech-support, show log, show process memory and show memory summary commands. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-5-CAS_IPC_QUEUED : CAS mbox at [hex] in use - message has been [chars].
Explanation A CAS IPC message has been queued because the mailbox is in use.
Recommended Action This is a notification message. If the modems are not functional or this message appears frequently, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-CAS_MSG_DEPLETED : An error was encountered in enqueuing a CAS message - [chars].
Explanation The modem may no longer be operational because the amount of memory available in the router may not be sufficient.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-CSM_BAD_EVENT : [chars]: [dec]/[dec] received invalid event [dec]
Explanation An invalid operation has been detected by the router.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-CSM_CALL_INFO_HWIDB_MISMATCH : csm_call_info hwidb mismatch
Explanation An internal error has occurred in CSM. The HWIDB is no longer pointing to this call.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-CSM_CALL_INFO_MISMATCH : csm_call_info contains
mismatch information call info has [chars]:[dec] framer gives [dec]/[dec]:[dec]Explanation An internal software error occurred while an outgoing call was being placed. A mismatch has occurred involving CSM call information. The call could not be updated with the new information. This condition could indicate a software error or an error due to existing network 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-CSM_MODEM_BAD : Modem [dec]/[dec] has been marked as bad by the router software.
Explanation The modem is no longer operational because of a run-time error.
Recommended Action The modem may become operational after the router is reset. If not, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-CSM_STRING_OVERRUN : String copy exceeded buffer size
Explanation The string written into the allocated buffer exceeded the size of the buffer. This error can cause memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-CSM_UNKNOWN_FAIL_CODE : Unknown fail code [dec]
Explanation The CSM attempted to process an unknown fail code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-DCHAN_ALLOC_FAIL : For channel [chars]
Explanation The CSM was unable to create the signaling interface for the channel specified in the error message. This error might have been caused by a low-memory condition or by a software failure.
Recommended Action Check the minimum memory requirements for your system configuration. If a memory problem is suspected, reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If your system meets the minimum memory requirements, this message is most likely caused by a software failure. If the problem persists, copy the error message text exactly as it appears on the console or in the system log. Enter the show tech-support, show log, show process memory and show memory summary commands. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-HWIDB : [chars]: hwidb is NULL
Explanation An invalid operation has been detected by the router.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-4-HWIDB_ALREADY_IN_USE : hwidb is already in use by another call
Explanation A call is already using this HWIDB. The new call is rejected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-HWIDB_SUBBLOCK : [chars]: hwidb subblock for b channel [dec] is in use
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-HWREV : The T1 or E1 network module is incompatible with the digital modems: [chars]
Explanation The T1 or E1 network module cannot be used with digital modems.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-INITFAIL : [chars]
Explanation The system was unable to create the periodic check process for the CSM during initialization of the CSM because of a low-memory condition. The router memory has been exhausted of memory, or the memory may be fragmented. This condition may be caused by the current system configuration, the network environment, or a software error.
Recommended Action Check the minimum memory requirements for your system configuration. If a memory problem is suspected, reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If your system meets the minimum memory requirements, this message is most likely caused by a software failure. If the problem persists, copy the error message text exactly as it appears on the console or in the system log. Enter the show tech-support, show log, show process memory and show memory summary commands. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-INITPORT : [chars] at slot [dec], port [dec]
Explanation An initialization error occurred on the specified port. The error message specifies more details.
Recommended Action Try resetting the port or power-cycling the system. If the error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-INITSYS : [chars]
Explanation The modem signaling module failed initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-5-MBRI : [chars] at slot [dec], unit [dec], with index [dec]
Explanation An ISDN MBRI interface has changed states. Details of the new state are shown in the error message.
Recommended Action No action is required.
Error Message%CSM-1-MODEM_INFO : [chars]: modem_info is NULL
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-NO_CHANNEL : [chars]
Explanation No signalling channels are available. All the channels have been allocated.
Recommended Action Wait for a channel to become available. If the modems are not functional or this message appears frequently, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-NO_CSM_CALL_INFO : No call control block
Explanation An internal software error has occurred. The call switching module could not allocate a modem for this call. A call record block that is associated with the call could not be found. This condition indicates either an inconsistent call state or an internal system error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-NO_HWIDB : No B channel associated with call
Explanation An internal software error has occurred. The call switching module could not process the call because the descriptor block associated with the controller was not found. This condition indicates either an inconsistent call state or an internal system error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-3-NO_VDEV : No modems associated:([chars]),Chan([dec]),Id([dec])
Explanation An internal software error has occurred. The call switching module could not complete a call connect operation because a call record block associated with the call was not found. This condition indicates either an inconsistent call state or an internal system error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-5-PRI : [chars] at slot [dec], unit [dec], channel [dec] with index [dec]
Explanation An ISDN PRI interface has changed states. Details of the new state are shown in the error message.
Recommended Action No action is required.
Error Message%CSM-1-QUEUE_ERROR : An error was encountered in enqueuing a [chars] ([dec]) for slot/port [dec]/[dec].
Explanation The modem may no longer be operational. The amount of memory available in the router may not be sufficient.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-1-RBS : [chars] at slot [dec], controller [dec], timeslot [dec]
Explanation An internal software error has occurred. An attempt was made to add a nonexistent CAS signaling interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CSM-3-TGRM_UPDATE_FAILURE : The trunk group resource manager failed to update channel status to [chars] for channel [chars]:[dec]:[dec]\n
Explanation The trunk group resource management subsystem reported an internal software error after a channel status update was sent to it by the CSM.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CSM-1-UNEXPECTEDEVENT : An Unexpected event received by tone process - [dec] [dec].
Explanation An invalid operation was detected by the router.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CSM_TGRM Messages
The following are CSM TGRM interaction messages.
Error Message%CSM_TGRM-3-UNEXPEVT : An Unexpected event was reported by the CSM-TGRM Interface service
Explanation The system has detected an internal software error. The interface service between the call-switching modules and the trunk group resource manager received an event that is invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CSM_TRUNK_MGR Messages
The following are Call Switching Manager (CSM) Trunk Manager messages.
Error Message%CSM_TRUNK_MGR-3-TRUNK_VALIDITY_FAILURE : [chars]
Explanation A trunk validity failure has occurred. This error usually indicates that memory is corrupted. But it can also indicate a problem with initialization or uninitialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CSM_VOICE Messages
The following are call switching mode (CSM) voice subsystem messages.
Error Message%CSM_VOICE-3-ADDINTRFFAIL : The Voice Telephony Service Provider has rejected our \nrequest to add this voice interface ([dec]/[dec]:[dec])
Explanation The voice software was unable to report a new signaling interface to the Voice Telephony Service Provider.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CSM_VOICE-3-MALLOC : No memory is available to build any internal data \n structure for the voice software.
Explanation The voice software was unable allocate memory to build any internal data structures. The system might be out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CSM_VOICE-3-NOMEM : No memory is available to build the voice interface ([dec]:[dec])
Explanation The voice software was unable allocate memory to build
a voice interface data structure. The system may be
out of memory.Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CSM_VOICE-3-NOSDB : No signaling data block is available to build the \n voice interface([dec]/[dec]:[dec])
Explanation The voice software was unable to obtain a signaling data block from the Voice Telephony Service Provider. The system might be out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CSM_VOICE-3-NOTDMCHNL : CSM failed to get a free dsp tdm channel from the DSP \n Resource Manager (DSPRM) to handle an incoming call
Explanation The voice software was unable to obtain the TDM channel for a free DSP from the DSP resource manager. All of the DSPs have been used to process calls or have been taken out of service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CSM_VOICE-3-NOVDEVINFO : CSM null voice resource info
Explanation An internal software error has occurred. There were no free voice resources available to make an outgoing voice call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CSM_VOICE-3-TDMHPMADDFAIL : CSM failed to add the CAS TDM hairpinning call
Explanation The CSM voice software interface was unable to add this call as a hairpinned call because another call was present for the same DS0. This condition indicates an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CSM_VOICE-3-UNDEFDSX0 : Undefined dsx0 interface for controller([dec]/[dec])
Explanation The dsx0 interface for the specified controller is not defined, but the voice software has used the interface. An internal software fault has occurred.
Recommended Action Contact your field service representative if this message is coincident with dropped calls.
Error Message%CSM_VOICE-3-UNDEFVOICEINTRF : Invalid interface slot:controller:group([dec]/[dec]:[dec])
Explanation The voice interface defined by slot:controller:group is not yet defined within the voice software, but attempts were made to use this interface. An internal software fault has occurred.
Recommended Action Contact your field service representative if this message is coincident with dropped calls.
CT3 Messages
The following are channelized T3 (CT3) port adapter messages.
Error Message%CT3-3-BADMSG : Received unexpected mailbox message (id = [dec])
Explanation An unexpected message has been received from the CT3 firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-CONFIGURE : Failed to configure [dec] interfaces in bay [dec], shutting down bay
Explanation The CT3 hardware has failed. Some components on the board failed to initialize.
Recommended Action Replace the CT3 port adapter.
Error Message%CT3-2-CT3FWCRASHED : CT3 F/W crashed in bay [dec]: [hex] - reset
Explanation The CT3 firmware does not update the software watchdog.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-2-CT3FWCRASHEDINFO : [hex] [hex] [hex] [hex]
Explanation This error message contains CT3 firmware failure information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-CT3NOACC : [chars] - Accumulator is not available
Explanation An invalid Tx accumulator was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-DISCOVER : Found [dec] interfaces in bay [dec], shutting down bay
Explanation The CT3 hardware has failed. Some components on the board failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-DWNLDFAIL : Microcode to slot [dec]
Explanation The firmware download into the CT3 port adapter failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-ERROR : [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-INITFAIL : Slot [dec] firmware init ([chars])
Explanation Initialization of the CT3 firmware has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-INITFAILP : [chars] init failed at [chars]
Explanation Initialization of the CT3 firmware has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-LOVEFAIL : [chars]: failed to send [chars] love letter
Explanation An expected message was not sent to the RSP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-MBOXRECV : Failed to receive reply [dec] from bay [dec] firmware
Explanation An expected message was not received from CT3 firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-MBOXSEND : Failed to send msg [dec] to bay [dec] firmware
Explanation The specified message was not sent to the CT3 firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-MBOXSENDM : Failed to send msg [chars] to bay [dec] firmware
Explanation The specified message was not sent to the CT3 firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-MBOXSENDP : Failed to send msg [dec] to [chars] driver firmware
Explanation A port-related message was not sent to CT3 firmware.
Recommended Action Copy the error message exactly as it appears, issue the show tech-support command, contact your Cisco technical support representative, and provide the representative with the gathered information. If possible perform an online insertion and removal. Refer to the Cisco documentation for information on how to perform an online insertion and removal for your platform.
Error Message%CT3-3-NOTMXT : Slot [dec] device ID seen as [hex], expected [hex] (Mueslix)
Explanation The HDLC controller was not detected on the CT3.
Recommended Action Replace the CT3 port adapter.
Error Message%CT3-3-NOTPLX : Slot [dec] device ID seen as [hex], expected [hex] (PLX9060)
Explanation The PLX 9060 was not detected on the CT3.
Recommended Action Replace the CT3 port adapter.
Error Message%CT3-1-NOTREADY : Slot [dec] for microcode download
Explanation An error has been detected on the communication path between the VIP and the CT3 hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-2-NOVC : [chars]: packet received for unknown VC [dec]
Explanation The virtual channel encapsulation has been corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-3-OWNERR : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The CT3 driver has detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-RESTARTFAIL : [chars] could not be reset by [chars]
Explanation The restart has failed to reset the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-STARTFAIL : [chars] could not be enabled by [chars]
Explanation The restart has failed to enable the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-STOPFAIL : [chars] could not be disabled by [chars]
Explanation The shutdown has failed to disable the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CT3-1-UNSUPPORTED : [chars]
Explanation A CT3 port adapter with a revision earlier than Revision 3 has been detected. This port adapter predates the router platform in which it has been installed. The combination is not supported.
Recommended Action Upgrade to a CT3 port adapter that is Revision 3 or higher.
CTA Messages
The following are CMCC Channel Interface Processor (CIP) messages for the channel transport architecture device task/mapper.
Error Message%CTA-6-BADCHAIN : PA[dec] CTA [hex]-[hex] Too many buffers in a CSNA write chain.
Explanation All the data sent in a CSNA write chain should fit in one transfer list element. The data sent in the CSNA required more than one.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-ERRSTASH : PA[dec] CTA [hex]-[hex] buffer [hex] not in stash, pc: [hex]
Explanation An error has been detected in the processing of host-bound messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-ERRSTATE1 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]
Explanation A sequence error has occurred. A host write was received when the subchannel setup was in a "pending open" state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-ERRSTATE2 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]
Explanation A sequence error has occurred. A host write was received when the subchannel setup was in a "pending open" state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-ERRSTATE3 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]
Explanation A sequence error has occurred. A host write was received when the subchannel setup was in a "pending open" state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-ERRSTATE4 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]
Explanation A sequence error has occurred. A host write was received when the subchannel setup was in a "setup complete" state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-FLUSH : PA[dec] CTA [hex]-[hex] Read data flushed.
Explanation Because of an error on the channel, some data that was intended to be sent to the channel was not sent to the channel. The VTAM will receive an error indication and the VTAM should retry the operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-INACT_ATTN_STATE : Attention FSM state: [chars]
Explanation This message indicates the state of the FSM. This message is associated with the previous INACTIVE message. An error involving the FSM has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-INACT_FLOW_COUNTS : Flow stop/resume [int]/[int]
Explanation This message indicates the total count of "flow stop" and "flow resume" frames that were passed by CTA to the host. This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-INACT_FLOW_QUEUED : Flow Resume queued in CTA: [int]
Explanation This message indicates the number of "flow resume" messages that were queued to the host in the CTA. This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-INACT_FREEMEM : Free Memory: [hex]
Explanation This message indicates the current amount of free memory. This message is associated with the previous INACTIVE message.
Recommended Action No action is required.
Error Message%CTA-0-INACTIVE : PA[dec] CTA [hex]-[hex] reset after being inactive for [dec] seconds
Explanation The specified subchannel has been inactive for more than the subchannel timeout interval. Either the host has been halted or the VTAM has been terminated by a z net cancel command.
Recommended Action Restart the VTAM HOST and activate the XCA major node.
Error Message%CTA-6-INACT_SCBS : SCBs in SLC: [dec]
Explanation This message indicates the number of SCBs that are queued in the SLC. It is associated with the previous INACTIVE message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-INACT_SLOWDOWN : Slowdown [chars]: [chars], [int] ms
Explanation This message indicates the slowdown state and duration. This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-INIT : PA[dec] CTA [hex]-[hex] Device initialized
Explanation A CSNA device has been initialized. The device string is in the form CSNA x/yyyy/zz, where x is the daughterboard number, yyyy is the path, and zz is the device number.
Recommended Action No action is required.
Error Message%CTA-6-LONGREC : PA[dec] CTA [hex]-[hex] Attempt to transmit too large a record.
Explanation The amount of data being read by the channel has exceeded the size of the read CCW.
Recommended Action If this message occurs with CSNA and the MAXPIU variable is set to less than 4500, then increase the MAXPIU value. Otherwise, report this error to your Cisco technical support representative.
Error Message%CTA-0-MSGERR1 : PA[dec] CTA [hex]-[hex] mismatch between channel block size and msg counts
Explanation An error involving a mismatch between the channel block size and the message counts has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-MSGERR2 : PA[dec] CTA [hex]-[hex] msg size less than DLC hdr size
Explanation The host has sent an invalid message. The message size is less than the DLC header size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-MSGERR3 : PA[dec] CTA [hex]-[hex] Received CTA command not recognized
Explanation A CTA command code has been received that is not in the valid range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-NOMEM : CTA attempt to acquire memory failed, pc: [hex]
Explanation An attempt by the CTA to create a pool or allocate a buffer has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-QUEUE_ERROR : PA[dec] CTA [hex]-[hex] attempt to init or alloc a queue failed at [hex]
Explanation An attempt by the CTA to initialize or allocate a queue has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-6-SHUTDOWN : PA[dec] CTA [hex]-[hex] Device shutdown
Explanation A CSNA device has been shut down. The device string is in the form CTAn/mmmm/yy, where n is the daughterboard number, mmmm is the path, and yy is the device number.
Recommended Action No action is required.
Error Message%CTA-0-SYSMGT_ERROR1 : CTA detected error in sysmgt call: invalid CSNA DEVICE length
Explanation An invalid parameter has been received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-SYSMGT_ERROR2 : CTA detected error in sysmgt call: invalid LLC2 CONN length
Explanation An invalid parameter has been received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-SYSMGT_ERROR3 : CTA detected error in sysmgt call: invalid CSNA type
Explanation An invalid parameter has been received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-UNEXP_ATTN_EVENT : PA[dec] CTA [hex]-[hex] unexpected event [int] in attn state [int], setup state [int]
Explanation An unrecognized event has been received by the CTA attention FSM. The receipt of the unrecognized event is an unrecoverable situation. This instance of CTA is initialized, and the CMPC TG node must be cycled to resume operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-UNEXP_EVENT : PA[dec] CTA [hex]-[hex] received unrecognized type code [hex] at [hex]
Explanation A transfer element type code not in the valid range has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-UNEXP_LSI_CMD : PA[dec] CTA [hex]-[hex] received LSI command [hex] at [hex]
Explanation An LSI command code not in the valid range has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CTA-0-UNEXP_LSI_STATUS : CTA received status [hex] in LSI cmd [hex]
Explanation An LSI status code not valid for the command has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CTLPROVIDERSERV Messages
The following are CTL provider service messages.
Error Message%CTLPROVIDERSERV-3-NOINIT : Can't initialize CTLProvider server
Explanation Ports could not be initialized for the CTL provider server because of an internal error.
Recommended Action Ensure that the CTL provider server port is available on the local machine.
Error Message%CTLPROVIDERSERV-3-NOMEM : Can't initialize memory for CTLProvider server
Explanation Sufficient memory could not be allocated for the CTL provider server.
Recommended Action Increase the amount of available memory for the CTL provider server.
Error Message%CTLPROVIDERSERV-3-NOPROC : Could not start CTLProvider Server
Explanation A process could not be created for the CTL provider server.
Recommended Action No action is required.
Error Message%CTLPROVIDERSERV-3-NOSOCKETS : Max Number of CTLProvider Server sockets exceeded
Explanation Too many CTL provider clients are requesting service.
Recommended Action Reduce the number of CTL provider clients that are requesting service.
CTRC Messages
The following are Cisco Transaction Connection (CTRC) messages.
Error Message%CTRC-3-APPCERROR : [chars]
Explanation An APPC error has occurred. CTRC uses APPC API calls to SNASw to communicate with the remote database server.
Recommended Action This error usually indicates a problem in the SNA network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server using the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug ctrc appc command and an SNA line trace between the router and the remote database server for the period during which this message appeared.
Error Message%CTRC-3-APPCVERB : Unexpected APPC error: opcode [hex], primary code [hex], secondary code [hex]
Explanation An unexpected APPC error has occurred. The CTRC uses APPC API calls to SNASw to communicate with the remote database server. The opcode identifies the APPC API call that received the error. Primary and secondary return codes are returned by the APPC API.
Recommended Action This error usually indicates a problem in the SNA network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server using the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug ctrc appc command and an SNA line trace between the router and the remote database server for the period during which this message appeared.
Error Message%CTRC-4-APPCWARN : [chars]
Explanation An APPC error has occurred. The CTRC uses APPC API calls to SNASw to communicate with the remote database server.
Recommended Action This error usually indicates a temporary problem in the SNA network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server using the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug ctrc appc command and an SNA line trace between the router and the remote database server for the period during which this message appeared.
Error Message%CTRC-3-NOBUFFS : No buffers available to [chars]
Explanation The CTRC attempted to allocate a buffer while performing the operation described in the message text. The buffer pool does not contain enough items to satisfy the allocation request.
Recommended Action This problem most commonly occurs whenever a public buffer pool runs out of elements. To determine which pool has run out of buffers, use the show buffers command. To adjust the pool size, use the buffers configuration command.
Error Message%CTRC-3-SNASWNOTSTARTED : SNASW is not started -- unable to connect to remote database.
Explanation A client has connected to a CTRC server, but the CTRC was unable to connect out to the remote database because SNASw has not been started. The CTRC uses SNASw to connect to the remote database server. You must start SNASW before CTRC clients attempt to connect.
Recommended Action Start SNASw, and retry the client connection.
Error Message%CTRC-3-SNASWSTOPPED : SNASW was stopped -- existing connections have been closed.
Explanation SNASw was stopped while CTRC connections were open. Stopping SNASw caused all open SNA network connections to the remote database server to be lost. As a result, all client connections were disconnected. You should not stop SNASw while there are open CTRC connections.
Recommended Action Restart SNASw. Disconnected clients must reconnect.
CWAN_ATM Messages
The following are Constellation WAN ATM messages.
Error Message%CWAN_ATM-3-BADMAC : Broadcast MAC on [chars] subnet
Explanation A packet with an unexpected MAC address from the backplane has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_ATM-3-MCAST_VC_ERR : Multiple IP Multicast addrs assigned to VC [hex]
Explanation An attempt was made to use a multicast MPT virtual circuit that was already in use and had been assigned to another multicast group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_ATM-3-NONDATAVC : Ethernet data frame received on non-data VC
Explanation A data packet for a control virtual circuit has been received from the backplane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CWAN_RP Messages
The following are Constellation WAN ATM route processor driver messages.
Error Message%CWAN_RP-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation A line card has forwarded a message that the Draco software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-BOOTFAIL : The CWAN-LC in slot [int]/[int] failed to boot
Explanation The line card that was booting either has reset or has failed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-6-CARDRELOAD : Card reloaded on slot [int]/[int]
Explanation A Find Master SCP message has been recovered on the RP. The line card was either inserted or reset from the NMP. The inserted interface shuts down until it is configured by the user or, if an interface of the same type was previously configured, it is restored to its previous state.
Recommended Action No action is required.
Error Message%CWAN_RP-3-ERROR : NULL
Explanation A software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-FOREVER : cmd [int] to [chars] (slot [int]/[int]) took [int] usecs, done [hex]
Explanation A CCB command from Draco to a line card took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-HV_ALLOCFAIL : Draco failed to allocate a VLAN for a WAN interface, status=[int]
Explanation The NMP has returned a failure for the VLAN allocation request.
Recommended Action If the error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-6-IMAGE_UPGRADE : Bootflash image upgrade [chars] for slot [int]/[int][chars]
Explanation The bootflash image on the CWAN line card has been automatically upgraded.
Recommended Action No action is required.
Error Message%CWAN_RP-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The Draco software has failed to allocate a buffer for communication with a line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars]
Explanation The Draco software has failed to open a port for communication with a line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The Draco software has failed to send a message to a line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-KEEPFAIL : The CWAN-LC in slot [int]/[int] is not responding to keepalives
Explanation The line card either has been reset or has failed.
Recommended Action If the error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-LC_CRASHINFO : The CWAN_LC in slot [int]/[int] copied [chars] on to RP bootflash
Explanation The line card has failed.
Recommended Action If the error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-6-LC_PRESENT : [chars] in slot [int]
Explanation A CWAN line card has been detected by the hardware.
Recommended Action No action is required.
Error Message%CWAN_RP-3-LCLOG_BADSEV : Linecard [int]/[int] invalid message severity [int]
Explanation The line card has forwarded a logger message that has an invalid severity code. The MSFC Route Processor cannot process the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-4-LCLOG_TOOLONG : Linecard [int]/[int] message too long, [int] bytes
Explanation The line card has forwarded a logger message that is too long for the MSFC Route Processor to process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-6-QUIESCE_FAIL : Quiesce failed for slot [int]/[int]
Explanation The Draco software has failed to contact the CWAN line card during the specified failover, and the line card is reset.
Recommended Action No action is required.
Error Message%CWAN_RP-3-RESET_FAIL : The CWAN-LC in slot [int] failed even after several resets
Explanation The line card has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-SCPALLOCFAIL : Failed to allocate SCP packet [chars]
Explanation The Draco software has failed to allocate a packet for communication with other slots in the chassis.
Recommended Action If the error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CWANLC Messages
The following are Constellation WAN line card messages.
Error Message%CWANLC-4-BUSSTALL : Constellation BUS Stall detected
Explanation A stall has been detected on the Constellation bus. The stall might have been caused by some OIR activity on the bus.
Recommended Action No action is required.
Error Message%CWANLC-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The line card has failed to allocate a buffer for communication with the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars]
Explanation The line card has failed to open a port for communication with the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The line card has failed to send a message to the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-4-LOGMSGTOOBIG : Logger message length exceeds max, [int] bytes
Explanation The line card has attempted to send a message that exceeded the maximum allowed length to the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-3-LONGSTALL : Long bus stall ([int] ms), check for improperly seated cards
Explanation A stall has been detected, and the backplane stall was longer than expected.
Recommended Action Ensure that all cards are firmly seated. A recurring problem may indicate a hardware failure.
Error Message%CWANLC-2-PCIERROR : Fatal PCI Error [chars] seen on PCI Bus [dec]
Explanation A fatal PCI error has been detected on the PCI bus. This PCI error is probably caused by a hardware problem.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CWANLC_ATM Messages
The following are Constellation WAN ATM route processor driver messages.
Error Message%CWANLC_ATM-3-CMDERR : ([dec]/[dec]) Interface ([chars]): [chars] IPC command fails (cause: [hex])
Explanation The ATM RP driver has experienced an IPC command error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-3-EVENT : ([dec]/[dec]) Interface ([chars]): unknown IPC event ([int]) from linecard
Explanation The ATM RP driver has received an unknown event from the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-4-HIRATE : ([dec]/[dec]) Interface ([chars]): SAR limits VBR VC PCR to [dec] kbps, opening UBR VC instead
Explanation The SAR limits the VBR VC PCR to one-half the bandwidth of the link.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-3-INIT : ATM driver ([int]/[int]) initialization [chars].
Explanation The ATM RP driver has experienced a software initialization error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-4-UNSUP : ([dec]/[dec]) Interface ([chars]): unsupported feature: [chars]
Explanation The specified feature is not supported by the ATM RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-3-VCENCTYPE : ([dec]/[dec]) VC:[int] unknown VC encapsulation type ([int])
Explanation The ATM RP driver has experienced an unknown VC encapsulation software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CWPA Messages
The following are Route Processor for Constellation Supervisor router module messages.
Error Message%CWPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The MSFC Route Processor has forwarded a message that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-BADMALUCMD : Unsupported MALU command [dec], arg=[hex], pascb=[hex]
Explanation The MSFC Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-BADMALUCMD2 : CWPA([int]): Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex], pascb=[hex]
Explanation The MSFC Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-CMDNOPASCB : PASCB Null for command [dec], arg=[hex]
Explanation The MSFC Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The line card has failed to allocate a buffer for communication with the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The line card has failed to send a message to the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-LVLTRTOOBIG : Loveletter length exceeds max, [int] bytes
Explanation The line card has attempted to send a message that exceeded the maximum allowed length to the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation No command dispatch vector has been found for the specified interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CWRMP Messages
The following are radio point-to-multipoint driver messages.
Error Message%CWRMP-3-AUTO_CABLECOMP_FAIL : Radio[dec]/[dec]: [chars]
Explanation An autocable compensation failure has occurred.
Recommended Action Check the RF ODU cabling or connection.
Error Message%CWRMP-1-BUNDLE : Error creating bundled microcode file [chars]/[chars] ([chars])
Explanation An internal error has occurred while the system was creating the microcode file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWRMP-5-CLEAR_METRICS : Radio[dec]/0, [chars] link-metrics cleared
Explanation The user has requested that the link-metrics be cleared.
Recommended Action No action is required.
Error Message%CWRMP-5-CONFIG_HW : Radio[dec]/0, hardware does not support requested configuration: [chars]
Explanation The hardware does not support the requested software configuration. The most likely cause of this error is an incorrect configuration.
Recommended Action Change the configuration to match the hardware.
Error Message Change the configuration to match the hardware.%CWRMP-5-CONFIG_MISMAT : Radio[dec]/0, invalid or inconsistent configuration requested: [chars]
Explanation An inconsistent parameters setting was requested.
Recommended Action Check your configuration for inconsistencies.
Error Message%CWRMP-1-CRPAS : [chars] [dec]/[dec]: Error creating microcode file [chars]/[chars] ([chars])
Explanation An internal error occurred while creating the microcode file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWRMP-1-DIRERR : [chars] [dec]/[dec]: Error reading microcode directory [chars] ([dec])
Explanation An internal error has occurred while reading the microcode directory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWRMP-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation An internal hardware or software failure has occurred.
Recommended Action Replace the line card.
Error Message%CWRMP-4-DUPLXR_INFO_MISSING : Radio[dec]/[dec]: ODU[dec] Duplexor Info is not set
Explanation The ODU duplexer information is missing.
Recommended Action Issue the radio interface radio slot/port rf-update-duplexor command.
Error Message%CWRMP-4-FREQ_OUT_OF_DUPLXR_RANGE : Radio[dec]/[dec]: Input [chars] freq ([dec] Khz) is outside of ODU[dec]'s duplexor freq range ([dec] - [dec] Khz)
Explanation The indicated frequency is out of the ODU duplexer range.
Recommended Action Verify the frequency range of the ODU duplexer.
Error Message%CWRMP-1-GENERIC : [chars]: [chars]
Explanation An internal software failure has occurred.
Recommended Action Reload the router.
Error Message%CWRMP-3-HE_LOOPBACK_FAIL : Radio[dec]/[dec]: Loopback signal failed to produce desirable signal levels
Explanation FIR slips did not produce a valid SNR measurement.
Recommended Action Isolate the defective hardware by performing all loopback modes.
Error Message%CWRMP-4-HOST_COMM : Radio[dec]/[dec], HOST-to-IF comm error ([chars])
Explanation A communication error has occurred between the host and the IF board. A likely cause is a loose IF board.
Recommended Action Check or replace the IF board.
Error Message%CWRMP-5-IF_NVS_CACHED : Radio[dec]/[dec]: IF NVS content cached into IOS memory
Explanation The IF NVS content has been cached into Cisco IOS memory.
Recommended Action No action is required.
Error Message%CWRMP-3-IF_NVS_CACHE_FAIL : Radio[dec]/[dec]: IF NVS content cache failed due to NVS read error
Explanation The IF NVS content cache has failed because of an NVS read error.
Recommended Action Check the IF HW or IF PIC/NVS version.
Error MessageExplanation A hardware error has occurred. The most likely cause of this error is vibration or hardware failure.
Recommended Action Check or replace the internal card.
Error Message%CWRMP-3-IF_PIC_IMAGE_FAIL : Radio[dec]/[dec]: [chars]
Explanation An error has occurred with the IF PIC image.
Recommended Action Verify the compatibility of the IF PIC image.
Error Message%CWRMP-4-IF_POWER_SUPPLY : Radio[dec]/[dec], IF [chars] power supply warning [dec] V
Explanation A hardware error has occurred. The power supply is showing an invalid voltage. The most likely cause is a failure of the internal card.
Recommended Action Check or replace the internal card.
Error Message%CWRMP-5-IF_SU_LOOPBACK : Radio[dec]/[dec], Make sure external IF loopback fixture is attached
Explanation The IF loopback requires an external loopback fixture instead of a standard ODU.
Recommended Action Attach an external loopback fixture.
Error Message%CWRMP-5-IF_UCODE_UPGRADE : Radio[dec]/[dec], IDU PIC changed from version [dec].[dec].[dec] to [dec].[dec].[dec]
Explanation A newer version of IDU PIC was found on the microcode, bundled, and downloaded to the IDU.
Recommended Action No action is required.
Error Message%CWRMP-0-INITFAIL : Radio[dec]/[dec], RSM Init failed, [chars]
Explanation The RSM initialization has failed, most likely because of a hardware failure of the line card.
Recommended Action Replace the defective line card.
Error Message%CWRMP-1-LBCERR : [chars]: Internal Local-Bus timeout on linecard at [hex]
Explanation The internal local bus has timed out on the line card, most likely because of an internal hardware failure of the line card.
Recommended Action Replace the line card if this error recurs frequently.
Error Message%CWRMP-5-LOOPBACK_UP : Hardware on Radio[dec]/[dec] configured for loopback, performance needs to be verified
Explanation The hardware is in loopback mode, but the loopback performance must be validated.
Recommended Action No action is required.
Error Message%CWRMP-1-MEMCMP : mismatch at [chars]:[hex], xor [hex]
Explanation An internal hardware failure has occurred, most likely because of a failure of the line card.
Recommended Action Replace the line card.
Error Message%CWRMP-5-METRICS_THRESH_HE_CH : Radio[dec]/0, Channel([dec]) per hour threshold met([int].[intUnrecognized format `]% '>= [int].[intUnrecognized format `]% ')
Explanation The signal quality is poor.
Recommended Action Refer to the installation and maintenance guide.
Error Message%CWRMP-5-METRICS_THRESH_HE_SU_CLEAR : Radio[dec]/0/U[dec], Subscriber([enet]) per hour threshold clear([int].[intUnrecognized format `]% '<=[int].[intUnrecognized format `]% ')
Explanation The signal quality has recovered.
Recommended Action Refer to the installation and maintenance guide.
Error Message%CWRMP-5-METRICS_THRESH_HE_SU_SET : Radio[dec]/0/U[dec], Subscriber([enet]) per hour threshold met([int].[intUnrecognized format `]% '>=[int].[intUnrecognized format `]% ')
Explanation The signal quality is poor.
Recommended Action Refer to the installation and maintenance guide.
Error Message%CWRMP-5-METRICS_THRESH_SU : Radio[dec]/0, [chars] per hour threshold met([dec]>=[dec])
Explanation The signal quality is poor.
Recommended Action Refer to the installation and maintenance guide.
Error Message%CWRMP-1-NOFS : Cannot find filesystem '[chars]'
Explanation An internal error has occurred while reading the file system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWRMP-1-NOSRC : [chars] [dec]/[dec]: Cannot read microcode directory [chars]
Explanation The microcode directory is not accessible.
Recommended Action Check the configuration and verify that there is network connectivity to the TFTP server.
Error Message%CWRMP-3-NOTCWRMP : Device reported [hex]
Explanation An internal hardware error has occurred.
Recommended Action Replace the defective hardware.
Error Message%CWRMP-1-NOTRADIO : Invalid PCI identifier [hex] in PA [dec]
Explanation A system or hardware failure has occurred, most likely because of a failure of the line card.
Recommended Action Replace the line card.
Error Message%CWRMP-4-NVS_UPGRADE_REQUIRED : Radio[dec]/[dec]: [chars] NVS upgrade or re-calibration may be required
Explanation The NVS content is out of date.
Recommended Action Update or recalibrate the NVS content.
Error Message%CWRMP-1-ODU_BAD_PIC_IMG : ODU[dec] PIC image is invalid. Require manual copy to recover.
Explanation The PIC image has failed to update automatically.
Recommended Action Manually copy in the appropriate image.
Error Message%CWRMP-4-RFIF_ODU_FAILOVER : Radio[dec]/[dec], Possible problem with primary transmitter, switching to secondary transmitter
Explanation An error condition has caused one ODU to stop transmitting. The system is switching to the other ODU for subsequent transmissions.
Recommended Action Check the ODU and repair it if necessary.
Error Message%CWRMP-4-RFIF_ODU_SU_OFFLINE : Radio[dec]/[dec], Too many subscribers are offline, possible problem with main transmitter
Explanation Too many subscribers went off-line in a short interval of time. The main transmitter may not be functioning properly.
Recommended Action Check the ODU and repair it if necessary. Check or replace the cable from the UBR to the RF ODU.
Error Message%CWRMP-4-RFIF_UNEXP_RESET : Radio[dec]/[dec], [chars] unexpected reset: [chars]
Explanation An unexpected reset has occurred. The most likely cause is loose cabling or a DC power disruption.
Recommended Action Check the cabling and, if necessary, the DC power supply.
Error Message%CWRMP-5-RF_NVS_CACHED : Radio[dec]/[dec]: RF/ODU[dec] NVS content cached into IOS memory
Explanation The ODU NVS content has been cached into Cisco IOS memory.
Recommended Action No action is required.
Error Message%CWRMP-3-RF_NVS_CACHE_FAIL : Radio[dec]/[dec]: RF/ODU[dec] NVS content cache failed due to NVS read error
Explanation The ODU NVS content has failed to be cached into IOS memory due to an NVS read error.
Recommended Action Check the ODU connection or verify that the ODU PIC or NVS version.
Error Message%CWRMP-3-RF_NVS_CHECKSUM_FAIL : Radio[dec]/[dec]: RF/ODU[dec] NVS [chars] checksum failed (Checksum=[hex])
Explanation Verification of the ODU NVS checksum has failed.
Recommended Action Return the ODU to the vendor for calibration.
Error Message%CWRMP-4-RF_ONOFF_LINE : Radio[dec]/[dec], IF-to-RF/ODU[dec] comm link status changed - [chars]
Explanation A hardware error has occurred, most likely because of a disconnected or loose cable.
Recommended Action Check or replace the cable from the UBR to the RF ODU.
Error Message%CWRMP-4-RF_OSC : Radio[dec]/[dec], RF/ODU[dec] [chars]
Explanation A hardware error has occurred. The most likely cause of this error is vibration or a hardware failure.
Recommended Action Replace the electronics on the ODU.
Error Message%CWRMP-2-RF_OVERTEMP : Radio[dec]/[dec], RF/ODU[dec] temperature ([dec] deg C) reached [chars] level
Explanation The temperature of the RF ODU has reached a high level. The most likely cause of this error is either a hardware failure or solar overheating of the ODU.
Recommended Action Keep the RF ODU cool.
Error Message%CWRMP-3-RF_PIC_IMAGE_FAIL : Radio[dec]/[dec]: [chars]
Explanation An error with the image of the RF ODU PIC has occurred.
Recommended Action Verify the compatibility of the RF ODU PIC image.
Error Message%CWRMP-4-RF_POWER_SUPPLY : Radio[dec]/[dec], RF/ODU[dec] supply voltage out of range
Explanation A hardware error has occurred. The power supply voltage is not within the acceptable range, most likely because of a failure of the RF ODU.
Recommended Action Replace the RF ODU.
Error Message%CWRMP-4-RF_TEMP : Radio[dec]/[dec], RF/ODU[dec] temperature is [dec] deg C, threshold is [dec] deg C
Explanation The temperature of the RF ODU has reached a level above its threshold level. The most likely cause of this error is either a hardware failure or solar overheating of the RF ODU.
Recommended Action Ensure that the RF ODU does not go above its threshold temperature.
Error Message%CWRMP-4-RF_TX_POWER : Radio[dec]/[dec], RF/ODU[dec] transmit power ([dec] dbm) reached [chars] level
Explanation A hardware error has occurred. The transmitting power has reached an unacceptable level.
Recommended Action Replace the RF ODU.
Error Message%CWRMP-5-RF_UCODE_UPGRADE : Radio[dec]/[dec], ODU[dec] PIC changed from version [dec].[dec].[dec] to [dec].[dec].[dec]
Explanation A newer version of the ODU PIC was found on Flash memory and was downloaded to the ODU.
Recommended Action No action is required.
Error Message%CWRMP-4-RX_GAINCAL_ERROR : Radio[dec]/[dec]: [chars]
Explanation An Rx gain calibration error has occurred.
Recommended Action Update the ODU NVS related to the Rx gain calibration.
Error Message%CWRMP-5-STATS_PRINT : Radio[dec]/0, statistics display error
Explanation Statistics cannot be displayed because the statistics were being generated faster than they could be printed.
Recommended Action Refer to the installation and maintenance guide.
Error Message%CWRMP-5-THRESHOLD : Radio[dec]/0, [chars] [chars] [dec] threshold crossed
Explanation A threshold has been crossed. The threshold that has been crossed is most likely userdefined.
Recommended Action No action is required.
Error Message%CWRMP-5-UCODE : [chars] [dec]/[dec]: Loaded [chars]
Explanation Microcode was loaded into the port adapter.
Recommended Action No action is required.
Error Message%CWRMP-3-UCODEFAIL : [chars] [dec]/[dec]: Loading [chars] failed
Explanation A microcode file has failed to load into the wireless port adapter.
Recommended Action Verify that the source file that is to be loaded exists and is accessible.
Error Message%CWRMP-5-UCODEPOST : [chars] [dec]/[dec]: Self test executed successfully
Explanation The power-on self-test did not find any errors.
Recommended Action No action is required.
Error Message%CWRMP-5-UPDOWN : Interface [chars] Port U[dec], changed state to [chars]
Explanation The upstream port was brought up or down.
Recommended Action No action is required.
CWRSU Messages
The following are wireless radio point-to-multipoint subscriber unit (SU) messages.
Error Message%CWRSU-4-CLIDISABLED : All Radio QOS flows and classifier's in the running config will be ignor \ned
Explanation Any DOCSIS QoS flow and classifiers added via the CLI will not take effect on the radio interface.
Recommended Action Change the DOCSIS configuration file to permit DOCSIS QoS commands to enter via the CLI.
Error Message%CWRSU-4-ENFLOWFAIL : Could not enable CLI Docsis qos flow [dec] on radio interface
Explanation The DOCSIS QoS flow added via the CLI was not enabled because it is not allowed in the DOCSIS configuration file.
Recommended Action Define the flow in the DOCSIS configuration file or change permission in the DOCSIS configuration file to permit DOCSIS QoS CLI commands.
Error Message%CWRSU-3-INTSOFTEV : Internal software event
Explanation The CWRSU OQS resource manager subsystem detected an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWRSU-4-NODOCFLOW : DOCSIS 1.0 class of service does not exist for class-id [dec]
Explanation The DOCSIS 1.0 CoS referenced by the class ID was not defined in the DOCSIS configuration file.
Recommended Action Define the DOCSIS 1.0 CoS in the DOCSIS configuration file.
Error Message%CWRSU-3-NOMEMORY : No memory available to build data structure
Explanation There is not enough memory in the system to complete this request.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CWRSU-4-NOPOLICYMAP : Policy map name [chars] not configured for DOCSIS qos flow [dec]
Explanation The policy map name defined for the DOCSIS QoS flow is not configured in the Cisco IOS configuration. Queueing for this flow defaults to first-come-first-serve.
Recommended Action Define the policy map in the Cisco IOS configuration.
CWRTEST Messages
The following are wireless radio point-to-multipoint test driver messages.
Error Message%CWRTEST-1-GENERIC : [chars]: [chars]
Explanation An internal software failure has occurred.
Recommended Action Reload the router.
Error Message%CWRTEST-1-MEMCMP : mismatch at [chars]:[hex], xor [hex]
Explanation An internal failure has occurred.
Recommended Action Replace the line card.
CWTLC Messages
The following are Constellation Supervisor router module line card messages.
Error Message%CWTLC-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The MSFC Route Processor has forwarded a message that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADINT : Attempted to access HWIDB for port [int]
Explanation The line card has attempted to access an HWIDB value that is associated with a port that does not exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADINTCREATE : Attempted to install HWIDB for port [int]
Explanation The line card has failed to install an HWIDB value because the associated port number was out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADMALUCMD : Unsupported MALU command [dec], arg=[hex], pascb=[hex]
Explanation The MSFC Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADMALUCMD2 : Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex], hwidb=[chars]
Explanation The MSFC Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-CMDNOINT : HWIDB Null for command [dec], arg=[hex]
Explanation The MSFC Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The line card has failed to allocate a buffer for communication with the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The line card has failed to send a message to the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-LVLTRTOOBIG : Loveletter length exceeds max, [int] bytes
Explanation The line card has attempted to send a message that exceeds the maximum allowed length to the MSFC Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation No command dispatch vector has been found for the specified interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-VAERROR : Error on Van Allen [dec]
Explanation An error has been detected on one of the Constellation Switching Bus ASICs that are located on the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-2-VAFATAL : Fatal Error on Van Allen [dec]
Explanation A fatal error has been detected on one of the Constellation Switching Bus ASICs.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CWTLC_ATM Messages
The following are ATM line card for Constellation Supervisor router module messages.
Error Message%CWTLC_ATM-3-CMD_ACK : ATM (port [dec]): Cmd ack problem: [chars]
Explanation An error has occurred during an attempted communication with SAR.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
DAS_ENV Messages
The following are RSC environmental monitor subsystem messages.
Error Message%DAS_ENV-2-AC_STATUS_CRITICAL : [chars], MBUS at Power Module 24 detects AC status = [hex] MBUS at Power Module 25 detects AC status = [hex]
Explanation The parameters specified for the AC shelves are outside the normal range of operation.
Recommended Action Check the status of the AC shelf and the ambient room temperature.
Error Message%DAS_ENV-1-AC_STATUS_WARNING : [chars], MBUS at Power Module 24 detects AC status = [hex] MBUS at Power Module 25 detects AC status = [hex]
Explanation The specified environmental parameters of the AC shelves are outside the normal range of operation.
Recommended Action Check the status of the AC shelf.
Error Message%DAS_ENV-2-BKPLN_STATUS_CRITICAL : Backplane Switches are in an Invalid position, Feature Boards are being Powered OFF. Reload the system after resetting the backplane Switches to Valid position
Explanation The backplane switches are in an invalid position. Under this condition, the system is not in an operational state. All feature boards are powered off after this state is detected.
Recommended Action Reload the system after resetting the backplane switches to a valid position.
Error Message%DAS_ENV-2-BLOWER_STATUS_MAJOR_ALARM : [chars], MBUS at Power Module [dec] detects Blower alarm = [hex]
Explanation No fans, or a limited number of fans, are operational. The fan condition does not meet cooling requirement of the chassis.
Recommended Action Check or replace the fan controller.
Error Message%DAS_ENV-2-BLOWER_STATUS_MINOR_ALARM : [chars], MBUS at Power Module [dec] detects Blower alarm = [hex]
Explanation Some fans are not operational. The system is running the remaining fans at a high speed to compensate.
Recommended Action Check the fan controller.
Error Message%DAS_ENV-1-BLOWER_STATUS_NORMAL_ALERT : [chars], MBUS at Power Module [dec] detects Blower normal = [hex]
Explanation All fans have recovered from an error condition and are now operating normally.
Recommended Action No action is required.
Error Message%DAS_ENV-2-CRITICAL : Slot [dec], [chars] [int] [chars]
Explanation The specified environmental parameters of the card are outside the normal range of operation.
Recommended Action Check the blowers and the ambient room temperature.
Error Message%DAS_ENV-2-NORMAL : Slot [dec], [chars] [chars] [int] [chars]
Explanation The environmental parameters have returned to a normal condition.
Recommended Action No action is required.
Error Message%DAS_ENV-0-SHUTDOWN : Slot [dec], [chars] [int] [chars]
Explanation The specified environmental parameters of the card are outside the normal range of operation.
Recommended Action Check the blowers and the ambient room temperature.
Error Message%DAS_ENV-1-WARNING : Slot [dec], [chars] [int] [chars]
Explanation The specified environmental parameters of the card are outside the normal range of operation.
Recommended Action Check the blowers and ambient room temperature.
DATACORRUPTION Messages
The following are Data Corruption messages.
Error Message%DATACORRUPTION-1-DATAINCONSISTENCY : [chars]
Explanation Software has detected that some internal data structures may be corrupt. This condition can lead to unpredictable device operation, including, but not limited to, unexpected reloads or spurious memory accesses. This detection is a proactive check for operating system consistency.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DBCONN Messages
The following are Database Connection messages.
Error Message%DBCONN-3-BADLICENSEKEY : Bad license key configured for Database Connection.
Explanation The license key configured with the dbconn license configuration command is not valid.
Recommended Action Check that the license key was entered correctly in the dbconn license configuration command. Refer to the DBCONN feature documentation for information about how to obtain a valid license key.
Error Message%DBCONN-3-BADMODE : Unknown mode '[chars]' configured for server [chars]
Explanation The mode configured for the DBCONN server has been rejected by the remote database server.
Recommended Action Contact your SNA network administrator to determine the correct name of the mode to use to connect to DB2 on the remote database server.
Error Message%DBCONN-3-BADRLU : Bad remote LU '[chars]' configured for server [chars]
Explanation The remote LU configured for the DBCONN server is incorrect.
Recommended Action Contact your SNA network administrator to determine the correct name of the remote LU for DB2 on the remote database server. Ensure that the SNA network name and the LU name are correct.
Error Message%DBCONN-3-BADTPNAME : Bad TP name configured for server [chars]
Explanation The TP name configured for the DBCONN server is not recognized by the remote database server.
Recommended Action Configure a TP name that is available on the remote database server. Most DB2 systems (except for SQL/DS) will accept the DRDA default TP name of X. Contact your SNA network administrator or your DB2 administrator to determine the TP name used by your DB2. To use the DRDA default, do not explicitly configure a TP name for your DBCONN server.
Error Message%DBCONN-3-DRDASYNTAX : DRDA protocol error from server [chars], SYNERRCD x'[hex]'
Explanation An unexpected DRDA protocol error has occurred between DBCONN and the remote database server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug dbconn drda command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.
Error Message%DBCONN-5-IDLETIMEOUT : Client [IP_address] connected to server [chars] has timed out after [time-stamp].
Explanation The client was idle for too long, and the idle timeout configured for the DBCONN server has expired.
Recommended Action No action is required.
Error Message%DBCONN-3-LICENSEEXPERROR : License is expired for Database and Transaction Connection.
Explanation This system is using a temporary key for its Database and Transaction Connection. The license has expired.
Recommended Action Contact StarQuest Software to acquire a permanent key.
Error Message%DBCONN-3-LICENSEEXPWARNING : License is about to expire for Database and Transaction Connection.
Explanation This system is using a temporary key for its Database and Transaction Connection. The license is about to expire.
Recommended Action Contact StarQuest Software to acquire a permanent key.
Error Message%DBCONN-3-LICENSEHWWARNING : Number of connections for TXCONN and DBCONN is at 90% license limit.
Explanation The number of allowed Database and Transaction Connection clients in this system has reached 90 percent of the limit.
Recommended Action Acquire more licenses.
Error Message%DBCONN-5-PWDEXPIRED : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The password supplied by the client was rejected by the remote database server because it has expired.
Recommended Action No action is required.
Error Message%DBCONN-5-PWDINVALID : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The password supplied by the client was rejected by the remote database server.
Recommended Action No action is required.
Error Message%DBCONN-5-PWDMISSING : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The remote database server requires a user ID and password, but the password was not provided.
Recommended Action No action is required.
Error Message%DBCONN-5-SECFAIL : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The user ID or password supplied by the client was rejected by the remote database server.
Recommended Action No action is required.
Error Message%DBCONN-5-SECUNKNOWN : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation An unspecified security failure has occurred. The database host system might be able to provide more specific information.
Recommended Action No action is required.
Error Message%DBCONN-5-UIDINVALID : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The user ID used to connect to the remote database server is not valid.
Recommended Action This is an informational message only. No action is required.
Error Message%DBCONN-5-UIDMISSING : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The remote database server requires a user ID, but the user ID was not provided.
Recommended Action This is an informational message only. No action is required.
Error Message%DBCONN-5-UIDREVOKED : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The user ID used to connect to the remote database server has been revoked.
Recommended Action This is an informational message only. No action is required.
Error Message%DBCONN-5-WLMDOWN : All WLM routes on server [chars] have become unavailable. Recovery is in progress.
Explanation A load-balanced WLM server has lost connectivity to all destinations in its server list. All client connections to this server will be rejected until a host in the complex becomes available again.
Recommended Action No action is required.
Error Message%DBCONN-5-WLMMISMATCH : WLM transport type mismatch on server [chars].
Explanation The transport type within a server list received from a WLM load-balanced database does not match the transport type of the corresponding DBCONN server. If the conflicting server list specifies the SNA network transport type, the default mode #INTER is used to establish the connection.
Recommended Action No action is required.
DBUS Messages
The following are data bus messages.
Error Message%DBUS-3-BADCTRLRTYPE : Invalid controller type [dec] in slot [dec]
Explanation An interface processor responded with an unknown or illegal controller type when queried. This problem should not happen unless the running software does not support the interface processor in question or the interface processor fails.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-BADEEPROM : Invalid EEPROM data found for card in slot [dec], card disabled
Explanation The ID EEPROM on the indicated card is not programmed correctly.
Recommended Action Contact your Cisco technical support representative for a replacement card.
Error Message%DBUS-3-BADHSACONF : Down rev RSP EPROM found HSA system, upgrade EPROM, or remove one RSP
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-3-CXBUSERR : Slot [dec], CBus Error
Explanation A processor has reported a bus error. The processor is reset and is not used until the next OIR event or microcode download, when it is retested.
Recommended Action Reinstall the processor or download the microcode. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-DAUGHTER_STATS : Slot [dec] control [hex], status [hex]
Explanation A processor has reported an error. This error message is sent out in conjunction with other error messages to provide additional information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-3-DBUSINTERR : Slot [dec], Internal Error
Explanation A processor has reported an internal error. The processor is reset and is not used until the next OIR event or microcode download, when it is retested.
Recommended Action Reinstall the processor or download the microcode. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-DBUSINTERRSWSET : Slot [dec], Internal Error due to VIP crash
Explanation A processor has reported an error. The processor is reset and is not used until the next OIR event or microcode download, when it is retested.
Recommended Action Reinstall the processor or download the microcode. If this error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-MSGOVERFLOW : Slot [dec], too many DBUS messages
Explanation A card in the slot identified in the error message has tried to send too many logger messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-3-NOMAGIC : No magic number found in RP1 EEPROM
Explanation The structure containing the system MAC address that is required by the OIR facility cannot be found in the RP EEPROM. The RP must be returned for reprogramming.
Recommended Action Return the RP for reprogramming, and contact your Cisco technical support representative for assistance.
Error Message%DBUS-3-NORESP : bad or no response, slot [int]
Explanation A card in the slot identified in the error message has failed to respond.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-3-NOSUPPORT : No driver support in this image for [chars] in slot [dec] (card type [dec]) - disabled
Explanation The Cisco IOS image does not have driver support code for the specified interface processor.
Recommended Action Remove the unsupported interface processor card or reload the router with a Cisco IOS image that has driver support code for that interface processor card.
Error Message%DBUS-3-PERMANENT_WEDGED : Line card in slot [dec] is permanently wedged
Explanation Two successive attempts to restart and analyze the line card have failed.
Recommended Action Reinstall the line card. This condition could be caused by bad VIP hardware. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%DBUS-3-SLOTCOMP : Slot [dec], dbus error, slot ([hex]) and complement ([hex]) do not match
Explanation A processor has reported a mismatch between the contents of the slot register and its complement. This condition indicates a hardware failure in the diagnostic bus controller on that processor or on the diagnostic bus. The processor is reset and is not used until the next OIR event or microcode download, when it is retested.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-3-SW_NOTRDY : DBUS software not ready after [chars], elapsed [int], status [hex]
Explanation An interface processor failed to appear online after being reset. A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-2-UNKNOWN : Slot [dec], unknown controller type [hex], ignoring
Explanation A processor has reported a controller type that is unknown to the system. The processor is no longer used and must be repaired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-3-WCSCTRLRERR : Slot [dec], WCS Controller Instruction Error
Explanation The WCS is the set of devices on each interface processor that contains the running microcode. It can be loaded either from the ROM on the interface processor or from the system by using the downloadable microcode facility. In this message, a processor reported a WCS controller instruction error. The processor is reset and is not used until the next OIR event or microcode download, when it is retested.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DBUS-3-WCSERR : Slot [dec], WCS controller in error state ([hex]), resetting
Explanation The processor in the slot identified in the error message reported a WCS controller error. The processor is reset, and the new microcode is loaded. This error message appears only when the microcode is downloaded.
Recommended Action Reset the processor and load new microcode. If this error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-WCSFLOW : Slot [dec], flow cntrl error loading WCS, last data [hex] pos [dec]
Explanation A processor has indicated an error condition while downloading microcode. The status, cmd/data, and position numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted, and the ROM microcode is loaded.
Recommended Action If this error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-WCSLDERR : Slot [dec], error loading WCS, status [hex] cmd/data [hex] pos [dec]
Explanation A processor indicated an error condition while downloading the microcode. The status, cmd/data, and position numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted, and the ROM microcode is loaded.
Recommended Action If this error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-WCSPARERR : Slot [dec], WCS Controller Parity Error
Explanation A processor has reported a WCS parity error. The processor is reset and is not used until the next OIR event or microcode download, when it is retested.
Recommended Action Replace the processor or download microcode. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-XILINX : ready wait timeout, slot [int]
Explanation The field-programmable gate arrays on an interface processor failed to load after being reset. This failure indicates a probable software or hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.