COMP_MATRIX through CPPTCAMRM
COMP_MATRIX
%COMP_MATRIX-4-DISABLED : Compatibility Matrix has been disabled. No image compatibility checking will be done. | |
---|---|
Explanation | The ISSU compatibility matrix check has been disabled via configuration command no service image-version compatibility. When the standby comes up, no image compatibility checking will be done, which results in SSO redundancy mode even if the active and standby are running different images. |
Recommended Action | The ISSU compatibility matrix check has been disabled using the global configuration command no service image-version compatibility. Redundancy mode would be SSO. Please be sure this is your intention or change configuration using service image-version compatibility. |
%COMP_MATRIX-3-PRST_VBL_GET : ISSU Compatibility Matrix was unable to read a persistent variable from the local system (rc = [dec]). | |
---|---|
Explanation | The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show persistent variable command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%COMP_MATRIX-3-PRST_VBL_DELETE : ISSU Compatibility Matrix was unable to delete a persistent variable from the [chars] system (rc = [dec]). | |
---|---|
Explanation | The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show persistent variable command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%COMP_MATRIX-3-PRST_VBL_WRITE : ISSU Compatibility Matrix was unable to write to persistent variables on the [chars] system (rc = [dec]). | |
---|---|
Explanation | The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show persistent variable command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
COND_DEBUG_HA
%COND_DEBUG_HA-2-INIT : COND_DEBUG ISSU client initialization failed to [chars]. Error: [dec] ([chars]) | |
---|---|
Explanation | The COND_DEBUG ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%COND_DEBUG_HA-3-TRANSFORM : COND_DEBUG ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars]) | |
---|---|
Explanation | The COND_DEBUG ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the COND_DEBUG state between the active device and the standby device is not identical. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>) |
%COND_DEBUG_HA-3-MSG_SIZE : COND_DEBUG ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars]) | |
---|---|
Explanation | The COND_DEBUG ISSU client failed to calculate the MTU for the specified message. The COND_DEBUG ISSU client will not able to send the message to the standby device. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>) |
%COND_DEBUG_HA-3-INVALID_SESSION : COND_DEBUG ISSU client does not have a valid registered session. | |
---|---|
Explanation | The COND_DEBUG ISSU client does not have a valid registered session. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>) |
%COND_DEBUG_HA-2-SESSION_REGISTRY : COND_DEBUG ISSU client failed to register session information. Error: [dec] ([chars]) | |
---|---|
Explanation | The COND_DEBUG ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>) |
%COND_DEBUG_HA-3-SESSION_UNREGISTRY : COND_DEBUG ISSU client failed to unregister session information. Error: [dec] ([chars]) | |
---|---|
Explanation | The COND_DEBUG ISSU client failed to unregister session information. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>) |
%COND_DEBUG_HA-2-SESSION_NEGO : COND_DEBUG ISSU client encountered unexpected client nego_done. Error: [dec] ([chars]) | |
---|---|
Explanation | An ISSU-compliant client transitions through a series of internal states. The COND_DEBUG ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>) |
%COND_DEBUG_HA-2-SEND_NEGO_FAILED : COND_DEBUG ISSU client failed to send negotiation message. Error: [dec] ([chars]) | |
---|---|
Explanation | The COND_DEBUG ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client) |
%COND_DEBUG_HA-2-GET_BUFFER : COND_DEBUG ISSU client failed to get buffer for message. Error: [dec] ([chars]) | |
---|---|
Explanation | The COND_DEBUG HA client failed to get buffer space for building chkpt message. Message cannot be sent to standby device. If a problem occurs, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client) |
CONFIG_CSRLXC
%CONFIG_CSRLXC-2-INIT_FAILED : CSRLXC configuration cannot occur: [chars] | |
---|---|
Explanation | The system was unable to even attempt to apply LXC configuration for the given reason. |
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. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONFIG_CSRLXC-3-FILE_ERROR : Could not [chars] file [chars]: [chars] | |
---|---|
Explanation | The system was unable to perform the indicated operation on the indicated file for the indicated reason |
Recommended Action | Make sure the given disk is correctly formatted and has sufficient free space available. |
%CONFIG_CSRLXC-3-CONFIG_NOT_SAVED : Configuration not saved to NVRAM. Please inspect [chars] for details. | |
---|---|
Explanation | Out of the generated VM configuration commands, the given number of commands were rejected by the IOSd parser. The configuration is only automatically saved to NVRAM if no errors are encountered, so in this case it was not saved. The indicated log file will describe exactly which commands were rejected, as will any accompanying CSRLXC-4-CLI_FAILURE messages in this log. |
Recommended Action | Inspect the current running-config of the router using the show running-config command. If it appears valid, you may manually save the configuration using copy running- config startup-config. If it does not appear valid, manually correct the configuration or use the config replace nvram:startup- config command to revert to the startup-config. |
%CONFIG_CSRLXC-4-CLI_FAILURE : Configuration command failure: '[chars]' was rejected | |
---|---|
Explanation | The indicated IOSd configuration command generated by the CSRLXC subsystem was rejected by the IOSd CLI. Look for a subsequent CSRLXC-3-CONFIG_NOT_SAVED log message, which will contain a reference to a logfile containing more information about this failure. |
Recommended Action | Inspect the log file to determine why the command was rejected and how to correct it. If necessary, manually re-issue the corrected command. |
%CONFIG_CSRLXC-5-CONFIG_DONE : Configuration was applied and saved to NVRAM. See [chars] for more details. | |
---|---|
Explanation | The generated configuration was successfully applied (no commands were rejected by the IOSd CLI), and the resulting system configuration has been saved to the startup-config in NVRAM. The indicated logfile may contain additional information. |
Recommended Action | No action is required. |
CONF_SW
%CONF_SW-3-FEAT_DOWN : Invalid request [chars] while feature down, conf id [int] | |
---|---|
Explanation | While the feature was not active, an invalid request was received from another layer of the CONF_SW software stack for the specified conf ID. Some requests do not have an associated conf ID. For them the displayed conf ID is zero. |
Recommended Action | This is a software issue. The consequences could be limited to only one or a few confs. LOG_STD_RECUR_ACTION |
%CONF_SW-3-FEAT_UP : Invalid request [chars] while feature up | |
---|---|
Explanation | While the feature was active, an invalid request was received from another layer of the CONF SW software stack. |
Recommended Action | This is a software issue. There are no consequences as this can only have been an Init request while the feature was already active. LOG_STD_RECUR_ACTION |
%CONF_SW-3-NO_RES : [chars] resource not available for the [chars] request, conf id [int] | |
---|---|
Explanation | The specified software resource was not available or could not be located for the specified request from upper CONF SW software stack layers for the specified conf ID. |
Recommended Action | This is a software issue. The consequences are that the specified request could not be performed. LOG_STD_RECUR_ACTION |
%CONF_SW-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int] | |
---|---|
Explanation | For a request from upper CONF SW software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck conf that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations. |
Recommended Action | This is normally a software issue. LOG_STD_RECUR_ACTION |
%CONF_SW-3-IPC_NORES : No space for the IPC reply, size [int] | |
---|---|
Explanation | For a request from upper CONF SW software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck conf that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations. |
Recommended Action | This is normally a software issue. LOG_STD_RECUR_ACTION |
%CONF_SW-2-IPC_INIT : IPC message handler registration failure, rc [int] | |
---|---|
Explanation | Registering an IPC message handler for the CONF SW feature failed. This will cause the feature not to function. The function |
Recommended Action | This is normally a software issue. The consequences are that the CONF SW feature will not function. LOG_STD_ACTION |
CONST_ISSU
%CONST_ISSU-3-MSG_NOT_OK : [chars]([dec]): ISSU message type ([dec]) is not compatible | |
---|---|
Explanation | ISSU received a message not compatible with the running version. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show message type <Client_ID>) |
%CONST_ISSU-3-MSG_MTU : [chars]([dec]): Client failed to get mtu for message [dec] ([chars]) | |
---|---|
Explanation | %s(%d): client cannot get the MTU for a message type |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-TRANSFORM_FAILED : [chars]([dec]): [chars] transformation failed ([chars]) | |
---|---|
Explanation | The transformation operation for the ISSU message has failed |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CF_SEND : [chars]([dec]): Client failed to send message ([dec]) | |
---|---|
Explanation | ISSU client cannot send a negotiation message to a peer |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-ICC_SEND : [chars]([dec]): Client failed to send message | |
---|---|
Explanation | ISSU client cannot send a negotiation message to a peer |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CLIENT_REG : [chars]([dec]): Client failed to register ([chars]) | |
---|---|
Explanation | The ISSU Client could not be registered |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CLIENT_REG_FAILED : [chars]([dec]): Client is not initialized | |
---|---|
Explanation | The ISSU Client is not yet initialized. The negotiation for this client is not yet done. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-SESSION_REG : [chars]([dec]): session failed to register ([chars]) | |
---|---|
Explanation | The client's ISSU session could not be registered |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-SESSION_UNREG : [chars]([dec]): session ([dec]) failed to unregister ([chars]) | |
---|---|
Explanation | The client's ISSU session could not be unregistered |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-START_NEGO_FAILED : [chars]([dec]): failed to start negotiation ([chars]) | |
---|---|
Explanation | The ISSU client cannot start its negotiation |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CAPTYPE_REG : [chars]([dec]): failed to register capability type ([chars]) | |
---|---|
Explanation | The ISSU client failed to register a capability type |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CAPENTRY_REG : [chars]([dec]): failed to register a capability entry ([chars]) | |
---|---|
Explanation | The ISSU client failed to register a capability entry |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CAPGROUP_REG : [chars]([dec]): failed to register a capability group ([chars]) | |
---|---|
Explanation | The ISSU client failed to register a capability group |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-MSGTYPE_REG : [chars]([dec]): failed to register a message type ([chars]) | |
---|---|
Explanation | The ISSU client failed to register a message type |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-MSGGROUP_REG : [chars]([dec]): failed to register a message group ([chars]) | |
---|---|
Explanation | The ISSU client failed to register a message group |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-ENTITY_REG : [chars]([dec]): failed to register the entity ([chars]) | |
---|---|
Explanation | The ISSU entity could not be registered |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-ENTITY_UNREG : [chars]([dec]): failed to unregister the entity ([chars]) | |
---|---|
Explanation | The ISSU entity could not be unregistered |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CAP_REG : [chars]([dec]): failed to register its capabilities ([chars]) | |
---|---|
Explanation | The capabilities of the ISSU client could not be registered |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-MSG_REG : [chars]([dec]): failed to register its messages ([chars]) | |
---|---|
Explanation | Messages for the ISSU client could not be registered |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CAP_EXCHANGE : [chars]([dec]): Capability exchange failed with error ([chars]) | |
---|---|
Explanation | The capability exchange failed, the ISSU client is unable to process the received capability |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-NEGO_PROCESS : [chars]([dec]): Cannot create process: [chars] | |
---|---|
Explanation | The process to negotiate the session for the specified ISSU client cannot be created. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-CONST_MTU_NOT_ENOUGH : [chars]([dec]): Requested buffer size ([dec]) is greater than the max MTU size ([dec]) | |
---|---|
Explanation | Checkpoint buffer size requested is greater than the max MTU size checkpoint supports |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-3-MSG_POLICY : [chars]([dec]): Client failed to negotiate version for message type ([dec]), error ([chars]) | |
---|---|
Explanation | ISSU client cannot negotiate message to a peer |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONST_ISSU-2-NEGO_NOT_DONE : [chars]([dec]): ISSU Negotiation not complete | |
---|---|
Explanation | Unable to complete ISSU negotiation. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
CONTROLLER
%CONTROLLER-5-UPDOWN : Controller [chars], changed state to [chars] | |
---|---|
Explanation | A configurable controller changed its state. |
Recommended Action | No action is required. |
%CONTROLLER-5-DOWNDETAIL : Controller [chars], changed state to [chars] due to [chars] | |
---|---|
Explanation | A configurable controller changed its state. |
Recommended Action | No action is required. |
%CONTROLLER-5-REMLOOP : Controller [chars], remote loop [chars] [chars] | |
---|---|
Explanation | A configurable controller entered remote loopback. |
Recommended Action | No action is required. |
%CONTROLLER-5-REMLOCALLOOP : Controller [chars], local loop [chars] [chars] | |
---|---|
Explanation | A configurable controller entered local loopback. |
Recommended Action | No action is required. |
%CONTROLLER-5-LOOPSTATUS : Controller [chars], [chars] | |
---|---|
Explanation | A configurable controller loopback status. |
Recommended Action | No action is required. |
%CONTROLLER-2-CRASHED : Interface Processor in slot [dec] not responding ([hex]): shutting it down | |
---|---|
Explanation | A controller stopped responding to commands over the cBus, so it was put into shutdown mode. |
Recommended Action | Re-enable the controllers by issuing the no shut configuration command on all controllers on the card, or hotswap out the bad card and install the new one. You must still manually no shut the controllers. |
%CONTROLLER-2-NOTFOUND : For controller [chars] | |
---|---|
Explanation | An internal software error 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 may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONTROLLER-2-FIRMWARE : Controller [chars], [chars] | |
---|---|
Explanation | A software or hardware error 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 may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONTROLLER-5-CALLDROP : Controller [chars], [chars] | |
---|---|
Explanation | A software or hardware error occurred. |
Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
%CONTROLLER-5-HDLC_INSUFF_RESOURCE : Insufficient HDLC resources to enable channel [dec] | |
---|---|
Explanation | Limited number of HDLC channels can be allocated for this trunk |
Recommended Action | Please check the number of HDLC resources supported for this trunk card. Please contact your technical support representative. |
%CONTROLLER-5-CLOCKSTATE : Controller [chars], [chars] | |
---|---|
Explanation | A configurable controller clock changed its state. |
Recommended Action | No action is required. |
%CONTROLLER-2-CDB_NULL : cdb is NULL | |
---|---|
Explanation | A NULL pointer is detected |
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. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONTROLLER-2-DSX_NULL : dsx pointer is NULL | |
---|---|
Explanation | A NULL pointer is detected |
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. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CONTROLLER-4-ACR_DCR_CLOCK_DS1 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int] ([chars]) | |
---|---|
Explanation | DS1 Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_DS3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int] ([chars]) | |
---|---|
Explanation | DS3 Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_DS3_CHANNEL : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int] ([chars]) | |
---|---|
Explanation | DS3:channelized Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_OCN_VT_T1 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int]/[int] ([chars]) | |
---|---|
Explanation | OCN_VT_T1: Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_OCN_CT3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int] ([chars]) | |
---|---|
Explanation | OCN_CT3: Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_OCN_T3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int] ([chars]) | |
---|---|
Explanation | OCN_T3: Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_T3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int] ([chars]) | |
---|---|
Explanation | STMN_T3: Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_E3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int] ([chars]) | |
---|---|
Explanation | STMN_E3: Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_VC1x : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int]/[int] ([chars]) | |
---|---|
Explanation | STMN_VC1x: Recovered clock status change message |
Recommended Action | No action is required. |
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_CT3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int]/[int] ([chars]) | |
---|---|
Explanation | STMN_CT3: Recovered clock status change message |
Recommended Action | No action is required. |
CPPDRV
%CPPDRV-6-INTR : [chars]([dec]) Interrupt : [chars] | |
---|---|
Explanation | A CPP hardware interrupt has occurred. |
Recommended Action | No action is required. |
%CPPDRV-2-HALT : [chars]([dec]) Interrupt : [chars] Seq:%03d Halt bit set. | |
---|---|
Explanation | A Serious CPP hardware error has occurred. |
Recommended Action | No action is required. |
%CPPDRV-3-HOT : [chars]([dec]) Interrupt : [chars] Seq:%03d repeating interrupt has been disabled. | |
---|---|
Explanation | A repeating hardware interrupt has been disabled. |
Recommended Action | No action is required. |
%CPPDRV-3-TCAM_PERR : [chars]([dec]) TCAM Parity error TCAM device #[dec] at offset [hex]. | |
---|---|
Explanation | A Parity error has occurred in a TCAM device. |
Recommended Action | No action is required. |
%CPPDRV-3-TCAM_PERR_FAILURE : [chars]([dec]) Failed to correct TCAM Parity error. Parity error detection disabled. | |
---|---|
Explanation | Failed to correct a TCAM Parity error and further detection has been disabled. |
Recommended Action | No action is required. |
%CPPDRV-3-SRT_PERR_FAILURE : [chars]([dec]) Failed to correct BQS SRT Parity error. | |
---|---|
Explanation | Failed to correct a BQS SRT Parity error. |
Recommended Action | No action is required. |
%CPPDRV-3-LOCKDOWN : QFP[int].[int] CPP Driver LOCKDOWN encountered due to previous fatal error ([chars]: [chars]). | |
---|---|
Explanation | A fatal error has caused the driver to LOCKDOWN. |
Recommended Action | No action is required. |
%CPPDRV-3-LOCKDOWN_INITIATED : QFP[int].[int] CPP Driver LOCKDOWN being triggered due to fatal error. | |
---|---|
Explanation | A fatal error has caused the process to initiate LOCKDOWN. |
Recommended Action | No action is required. |
%CPPDRV-3-INIT_NOTF_ID : CPP[dec]: Failed to initialize: ([chars]) | |
---|---|
Explanation | A function failed to initialize. |
Recommended Action | No action is required. |
%CPPDRV-3-INIT_NOTF : Failed to initialize: ([chars]) | |
---|---|
Explanation | A function failed to initialize. |
Recommended Action | No action is required. |
%CPPDRV-3-DESTROY_NOTF : Failed to destroy connection :([chars]) | |
---|---|
Explanation | A function failed to destroy a connection. |
Recommended Action | No action is required. |
%CPPDRV-3-CLEANUP_NOTF : Failed to Cleanup: ([chars]) | |
---|---|
Explanation | A function failed to cleanup data. |
Recommended Action | No action is required. |
%CPPDRV-3-ALLOC_NOTF : CPP[dec]: Failed to Allocate: ([chars]) | |
---|---|
Explanation | A function failed to allocate data. |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_PLAT_DB : CPP[dec]: ([hex]) Platform failure accessing [chars] | |
---|---|
Explanation | Platform DB query failed |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_INTERRUPT_CLEAR : CPP[dec]: ([hex]) Failed to clear [chars] interrupt | |
---|---|
Explanation | Failed to clear an interrupt node |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_INTERRUPT_OPEN : CPP[dec]: ([hex]) Failed to access [chars] interrupt node - [chars] | |
---|---|
Explanation | Failed to open an interrupt |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_INTERRUPT_HANDLER : CPP[dec]: ([hex]) Failed to register [chars] interrupt handler - [chars] | |
---|---|
Explanation | Failed to register interrupt handler |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_INTERRUPT_INIT : CPP[dec]: ([hex]) Failed to initialize [chars] interrupt - [chars] | |
---|---|
Explanation | Failed to initialize an interrupt |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_ATTACH : CPP[dec]: ([hex]) FAILED: to attach [chars] | |
---|---|
Explanation | Device Failed to attach |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_UNSUPPORT : CPP[dec]: ([hex]) - unsupported CPP TYPE. CPP TYPE:[dec] | |
---|---|
Explanation | Unsupported CPP TYPE |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_INIT : ([hex]) Failed to initialize [chars] - [chars] | |
---|---|
Explanation | Failed to init device |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_INIT_ID : CPP[dec]: ([hex]) Failed to initialize [chars] - [chars] | |
---|---|
Explanation | Failed to init device |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_CREATE : ([hex]) Failed to create [chars] - [chars] | |
---|---|
Explanation | Failed to create device |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_CREATE_ID : CPP[dec]: ([hex]) Failed to create [chars] - [chars] | |
---|---|
Explanation | Failed to create device |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_GET_DETAILS : CPP[dec]: ([hex]) Failed to get [chars] details - [chars] | |
---|---|
Explanation | Failed to get device details |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_ALLOCATE : CPP[dec]: ([hex]) Failed to allocate [chars] - [chars] | |
---|---|
Explanation | Failed to allocate data |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_INTERNAL : CPP[dec]: ([hex]) Internal Error [chars] | |
---|---|
Explanation | Internal coding error. |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_CPP_SUBDEV_ACCESS : CPP[dec].[dec]: An access error has been reported. Error count [int]. | |
---|---|
Explanation | The system has reported an error while accessing a CPP subdevice |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_MEM_CLEAR : CPP[dec]: ([hex]) Failed to clear memory [chars] | |
---|---|
Explanation | SW failed to clear memory location |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_MEM_WRITE : CPP[dec]: ([hex]) Failed to write to memory [chars] | |
---|---|
Explanation | SW failed to write to a memory location |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_ACQUIRE_LOCK : CPP[dec]: ([hex]) Failed to acquire memory lock [chars] | |
---|---|
Explanation | SW failed to acquire shared memory lock |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_RELEASE_LOCK : CPP[dec]: ([hex]) Failed to release memory lock [chars] | |
---|---|
Explanation | SW failed to release shared memory lock |
Recommended Action | No action is required. |
%CPPDRV-4-HW_REV_OLD : Found HW revision [chars], using [chars] based on [chars]. No customer deployment. | |
---|---|
Explanation | The specified board or chip showed an incorrect, invalid or too old hardware revision. That hardware revision was (possibly) overridden to a different value based on some other data available at the time. For instance, the QFP hardware revision might be unprogrammed, so the correct revision was derived from the board type and revision or the QFP's die ID. Boards showing this warning should not be deployed at customer sites. |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_MEM_SIZE : CPP[dec]: ([hex]) Failed to acquire memory size [chars] | |
---|---|
Explanation | SW failed to acquire the size of a block of memory |
Recommended Action | No action is required. |
%CPPDRV-4-ADRSPC_LIMIT : Address space limit [int] KB reached, mapping block [chars] size [int] dynamically, over limit space: [int] KB | |
---|---|
Explanation | The process indicated tried to map more of the Forwarding Engine's address space than was allocated for it. A slower access method will be used instead. This will lower the performance of some operations which require accesses to the Forwarding Engine |
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. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CPPDRV-6-ACCTRC8B : Access CPP [dec] address 0x%08llX (Blk/Off:[chars]/0x%08llX) [chars] %3d bytes 0x%016llX flags [hex] | |
---|---|
Explanation | A CPP access was traced |
Recommended Action | No action is required. |
%CPPDRV-6-ACCTRC16B : Access CPP [dec] address 0x%08llX (Blk/Off:[chars]/0x%08llX) [chars] %3d bytes 0x%016llX_%016llX flags [hex] | |
---|---|
Explanation | A CPP access was traced |
Recommended Action | No action is required. |
%CPPDRV-4-CORE_TABLE : CPP[dec] specific core dump table '[chars]' not found, using minimal fallback table '[chars]' instead | |
---|---|
Explanation | The QFP configuration found on this board did not match any of the tables which define which data has to be collected if a fatal error is detected. Instead a minimal table is used which covers most of the QFP registers. The QFP is fully operational. |
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. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%CPPDRV-3-FATAL_MIN_CPU : CPP[dec]: Insufficent number of CPUs (detected = [dec], required = [dec]) | |
---|---|
Explanation | The current system lacks a sufficent number of CPUs (or cores) to operate. |
Recommended Action | No action is required. |
%CPPDRV-4-CPU_FEATURE : CPP[dec]: CPU lacks feature ([chars]). Performance may be sub-optimal. | |
---|---|
Explanation | The currently installed CPU lacks a certain feature that improve performance of the forwarding engine. The QFP is fully operational, but may operate at a reduced capacity. |
Recommended Action | No action is required. |
%CPPDRV-3-GUEST_CPU_FEATURE : CPP[dec]: Guest CPU lacks feature ([chars]). | |
---|---|
Explanation | The currently installed Guest CPU lacks a certain feature that is required by the forwarding engine, but that feature is supported by the Host CPU. The QFP is operating with normal functionality using the host CPU feature, but live migration to a host which lacks this feature will result in a crash. |
Recommended Action | No action is required. |
%CPPDRV-3-FATAL_CPU_FEATURE : CPP[dec]: CPU lacks feature ([chars]). Packet forwarding disabled. | |
---|---|
Explanation | The currently installed CPU lacks a certain feature that is required by the forwarding engine. The QFP is operating with reduced functionality with packet forwarding disabled. |
Recommended Action | No action is required. |
%CPPDRV-4-FUTURE_FATAL_CPU_FEATURE : CPP[dec]: CPU lacks feature ([chars]) required in a future release. | |
---|---|
Explanation | The currently installed CPU lacks a certain feature that will be required by the forwarding engine in a future release. Caution is advised before upgrading to a newer release to ensure the CPU has the minimum set of CPU features necessary to operate. |
Recommended Action | No action is required. |
CPPFPM
%CPPFPM-6-IPACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%CPPFPM-6-IPACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%CPPFPM-6-IPACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%CPPFPM-6-FMANACLLOGMISSMSG : access-list logging datapath rate-limited or missed [int] packet[chars] | |
---|---|
Explanation | Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available. |
Recommended Action | No action is required. |
CPPOSLIB
%CPPOSLIB-3-INIT_NOTIFY : Failed to initialize: ([chars]) | |
---|---|
Explanation | A function failed to initialize. |
Recommended Action | No action is required. |
%CPPOSLIB-3-ERROR_NOTIFY : [chars] encountered an error | |
---|---|
Explanation | Print error message to console |
Recommended Action | No action is required. |
%CPPOSLIB-3-REGISTER_NOTIFY : Failed to register: ([chars]) | |
---|---|
Explanation | A function failed to register. |
Recommended Action | No action is required. |
%CPPOSLIB-3-GET_NOTIFY : Failed to get data: ([chars]) | |
---|---|
Explanation | A function failed to get data. |
Recommended Action | No action is required. |
%CPPOSLIB-3-CLEAN_NOTIFY : Failed to cleanup: ([chars]) | |
---|---|
Explanation | A function failed to cleanup data. |
Recommended Action | No action is required. |
CPPTCAMRM
%CPPTCAMRM-6-HIGH_WATER_MARK : TCAM resources in the system is limited. | |
---|---|
Explanation | The TCAM device has limited number of free cells left to allocate. |
Recommended Action | No action is required. |
%CPPTCAMRM-6-LOW_WATER_MARK : There is sufficient TCAM resources in the system. | |
---|---|
Explanation | The TCAM device has sufficient number of free cells left. |
Recommended Action | No action is required. |
%CPPTCAMRM-6-TCAM_RSRC_ERR : Allocation failed because of insufficient TCAM resources in the system. | |
---|---|
Explanation | The TCAM device has no free cells to accomodate the current allocation request. |
Recommended Action | No action is required. |