COMMON_MFIB through EM_ISSU

COMMON_MFIB through CPPFPM

COMMON_MFIB

%COMMON_MFIB-3-NOMEM : Memory allocation failure for [chars] in [chars] MFIB [[hex]].
Explanation An attempt to allocate memory has failed. Depending on the criticality of the data to be stored, MFIB operation may be impacted.
Recommended Action Verify that the configuration is supported by the memory present in the system. Copy the message exactly as it appears, and report it to your technical support representative.


%COMMON_MFIB-3-ILLEGALARGS : Illegal arguments - [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-NOBROKER : [chars] distribution broker not found - distributing [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-BROKERINITFAIL : Failed to initialise [chars] RP broker facility
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-BROKER_ENCODE : [chars] broker failed to encode msg type [dec] for slot(s) [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-MFIBXDRINV : Invalid XDR format. [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-MFIBXDRLEN : Invalid XDR length. Type [dec] [chars]. XDR/buffer len [dec]/[dec]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-TABLE : [chars]: [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-MFIB_GSB : Generic subblock error: [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-4-MFIBXDR_REGISTRATION : Unable to register XDR client ([chars]).
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-4-MFIBXDR_NOTREG : XDR client ([chars]) should be registered.
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-MFIBXDR_ISSUREGERROR : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-ASSERT : Assertion '[chars]' failed in [chars] MFIB [[hex]]: [chars] ([chars])[chars].
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-4-DISABLING : [chars] MFIB is being disabled due to a fatal error.
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-4-BROKERINVMSG : Invalid message: [chars], type [chars], len [dec]
Explanation An invalid message has been received by this broker.
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.


%COMMON_MFIB-3-EPOCH : Failed to [chars] table [chars][chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-4-MFIBTABLE : Failed to [chars] table [chars] [chars]
Explanation An MFIB table was found to be missing when attempting to perform a change to it. This may be a transient condition
Recommended Action If the same table gives repeated warnings or generates more serious errors, copy the message exactly as it appears and report it to your technical support representative


%COMMON_MFIB-4-MFIBMSG : Invalid message received. Type [chars], event/sub-type [dec], length [dec]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-ILLEGAL_TABLEID : Attempt to create [chars] table with illegal tableid [dec] ([chars])
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-NO_TABLE_NAME : Attempt to clear the name of [chars] table with tableid [IPV6 address], previous name [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-INVALID_AF : Invalid address family [dec][chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-MFIBISSU_REGISTRATION : Unable to register [chars] ISSU client([int]).
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


%COMMON_MFIB-3-BG_POPULATE : MFIB master background process failed to populate tables for [chars]
Explanation COMMON_MFIB_INTERNAL_ERROR
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.


COMP

%COMP-5-NOBUF : Interface [chars] [chars]
Explanation Interface serial0 compression getbuffer failed, causing Link Access Procedure, Balanced (LAPB) retransmissions.
Recommended Action Configure additional large and big buffers.


%COMP-3-SYNCBAD : Interface [chars] Decompression sync error
Explanation One interface is configured for predictor compression, the other is not.
Recommended Action Configure both interfaces for predictor compression.


%COMP-3-VERSIONBAD : Interface [chars] Compression Version mismatch expected [hex] received [hex]
Explanation One interface is configured for predictor compression, the other is not.
Recommended Action Configure both interfaces for predictor compression.


%COMP-3-SIZEBAD : Interface [chars] Decompression size error
Explanation One interface is configured for predictor compression, the other is not.
Recommended Action Configure both interfaces for predictor compression.


%COMP-3-COMPERR : [chars]: COMPRESS: (stac error!) status: [dec], size in: [dec], size out: [dec]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%COMP-3-CONFIGBAD : Interface [chars] Compression internal configuration error
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%COMP-3-BADCOMP : Interface [chars] Bad status returned from packet compression operation
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%COMP-3-SUBBLOCKERR : Interface [chars] compression subblock creation failed.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


COMPILED_ACL

%COMPILED_ACL-3-INTERNAL_ERROR : an unexpected internal error occured: [chars]
Explanation An unexpected internal error occurred. This error may result in one or more flows being punted to the RP or in Turbo ACL not functioning.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_WRONG : [chars]: entry at row [int], column [int] in node [int] does not reference row [int] in the node's child
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_PROCESSING_OVERFLOWED : [chars]: processing back-pointers in row [int] in node [int] but the list is marked as overflowed
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY : [chars]: the back-pointer list for row [int] in node [int] is marked as overflowed but is not empty
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY_REFERENCES : [chars]: the back-pointer list for row [int] in node [int] is marked as overflowed but is not empty
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BAD_PROCESS_REFERENCES : [chars]: error while processing references for row [int] in node [int]: [chars]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-DEFERRED_ENTRY_CONSISTENCY : [chars]: while [chars] in row [int] in node [int], found deferred entry bitmap is [chars] but count is [int]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ROW_UPDATE : [chars]: cannot process row queue update for row [int] in node [int]: [chars]
Explanation EXPLANATION_INTERNAL_ERROR EXPLANATION_IMPACT_POSSIBLE_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ROW_UPDATE_ENQUEUE : [chars]: cannot process row queue update for row [int] in node [int]: enqueue failed ([int]/[int] entries, list is [chars]valid, entry is [chars]enqueued)
Explanation EXPLANATION_INTERNAL_ERROR EXPLANATION_IMPACT_POSSIBLE_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ROW_THROTTLE : [chars]: unable to re-queue row [int] on row queue for node [int]; node should not have been freed as it was written to only [int] ms ago
Explanation EXPLANATION_INTERNAL_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-2-LIST_CREATE : [chars]: failed to create row queue for node [int], Turbo ACL has been disabled temporarily
Explanation The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-2-QUEUE_INIT : [chars]: failed to initialize back-pointer list for row [int] in node [int], Turbo ACL has been disabled temporarily
Explanation The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-5-LIST_INFO : [chars]: failed to set list information function for node [int]'s row queue (ID [int])
Explanation The system encountered an error while initializing a function vector used for debugging purposes. Turbo ACL will continue to function correctly, but the show list ID command will not show Turbo ACL-specific information for the specified list ID number.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BAD_ROW_FREE : [chars]: cannot free row [int] in node [int]: [chars]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ENTRY_COUNT : [chars]: row entry counters not allocated for node [int] while freeing row [int]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show persistent variable command to gather data that may help identify the nature of the error. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show persistent variable command to gather data that may help identify the nature of the error. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show persistent variable command to gather data that may help identify the nature of the error. 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)


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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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 through CRYPTO_DEV_PROXY

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.


CPPUI

%CPPUI-3-ERROR_NOTIFY : [chars]
Explanation An UI fault has occurred.
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.


CPP_BQS

%CPP_BQS-3-INVALID_SUBTYPE : CPP BQS RM Proxy subtype [int]
Explanation BQS proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.
Recommended Action LOG_STD_ACTION


%CPP_BQS-3-INIT_FAILED : CPP BQS RM Proxy, region [chars]
Explanation BQS proxy failed due initialize or resize software managed memory.
Recommended Action LOG_STD_ACTION


%CPP_BQS-3-CMD_ACTIVE : CPP BQS Proxy Command, correlator [int]
Explanation A BQS Proxy command was received, but the correlator was still in use. Commad was not processed.
Recommended Action LOG_STD_ACTION


%CPP_BQS-2-MPASS_FS_REG : CPP BQS PROXY feature special vector [dec] registration failed (result: [dec])
Explanation Cisco internal software error. CPP multipass registration of a feature special processing vector for BQS Proxy failed. The BQS proxy will not be fully functional while this condition exists.
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.


%CPP_BQS-3-CARVE : [chars]: size [int] SW carved out memory region initialization failed.
Explanation A BQS proxy failed to initialize the software memory region.
Recommended Action LOG_STD_ACTION


%CPP_BQS-3-RESIZE : CPP BQS Proxy Memory Manager, region [chars]
Explanation BQS proxy failed to resize software managed memory.
Recommended Action LOG_STD_ACTION


%CPP_BQS-2-PROXY_IPC_INIT_FAILED : CPP BQS Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP BQS initialization detected that the Proxy IPC interface initialization failed. The BQS Proxy will not be functional while this condition exists.
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.


%CPP_BQS-3-PROXY_IPC_SEND : failure: [chars]
Explanation BQS Proxy send response failed, response was dropped.
Recommended Action LOG_STD_ACTION


%CPP_BQS-3-MAX_GPM_TX_LEN_EXCEED : CPP BQS Proxy Command, exceed GPM tx len [int]
Explanation A BQS Proxy command recycle a packet exceed GPM tx len
Recommended Action LOG_STD_ACTION


CPP_FM

%CPP_FM-4-CPP_FM_FIELD_IGNORED : Matching on field type [int] ([chars] value [int] ([hex])) not supported for client [chars] ([int]), rule oid: [chars], seqnos: [int], [int], [int]: RULE *IGNORED*
Explanation User is trying to use a classification criterion not supported by the feature. For example, user is trying to apply a with a class matching matched on an IPv6 ACL that contains a match on flow-label. The entire rule (e.g. ACE) containing the unsupported criterion is ignored. In our example, only the ACEs containing match on flow label are ignored. All other ACEs are still downloaded to CPP.
Recommended Action No action is required.


%CPP_FM-3-CPP_FM_TCAM_WARNING : TCAM limit exceeded: [chars]
Explanation
Recommended Action


%CPP_FM-3-CPP_FM_CLIENT_WARNING : Client Is Invalid: [chars]
Explanation
Recommended Action


%CPP_FM-4-CPP_FM_TCAM_MORE_INFO_WARNING : TCAM limit exceeded: [chars]
Explanation
Recommended Action


CPP_FR

%CPP_FR-2-PROXY_IPC_INIT_FAILED : Frame Relay Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. FR initialization detected that the Proxy IPC interface initialization failed. The FR interfaces may not function properly while this condition exists.
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.


%CPP_FR-3-INV_PROXY_MSG : CPP FR Proxy received invalid IPC message ID [dec]
Explanation Cisco internal software error. CPP FR Proxy received an invalid message ID. This message will be ignored.
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.


%CPP_FR-3-PROXY_IPC_ALLOC_FAIL : CPP Frame Relay Proxy response to msg id [int] lost due to buffer allocation failure
Explanation Cisco internal software error. CPP Frame Relay Proxy message processing detected a IPC buffer allocation failure during response processing.
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.


%CPP_FR-4-PROXY_IPC_ALLOC_FAIL2 : QFP Frame Relay MFR Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a IPC buffer allocation failure during proxy response processing. The associated Frame Relay MFR functionality may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_SID_UPDATE_LOCK_ERROR : QFP Frame Relay Proxy ([chars]) Multiple SID Update Locks to same interface (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
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.


%CPP_FR-3-PROXY_SID_UPDATE_COMPLETE_ERROR : QFP Frame Relay MFR Proxy ([chars]) SID Update Complete w/o Preceeding Lock (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
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.


%CPP_FR-2-BQS_SCRATCH_TOOSMALL : QFP BQS Scratch area too small for Frame Relay MFR feature usage (size: [dec], need: [dec]).
Explanation Cisco internal software error. QFP Frame Relay MFR initialization detected that the BQS scratch memory area is insufficient for Frame Relay MFR usage. The Frame Relay MFR Bundle interfaces will not be functional while this condition exists.
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.


%CPP_FR-3-PROXY_INV_RX_TX_INTF_VALUE : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Rx/Tx interface value [dec] for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Bundle state change or configuration update due to an invalid interface Rx/Tx designation in the proxy request. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_NULL_BUNDLE : QFP Frame Relay MFR Proxy ([chars] [chars]) NULL Bundle sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Bundle state change or configuration update due to an invalid or uninitialized Bundle sub-block. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_NULL_LINK : QFP Frame Relay MFR Proxy ([chars] [chars]) NULL Member Link sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Member Link state change or configuration update due to an invalid or uninitialized Member Link sub-block. The associated Frame Relay MFR Member Link interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_NULL_DLCI : QFP Frame Relay MFR Proxy ([chars] [chars]) NULL PVC sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Member PVC state change or configuration update due to an invalid or uninitialized PVC sub-block. The associated Frame Relay MFR PVC interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_BUNDLE_STATE : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message could not be processed due to the Frame Relay MFR Bundle being in an incorrect state to accept the message. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_LINK_STATE : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message could not be processed due to the Frame Relay MFR Link being in an incorrect state to accept the message. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_SUB_DEV_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Sub-Device ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message Bundle Add could not be processed for the indicated interface due to an invalid Sub-Device ID. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_LINK_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Link ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message Link Add could not be processed for the indicated interface due to an invalid Link ID. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_DUP_LINK_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) duplicate Link ID [dec] for interface [chars] and [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message Link Add could not be processed for the indicated interface due use of a given Link ID on multiple member links within the same Frame Relay MFR Bundle. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_DLCI_INFO : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid PVC Info (Base: [hex], Num: [dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message contained invalid Frame Relay MFR PVC information. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_DUP_DLCI_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) duplicate DLCI [dec] for interface [chars] and [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message DLCI Add could not be processed for the indicated interface due use of a given DLCI on multiple member links within the same Frame Relay MFR Bundle. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_LOST_SEQ_TO : QFP Frame Relay MFR Proxy ([chars] [chars]) indicated an invalid lost sequence timeout ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR was provided a invalid lost sequence timeout value. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_BUFFER_LIMIT : QFP Frame Relay MFR Proxy ([chars] [chars]) indicated an invalid Rx buffer limit ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR was provided a invalid Rx buffer limit value. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-3-PROXY_INV_TX_LINK_WEIGHT : QFP Frame Relay MFR Proxy ([chars] [chars]) indicated an invalid Tx Link weight ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message contained invalid Tx Link weight information. The associated Frame Relay MFR Member Link and/or Bundle interface may not be fully functional as a result of this condition.
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.


%CPP_FR-4-PROXY_SYNC : QFP Frame Relay MFR Proxy ([chars] [chars]) Bundle/Link sync issue with interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle-Link state synchronization abnormality. This condition should be cosmetic. Full context of the message will aid in problem isolation.
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.


%CPP_FR-3-MFR_INVALID_RX_DLCI : Frame Relay MFR DLCI ([dec]) received from the peer must be configured for interface [chars] (Peer error), MSGDEF_LIMIT_SLOW
Explanation Possible error on the peer device with Multilink FR. Received Multilink FR packet contained wrond DLCI number.
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.


%CPP_FR-4-TX_BUNDLE_FLOWED_OFF : QFP Frame Relay MFR Tx Bundle [chars] flowed off for an abnormal duration due to one or more congested member link(s)
Explanation Possible Cisco internal software or hardware error. QFP Frame Relay MFR Tx processing detected that a Frame Relay MFR Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
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.


CPP_IPHC_PROXY

%CPP_IPHC_PROXY-3-INVALID_IPC_INPUT : [chars] CPP IPHC Client Proxy failure
Explanation IPHC proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.
Recommended Action LOG_STD_ACTION


CPP_LDN

%CPP_LDN-2-PROXY_IPC_INIT_FAILED : CPP LDN Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP LDN initialization detected that the Proxy IPC interface initialization failed. The LDN Proxy will not be functional while this condition exists.
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.


%CPP_LDN-3-PROXY_IPC_SEND : failure: [chars]
Explanation LDN Proxy send response failed, response was dropped.
Recommended Action LOG_STD_ACTION


%CPP_LDN-3-PROXY_IPC_INVALID : failure: [dec]
Explanation LDN Proxy received an invalid IPC msg from the client.
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.


%CPP_LDN-3-PROXY_GPM_RSRC_FAIL : failure: [chars]
Explanation LDN Proxy failed in performing a GPM operation.
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.


%CPP_LDN-3-PROXY_METAPKT_ENQ : subdevice id: [dec] failure: [dec]
Explanation LDN Proxy metapacket enqueue 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.


CRASH_DUMP

%CRASH_DUMP-3-FILE_OP : FILE operation [chars] failed CRASH DUMP May not be successfull
Explanation The File operation for dumping DSP crash details failed The error message could be a software issue or due to not enough disk space.
Recommended Action No action is required.


%CRASH_DUMP-6-TIMEOUT : CRASH DUMP may not be successfull for the device [dec]
Explanation Crash dump process timed out waiting for diaganostic messages
Recommended Action No action is required.


%CRASH_DUMP-6-ABORT : CRASH DUMP aborted for device [dec]
Explanation Crash dump aborted. Crash Dump may not be successfull
Recommended Action No action is required.


CRYPTO_DEV_PROXY

%CRYPTO_DEV_PROXY-2-PROXY_IPC_INIT_FAILED : QFP Crypto device Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device Proxy initialization detected that the IPC interface initialization failed. QFP Crypto device proxy will not be functional while this condition exists.
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.


%CRYPTO_DEV_PROXY-2-PROXY_REG_NULL_MSG_HNDLR : QFP Crypto device Proxy registered invalid message handlers (source: [chars]).
Explanation Cisco internal software error. QFP Crypto device Proxy registered with invalid message handler. QFP Crypto device Proxy will not be functional while this condition exists.
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.


%CRYPTO_DEV_PROXY-3-PROXY_BAD_MSG : QFP Crypto device Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP Crypto device Proxy received a corrupted message from control plane. This message will be ignored.
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.


%CRYPTO_DEV_PROXY-3-PROXY_INV_MSG : QFP Crypto device Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP Crypto device Proxy received an invalid message from control plane. This message will be ignored.
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.


%CRYPTO_DEV_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP Crypto device Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP Crypto device Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition.
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.


%CRYPTO_DEV_PROXY-3-PROXY_IPC_SEND_FAILED : QFP Crypto device Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device Proxy message processing detected a message sent failure. The message is lost as the result of this condition.
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.


CRYPTO_RSA_ISSU through CWAN_ALARM

CRYPTO_RSA_ISSU

%CRYPTO_RSA_ISSU-3-INIT : Crypto RSA ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CRYPTO_RSA_ISSU-3-TRANSFORM_FAIL : Crypto RSA ISSU client [chars] transform failed for message type [dec]. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message can not be applied on the standby unit. In both cases the Crypto RSA state will not be indentical with the active unit.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>)


%CRYPTO_RSA_ISSU-3-MSG_NOT_OK : Crypto RSA ISSU client message type [dec] is not compatible
Explanation Crypto RSA ISSU client received an incompatible message from the peer unit. Since the message is not compatible it cannot be processed by this unit
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%CRYPTO_RSA_ISSU-3-MSG_SIZE : Crypto RSA ISSU client failed to get the MTU for message type [dec]. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to calculate MTU for the message specified. The dot1x ISSU client will not be able to send message to the standby unit.
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>)


%CRYPTO_RSA_ISSU-3-INVALID_SESSION : Crypto RSA ISSU client does not have a valid registered session.
Explanation Crypto RSA ISSU client does not have a valid registered session. When there is a problem with the session the standby unit cannot be brought up.
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>)


%CRYPTO_RSA_ISSU-3-SESSION_REGISTRY : Crypto RSA ISSU client failed to register session information. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to register session information. When there is a problem with the session the standby unit cannot be brought up.
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>)


%CRYPTO_RSA_ISSU-3-SESSION_UNREGISTRY : Crypto RSA ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation Crypto RSA 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>)


%CRYPTO_RSA_ISSU-3-SESSION_NEGO : Crypto RSA ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client encountered an unexpected 'client negotiation done'.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%CRYPTO_RSA_ISSU-3-SEND_NEGO_FAILED : Crypto RSA ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to send a session negotiation message to the peer. When there is a problem in the ISSU negotiation the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


%CRYPTO_RSA_ISSU-3-GET_BUFFER : Crypto RSA ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to get buffer for building a negotiation message. Hence, it cannot send the negotiation message to the standby unit. When there is a problem in the negotiaiton the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


CRYPTO_SL_TP_LEVELS

%CRYPTO_SL_TP_LEVELS-3-VAR_SET_FAILED : Update of rommon variable failed: retcode=[dec]
Explanation Call to update rommon variable 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.


%CRYPTO_SL_TP_LEVELS-6-VAR_NEW_VALUE : Setting crypto bidir throughput to: [dec] kbps
Explanation Crypto throughput rommon var updated
Recommended Action No action required. Informational message.


%CRYPTO_SL_TP_LEVELS-6-TP_THROTTLE_STATE : Crypto throughput [chars] throttled. New level is [dec]
Explanation Maximum throughput level is the same as unthrottled. All other levels are throttled
Recommended Action No action required. Informational message.


%CRYPTO_SL_TP_LEVELS-3-INV_PLATFORM_VALUE : Invalid platform level value, token: [chars]
Explanation
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.


%CRYPTO_SL_TP_LEVELS-3-INV_DEFAULT_VALUE : Invalid platform default value, token: [chars]
Explanation
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.


%CRYPTO_SL_TP_LEVELS-3-NO_VALID_PLATFORM_VALUES : No valid platform level values specified
Explanation
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.


%CRYPTO_SL_TP_LEVELS-3-ROMMON_WRITE_FAILED : Error in updating rommon variable
Explanation
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.


%CRYPTO_SL_TP_LEVELS-6-SAVE_CONFIG_AND_RELOAD : New throughput level not applied until reload; please save config
Explanation
Recommended Action


%CRYPTO_SL_TP_LEVELS-6-ROMMON_VAL : Current rommon value: [dec]
Explanation
Recommended Action


%CRYPTO_SL_TP_LEVELS-6-TP_LEVEL_LIMITED : HSECK9 is disabled: bandwidth restricted to 250Mbps
Explanation
Recommended Action


%CRYPTO_SL_TP_LEVELS-6-TP_LICENSE_TP_REQUEST_FAILED : License request failed, rc=[dec]
Explanation License request failed. Data plane will use platform default throughput level
Recommended Action Look at other logs/debugs to see reason for failure.


%CRYPTO_SL_TP_LEVELS-6-TP_LICENSE_HSEC_REGISTER_FAILED : License registration failed, rc=[dec]
Explanation License request failed.
Recommended Action Look at other logs/debugs to see reason for failure.


%CRYPTO_SL_TP_LEVELS-6-TP_LICENSE_HSEC_REQUEST_FAILED : License request failed, rc=[dec]
Explanation HSECK9 License request failed.
Recommended Action Look at other logs/debugs to see reason for failure.


CSMPI

%CSMPI-3-PLATFORM_INIT_FAILED : CSMPI platform initialization failed.
Explanation Essential CSMPI initialization 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.


%CSMPI-3-IF_INIT_FAILED : CSMPI interface initialization failed.
Explanation Essential CSMPI initialization 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.


%CSMPI-3-ADDR_MISMATCH : Region address error: start @ [IPV6 address], end @ [IPV6 address], part addr @ [IPV6 address]
Explanation CSMPI encountered a bnad buffer address, possible corruption.
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.


%CSMPI-3-BAD_INDEX : bad particle index [int], max [int], addr [IPV6 address]
Explanation CSMPI encountered a bnad buffer address, possible corruption.
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.


CSVERIFY

%CSVERIFY-3-CSVERIFY_FAIL : Signature verification: [[chars]]
Explanation During digital signature verification, an error has occured
Recommended Action Check the diagnostic csverify trace file for more information on the underlying failure.


%CSVERIFY-6-CSVERIFY_SUCCESS : Signature verification success for [chars]
Explanation Signature verification was successful for the file mentioned.
Recommended Action This is an informational message. No action is required.


CTLPROVIDERSERV

%CTLPROVIDERSERV-3-NOINIT : Can't initialize Credentials server
Explanation Internal problems with initializing ports for the Credentials server
Recommended Action Make sure the Credentials server port is available on the local machine.


%CTLPROVIDERSERV-3-NOMEM : Can't initialize memory for Credentials server
Explanation Insufficient Memory for Credentials server
Recommended Action Increase amount of available memory


%CTLPROVIDERSERV-3-NOSOCKETS : Max Number of Credentials Server sockets exceeded
Explanation There are too many Credentials clients requesting service
Recommended Action Reduce number of Credentials requesting service


%CTLPROVIDERSERV-3-NOPROC : Could not start Credentials Server
Explanation Internal Problem in process creation
Recommended Action None


CTS_PD

%CTS_PD-3-IPC_INVALID_MSG : CTS-Invalid request [int]
Explanation We received an invalid message from another layer of the CTS software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CTS_PD-3-FEAT_DOWN : CTS-Invalid request [chars] ([int]) while feature is down
Explanation While the feature was not active, an invalid request was received from another layer of the CTS software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CTS_PD-3-FEAT_CTX_DOWN : CTS-Invalid request [chars] ([int]) while context is down
Explanation While the feature context was not active, an invalid request was received from another layer of the CTS software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CTS_PD-3-IPC_OPEN_REPLY : CTS-IPC Open Reply failed, request [int]
Explanation For a request from upper CTS software stack layers it was not possible to open the reply buffer.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CTS_PD-3-IPC_NORES : CTS-No space for the IPC reply, size [int], request [int]
Explanation For a request from upper CTS software stack layers it was not possible to allocate space for a reply for the specified size.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CTS_PD-3-IPC_INVALID_MSG_LEN : CTS-Invalid IPC length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length
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.


%CTS_PD-3-IPC_SEND_FAILED : CTS-IPC [chars] [int] send failed [int]
Explanation IPC message send failure
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.


%CTS_PD-3-IPC_INIT_FAILED : CTS-IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CTS feature failed. This will cause the feature to not function.
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.


%CTS_PD-2-IPC_FAILURE : CTS-IPC message [chars] handler failed, rc [int]
Explanation An IPC message handler for the CTS feature failed. This will cause the feature to not function.
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.


CUBE

%CUBE-1-LICENSING : [chars]
Explanation CUBE Licensing Enforcement
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


CVLA

%CVLA-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper CVLA software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as infra activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CVLA-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper CVLA 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 monitor that cannot be established etc. In rare cases this could also affect other operations such as infra activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CVLA-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CVLA infra failed. This will cause the infra to not function.
Recommended Action This is normally a software issue. The consequences are that the CVLA infra will not function. LOG_STD_ACTION


CWANLC_ATM

%CWANLC_ATM-4-UNSUP : [chars]: unsupported feature: [chars]
Explanation This feature is not supported by Draco ATM RP.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWANLC_ATM-3-CMDERR : [chars]: [chars] IPC command fails (cause: [hex])
Explanation The ATM RP driver experienced IPC command error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWANLC_ATM-3-IPC_ERROR : [chars]: IPC command [chars] failure due to [chars]
Explanation The SPA ATM RP driver experienced IPC command error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWANLC_ATM-4-MISMATCH_VCENCAP : [chars]: Cannot mix VC encapsulation types in multipoint interfaces
Explanation This ATM card only allows VC encapsulations of the same type on the main interface or multipoint subinterfaces
Recommended Action Reconfigure the ATM interface with matching VC encapsulations


%CWANLC_ATM-3-VCCLOSEFAIL : [chars]: Failed to remove VC [dec]/[dec] cause [int]
Explanation Attempt to remove VC on the linecard failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWANLC_ATM-3-VPCLOSEFAIL : [chars]: Failed to remove VP [dec] cause [int]
Explanation Attempt to remove VP on the linecard failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWANLC_ATM-3-NOVPSPACE : [chars]: out of VP space for VPI [dec]
Explanation Out of VPs on the SAR.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWANLC_ATM-4-SEMHOG : [chars]: Process [dec] ([chars]) hogging semaphore -- called by process [dec] ([chars])
Explanation The named process has held the resource semaphore longer than expected.
Recommended Action No action is required.


%CWANLC_ATM-4-CLOSEPEND : [chars]: The TX SAR is currently freeing internal buffers previously allocated for the identical channel id. The execution of the current command is delayed.
Explanation The TX SAR has taken longer than expected to free its internal buffers.
Recommended Action No action is required.


CWAN_ALARM

%CWAN_ALARM-6-SONET : [chars] [chars] [chars] [chars] [chars]
Explanation This message is generated whenever (a) an alarm is present in the system (and the alarm status has been reported to the RP) or (b) an alarm has been removed from the system (and the alarm status has been reported to the RP
Recommended Action No action is required.


%CWAN_ALARM-6-INFO : [chars] [chars] [chars] [chars] [chars]
Explanation This message provides alarm assertion or deassertion information.
Recommended Action No action is required.


CWAN_CHOC through CWMP_DOWNLOAD

CWAN_CHOC

%CWAN_CHOC-4-ALLOCFAIL : Interface [dec]/[dec] allocation failed: [chars]
Explanation required resources unavailable.
Recommended Action Either upgrade system memory or reconfigure memory usage.


%CWAN_CHOC-4-UNSUP : Slot [dec]: Unknown [chars] ([dec])
Explanation This value is not recognized by this version of software.
Recommended Action Check linecard version. Normally this is harmless but worth contacting cisco technical support representative.


%CWAN_CHOC-4-IFCONFIG : [chars] config error ([dec], lc delay:[dec] ms): [chars]
Explanation RP received configuration error from linecard.
Recommended Action Reconfigure or shut/no shut the error channel.


%CWAN_CHOC-4-PROV_FAIL : Interface [chars] provisioning ch([dec]) failed: [chars]
Explanation provisioning conflict or resource shortage
Recommended Action workaround: under 'controller sonet', do 'no channelized' followed by 'channelized', twice. If problem persists, do a 'show controller sonet <slot>/<port>' and 'show controller {pos/serial} <slot>/<port>:<chan>' then contact cisco technical support representative.


%CWAN_CHOC-4-UNPROV_FAIL : Interface [chars] unprovisioning failed: [chars]
Explanation Linecard failed to response unprovisioning command.
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.


%CWAN_CHOC-4-CORRUPT : [chars] information seems to be corrupted, bad value =[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected value is discarded.


%CWAN_CHOC-4-LCLOCK_FAIL : Interface [chars] failed to acquire semaphore for LC access: [chars]
Explanation Other process locked the semaphore for too long.
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.


%CWAN_CHOC-4-LCCFG_MISMATCH : LC needs reboot due to config mismatch on [chars], (rc=[int])
Explanation RP detects LC's channel provisioning mismatching start-config
Recommended Action reset linecard: hw-module module <slot> reset


%CWAN_CHOC-4-WRONG_LL : %.16s received wrong loveletter : type=[int], length=[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected messages from linecard is harmlessly discarded.


%CWAN_CHOC-6-WRONG_GULF : [chars] hardware version (gulf v[int]) does not support OC-12 or OC-48
Explanation Early version of hw asic (GULF2.0 and below) has bugs in rx fifo depth which can not handle oc-12 or oc-48 rate. Either limiting channel provisioning or upgrading hw
Recommended Action Limit channel provisioning to DS3 and/or OC3


%CWAN_CHOC-6-LCDRIVER : OIR failed: slot [int] linecard not responding to initial query
Explanation OIR insertion aborted due to failing to contact lc
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.


CWAN_CHOC_DS0

%CWAN_CHOC_DS0-3-UNKNOWNCTRLR : Slot [dec] - Unknown linecard type [dec]
Explanation This hardware can't be recognized by this version of software.
Recommended Action Check software version. Make sure the software supports the hardware.


%CWAN_CHOC_DS0-3-RMCTRLR_UNKNOWN : Slot [dec] - Unknown linecard type [dec] removed
Explanation This hardware can't be recognized by this version of software.
Recommended Action Check software version. Make sure the software supports the hardware.


%CWAN_CHOC_DS0-3-CDBFAIL : Port [dec]/[dec] - fail to create a SONET controller data structure
Explanation The software resource can't be allocated for this hardware
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.


%CWAN_CHOC_DS0-3-PORTFAIL : Port [dec]/[dec] - fail to create a port instance data structure
Explanation The software resource can't be allocated for this hardware
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.


%CWAN_CHOC_DS0-3-T1CFG_CCBERROR : CCB command error (cmd, [dec], arg [dec]) on T1 [dec]/[dec]/[dec]
Explanation A command sent from the system to a linecard 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.


%CWAN_CHOC_DS0-3-VCCFG_CCBERROR : CCB command error (cmd, [dec], arg [dec]) on port [dec]/[dec] channel [dec]
Explanation A command sent from the system to a linecard 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.


%CWAN_CHOC_DS0-3-IFCONFIG_ERR : config error on port [dec]/[dec]([chars]), cmd [dec] [chars]
Explanation A configuration command sent from the system to a linecard 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.


%CWAN_CHOC_DS0-4-UNSUP : Slot [dec]: Unknown [chars] ([dec])
Explanation This value is not recognized by this version of software.
Recommended Action Check linecard version. Normally this is harmless but worth contacting cisco technical support representative.


%CWAN_CHOC_DS0-3-CFG_BAD_PARA : [chars]: invalid config parameter [chars]
Explanation Configuration parameter is invalid
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.


%CWAN_CHOC_DS0-4-IFCONFIG : [chars] config error ([dec], lc delay:[dec] ms): [chars]
Explanation RP received configuration error from linecard.
Recommended Action Reconfigure or shut/no shut the error channel.


%CWAN_CHOC_DS0-4-ALLOCFAIL : Interface [dec]/[dec] allocation failed: [chars]
Explanation required resources unavailable.
Recommended Action Either upgrade system memory or reconfigure memory usage.


%CWAN_CHOC_DS0-4-PROV_FAIL : Interface [chars] provisioning ch([dec]) failed: [chars]
Explanation provisioning conflict or resource shortage
Recommended Action workaround: under 'controller sonet', do 'no channelized' followed by 'channelized', twice. If problem persists, do a 'show controller sonet <slot>/<port>' and 'show controller {pos/serial} <slot>/<port>:<chan>' then contact cisco technical support representative.


%CWAN_CHOC_DS0-4-UNPROV_FAIL : Interface [chars] unprovisioning failed: [chars]
Explanation Linecard failed to response unprovisioning command.
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.


%CWAN_CHOC_DS0-4-WRONG_LL : %.16s received wrong loveletter : type=[int], length=[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected messages from linecard is harmlessly discarded.


%CWAN_CHOC_DS0-4-CORRUPT : [chars] information seems to be corrupted, bad value =[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected value is discarded.


%CWAN_CHOC_DS0-4-LCLOCK_FAIL : Interface [chars] failed to acquire semaphore for LC access: [chars]
Explanation Other process locked the semaphore for too long.
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.


%CWAN_CHOC_DS0-3-UNKNOWN_MIB_TYPE : Unknown MIB type [int] from slot [int]
Explanation Draco received unknown communication message from linecard
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DS0-5-LOOPSTATUS : [chars], [chars]
Explanation A configurable loopback status.
Recommended Action No action is required.


CWAN_CHOC_DSX

%CWAN_CHOC_DSX-3-UNKNOWN_CTRLR : Slot [dec] - Unknown linecard type [dec]
Explanation This hardware can't be recognized by this version of software.
Recommended Action Check software version. Make sure the software supports the hardware.


%CWAN_CHOC_DSX-3-T3CFG_ERROR : T3 [int]/[int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard 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.


%CWAN_CHOC_DSX-3-T1CFG_ERROR : T1 [int]/[int]/[int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard 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.


%CWAN_CHOC_DSX-3-VCCFG_ERROR : VC [int]/[int]:[int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard 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.


%CWAN_CHOC_DSX-3-NULLDS3MIBTABLE : Null DS3 MIB table (snmp_if_index [int])
Explanation System cannot find the DS3 MIB table pointer
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-3-SEND_DRIVER_READY : send driver ready msg failed for [dec]
Explanation IPC message failure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-5-DEF_SUBRATE : [chars] [chars]
Explanation Remote subrate configuration changed
Recommended Action Inform the network operator that subrate configuration changed by remote end


%CWAN_CHOC_DSX-3-ENQUEUE_FAIL : [chars]
Explanation cmd enqueue failure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-5-UNKNOWN_EVENT : [chars]
Explanation Unexpected event received by the process
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-3-PROCESS_FAIL : process creation failed for [chars]
Explanation process creation failed for handling cmd
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-3-PROCESS_ERROR : process error - [chars]
Explanation process encountered fatal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-3-INVALID_SUBR_HWIDB : Invalid Subrate hwidb on T3 [dec]/[dec]
Explanation invalid subrate hwidb
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-3-VC_CONFIG_ERR : [chars] T1 [dec] channel group [dec] of T3 [dec]/[dec] unsuccessful (error code [dec])
Explanation channel configuration error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CWAN_CHOC_DSX-3-NODESTROYSUBBLOCK : The [chars] subblock named [chars] was not removed
Explanation A software error has occured, this message is displayed when IDB subblocks cannot be removed.
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.


CWAN_CONTAINER_ACCESS

%CWAN_CONTAINER_ACCESS-5-CWAN_VRF_MISMATCH : VRF of [chars] access does not match with [chars]
Explanation VRF of access interface does not match with that of associated container interface. Either container interface is deleted or VRF of container interface is changed
Recommended Action No action is required.


%CWAN_CONTAINER_ACCESS-5-CWAN_NO_CONTAINER : Associated container interface does not exist for [chars]
Explanation The container interface no longer exists for access interface.
Recommended Action No action is required.


CWAN_HA

%CWAN_HA-3-CCB_INIT_ERROR : Failed to initialize CCB list for slot [dec].
Explanation The High Availability component for WAN modules failed to properly initialize state information for the specified slot.
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.


%CWAN_HA-4-CCB_PLAYBACK_ERROR : CCB playback failed for slot [dec].
Explanation The High Availability component for WAN modules failed to synchronize some new state information for the specified slot.
Recommended Action Reload the standby supervisor module to force a fresh bulk synchronization. If this error recurs, LOG_STD_ACTION


%CWAN_HA-4-CCB_RECORD_ERROR : CCB record failed for slot [dec].
Explanation The High Availability component for WAN modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.


%CWAN_HA-3-IFCFG_INIT_ERROR : Failed to initialize Interface Configuration list for slot [int]/[int].
Explanation The High Availability component for WAN modules failed to properly initialize state information for the specified slot.
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.


%CWAN_HA-4-IFCFG_PLAYBACK_ERROR : Interface Configuration command [int] playback failed for slot [int]/[int].
Explanation The High Availability component for WAN modules failed to synchronize some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.


%CWAN_HA-4-IFCFG_RECORD_ERROR : Interface Configuration command [int] record failed for slot [int]/[int].
Explanation The High Availability component for WAN modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.


%CWAN_HA-3-IFCFG_NO_UNIQUE_KEY : No unique-key generator registered for interface configuration command [int].
Explanation The High Availability component for WAN modules is unable to properly synchronize state information for the current configuration.
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.


%CWAN_HA-3-IFCFG_CMD_NOT_UNIQUE : More than one command registered for unique-key generator for interface configuration command [int].
Explanation The High Availability component for WAN modules is unable to properly synchronize state information for the current configuration due to a conflict in command identifiers.
Recommended Action Copy the 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.


%CWAN_HA-4-IFCFG_DFLT_LIST_ERROR : For Interface Configuration command [int], default retval list search resulted [hex] for slot [int]/[int]
Explanation The High Availability component for WAN modules failed to synchronize some new state information for the specified slot.
Recommended Action LOG_STD_SH_CMD_ACTION(show platform redundancy if-config default-retvals)


%CWAN_HA-4-SRPSYNC : Slot [dec]: [chars]
Explanation An error occured while syncing SRP states from active RP to standby RP.
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.


%CWAN_HA-4-NOSRPBULKSYNC : Failed to [chars] SRP bulk data (slot=[dec], intf=[dec], type=[dec]), ret code [dec]
Explanation Some SRP-related state information failed to sync correctly from the active RP to the standby RP during the HA bulk-synchronization phase.
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.


%CWAN_HA-4-NOSRPSYNC : Failed to sync SRP packet (slot=[dec],intf=[dec]) to standby, HA_SYNC_STATUS=[dec]
Explanation Some SRP-related state information failed to sync correctly from the active RP to the standby RP when the configuration changed.
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.


%CWAN_HA-4-LTLSYNCFAIL : Failed to sync LTL data during [chars] for [chars] [int]: (slot=[dec],slotunit=[dec], if_num=[dec]) to standby (vlan=[int],hash=[int],ltl=[int])
Explanation Some LTL data did not sync correctly from active to standby RP
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.


%CWAN_HA-4-IFEVENT_INCRSYNCFAIL : [chars] for ifevent: [dec] with error: [dec]
Explanation Failed CWAN if-event incremental sync.
Recommended Action No action is required.


%CWAN_HA-4-IFEVENT_BULKSYNCFAIL : [chars] ifevent: [dec] error: [dec]
Explanation Failed CWAN if-event bulk sync.
Recommended Action No action is required.


%CWAN_HA-4-IFEVENT_UNEXPECTED_BULKTYPE : Unexpected value for bulk sync type ([dec]) received.
Explanation Received a unexpected type in bulk sync message.
Recommended Action No action is required.


CWAN_RP

%CWAN_RP-6-LC_PRESENT : [chars] in slot [int]
Explanation A WAN module was detected by the hardware.
Recommended Action No action is required.


%CWAN_RP-6-IMAGE_UPGRADE : Bootflash image upgrade [chars] for slot [int]/[int][chars]
Explanation The bootflash image on the WAN module has been or is being automatically upgraded.
Recommended Action No action is required.


%CWAN_RP-6-QUIESCE_FAIL : Quiesce failed for slot [int]/[int]
Explanation The RP failed to contact the WAN module during failover. The WAN module will be reset.
Recommended Action No action is required.


%CWAN_RP-6-UNQUIESCE_FAIL : Unquiesce failed for slot [int]/[int]. Error = [dec]
Explanation The RP failed to unquiesce the WAN module. The WAN module will be reset.
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/). Issue the show diagbus and show ipc status command to gather data that may help identify the nature of the error. 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.


%CWAN_RP-3-RESET_FAIL : The WAN module in slot [int] failed even after several resets
Explanation The WAN module in the slot specified in the error message did not boot successfully, even after multiple attempts.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CWAN_RP-3-POWER_CYCLE : Power cycling WAN module in slot [int]/[int]. [chars]
Explanation The WAN module is being power cycled.
Recommended Action No action is required.


%CWAN_RP-3-POWER_CYCLE_IMMINENT : The WAN module in slot [int]/[int] will be power cycled in [dec] seconds.
Explanation The WAN module in the slot specified in the error message will be power cycled in the amount of time specified in the error message
Recommended Action No action is required.


%CWAN_RP-3-BOOTFAIL : The WAN module in slot [int]/[int] failed to boot
Explanation The WAN module in the slot indicated in the error messages failed to boot and will be reset.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CWAN_RP-3-KEEPFAIL : The WAN module in slot [int]/[int] is not responding to keepalives
Explanation The WAN module was either reset or has crashed and will be reset.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CWAN_RP-3-SCPALLOCFAIL : Failed to allocate SCP packet [chars]
Explanation The RP failed to allocate a packet for communication with other slots in the chassis.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CWAN_RP-3-HV_ALLOCFAIL : [chars]: Failed to allocate a VLAN: [chars]
Explanation VLAN allocation failed for the stated reason.
Recommended Action First, power down any unused linecards. Next, delete any unused interfaces/subinterfaces, and any unused L2 VLANs from the VLAN database. Then wait for >3 minutes and retry.


%CWAN_RP-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars] with error [chars]
Explanation The RP failed to open a port for communication with a WAN module.
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.


%CWAN_RP-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The RP failed to allocate a buffer for communication with a WAN module.
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.


%CWAN_RP-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The RP failed to send a message to a WAN module.
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.


%CWAN_RP-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation A WAN module passed down a message that the RP software was not prepared to handle.
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.


%CWAN_RP-3-FOREVER : cmd [int] to [chars] (slot [int]/[int]) took [int]secs, done [hex]
Explanation A CCB command from the RP to a WAN module took longer than expected.
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.


%CWAN_RP-3-IFCFG_FOREVER : to [chars] (slot [int]/[int]) took [int]secs, ret_val [int]
Explanation A interface config command from the RP to a WAN module took longer than expected.
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.


%CWAN_RP-3-ERROR : NULL
Explanation This message can take many forms. It provides information about a software error.
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.


%CWAN_RP-6-CARDRELOAD : Module reloaded on slot [int]/[int]
Explanation The WAN module has booted.
Recommended Action No action is required.


%CWAN_RP-6-CARDRECONCILE : Module type changed on slot [int]/[int] from [int] to [int]
Explanation The WAN module has booted, and it has been detected that it is of a different type to the WAN module that was previously in this slot.
Recommended Action No action is required.


%CWAN_RP-3-LC_CRASHINFO : [chars] copied onto RP bootflash
Explanation The WAN module has crashed, and the crashinfo file has been copied onto the RP bootflash. The crashinfo filename indicates the module's slot. The file can be viewed using the more command.
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.


%CWAN_RP-3-LC_CRASHINFO_BLOCKED : Duplicate crashinfo upload from slot [int]/[int] blocked
Explanation The WAN module has crashed, and the crashinfo was not saved because the WAN module has already crashed recently.
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.


%CWAN_RP-3-LC_CRASHINFO_NOSPACE : Not enough space on RP bootflash for crashinfo from slot [int]/[int] ([int] bytes needed, [int] available)
Explanation The WAN module has crashed, and there is not enough space on the RP bootflash to store the crashinfo.
Recommended Action Free up space on the RP's bootflash by using the delete and squeeze commands.


%CWAN_RP-3-LC_CRASHINFO_IFSERR : Error [chars] [chars]: [chars] ([int])
Explanation The WAN module has crashed, and an error occured while trying to access the RP's bootflash to save the crashinfo.
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.


%CWAN_RP-3-LC_CRASHINFO_CORRUPT : Verification of crashinfo from slot [int]/[int] failed
Explanation The WAN module has crashed, and verification of the crashinfo it sent failed. The crashinfo has not been saved to RP bootflash.
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.


%CWAN_RP-3-LC_CRASHINFO_ERR : Unexpected error while receiving crashinfo from slot [int]/[int]
Explanation The WAN module has crashed, and an unexpected error occured while the crashinfo was being copied onto RP bootflash.
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.


%CWAN_RP-4-LCLOG_TOOLONG : Message too long from slot [int]/[int]: [int] bytes
Explanation The WAN module passed down a logger message that is too long for the RP to handle.
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.


%CWAN_RP-3-LCLOG_BADSEV : Invalid message severity from slot [int]/[int]: [int]
Explanation The WAN module passed down a logger message with an invalid severity level that the RP could not handle.
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.


%CWAN_RP-3-SLOTCACHE_SYNTAX : Error ([chars])!
Explanation The RP failed to parse the slot configuration string.
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.


%CWAN_RP-7-SLOTCACHE_CARDTYPE : parsed slot [dec], fci_type [dec]
Explanation Information parsed from the slot configuration string by the RP.
Recommended Action No action is required.


%CWAN_RP-7-SLOTCACHE_PATYPE : Bay [chars] has type [dec] ports([hex])
Explanation Information parsed from the slot configuration string by the RP.
Recommended Action No action is required.


%CWAN_RP-3-CHANGE_POSEIDON_NEGOTIATION : Unable to change negotiation. Failed to send message to slot [dec] port [dec]!
Explanation MSFC2 failed to send message to change negotiation to OSM-4GE-WAN-GBIC
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.


%CWAN_RP-3-OIRTWICE : Slot [int] OIR insertion/removal not paired up: [chars]
Explanation An internal OIR-related error occured for the specified WAN module.
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.


%CWAN_RP-3-IFCONFIG_ERR : Interface config failed on port [dec]/[dec], cmd [dec], retval [dec]
Explanation A configuration command sent from the system to a linecard 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.


%CWAN_RP-4-SEMAHOG : Process [dec] ([chars]) hogging [chars]! calling proc [dec] ([chars])
Explanation The RP waited too long for a reply to a command sent to a WAN module.
Recommended Action No action is required.


%CWAN_RP-4-IPCFAILED : IPC failed to send RPC message to WAN module
Explanation The RP failed to send an RPC message via IPC to a WAN module.
Recommended Action No action is required.


%CWAN_RP-3-PROCMSG : Process msg send failed for process[dec]
Explanation Process message send 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.


%CWAN_RP-3-MODULE_TYPE : cannot find FCI for module type [int] in slot [int]
Explanation An internal software error occurred while the system was detecting the module type for the module in the specified slot. The operation of the module will be affected.
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.


%CWAN_RP-4-MODULE_CONFIG_MISSING : configuration not available/not matching in startup-config for slot [int]
Explanation Some information regarding the configuration of the module in the specified slot is missing. Any configuration in the startup-config for the interfaces will not be applied. If the module in the specified slot is a FlexWAN, the missing configuration information is details of the Port Adapters in the FlexWAN module. This information is missing from the SLOTCACHE ROMMON variable.
Recommended Action If the module in the slot specified in the error message has not previously been inserted, it has no previous configuration; therefore, no action is required. If the configuration for the specified slot in the startup-config is suitable for the module in that slot, manually apply the configuration after the module has loaded by one of the following two methods. The second method requires a system reload: - Enter the copy nvram:startup-config system:running-config command to re-apply your saved configuration, then enter the no shutdown command on all interfaces whose configuration was rejected, then enter the copy system:running-config nvram:startup-config command to save your configuration and the WAN module slot configuration. - Enter the copy command to copy your startup-config to a temporary location (for example, copy nvram:startup-config bootflash:tmp-config), then enter the copy system:running-config nvram:startup-config command to update the WAN module slot configuration, then enter the copy command to restore the temporary copy of the startup-config (for example, copy bootflash:tmp-config nvram:startup-config), then enter the reload command to reload the system. After using the second method, you may wish to use the delete command to remove the temporary copy of the startup-config. To prevent this condition from recurring, ensure that the SLOTCACHE variable is updated whenever modules that require it (FlexWANs, but not OSMs) are moved between slots in the chassis. The SLOTCACHE variable is updated when the running-config is written to the startup-config using the copy system:running-config nvram:startup-config command (or the deprecated write memory equivalent). The two methods of restoring the configuration for the module shown above ensure the SLOTCACHE variable is updated.


%CWAN_RP-4-LL_UNKNOWN : Unknown linecard message: type [int], [chars]
Explanation Mismatch version between RP and LC, or internal message format mismatch
Recommended Action No action is required.


%CWAN_RP-3-GBIC_INSERTED : GBIC media type [dec] inserted in [chars]
Explanation A GBIC was inserted in the interface.
Recommended Action No action is required.


%CWAN_RP-3-GBIC_REMOVED : GBIC removed from [chars]
Explanation The GBIC was removed from the interface.
Recommended Action No action is required.


%CWAN_RP-1-TOO_MANY_VRF : Slot [int] can not support all the VRFs configured!
Explanation A non-Enhanced OSM card has been inserted into a router with more than 511 IP VRFs already configured. This router cannot support more than 511 IP VRFs if there is at least one non-Enhanced OSM in the system.
Recommended Action Replace the inserted non-Enhanced OSM with an Enhanced OSM, or decrease the number of IP VRFs to 511 or fewer.


%CWAN_RP-4-IFCFG_CMD_TIMEOUT : Interface configuration command ([hex]) to slot [int]/[int] timed out
Explanation The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command.
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.


%CWAN_RP-3-IFCFG_CMD_NOT_OWNER : Process '[chars]' waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process '[chars]'
Explanation A process on the RP sent an configuration command to the slot specified in the error message and a different process waited for the result. This could cause incorrect line card configuration states.
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.


%CWAN_RP-6-UPGRADE_COMPLETE : Slot [int]: ROMMON upgrade complete. Reset the card for the changes to take effect.
Explanation The ROMMON upgrade has completed successfully. The card must be reloaded for the changes to take effect
Recommended Action No action is required.


%CWAN_RP-3-UPGRADE_ERROR : Slot [int]: The ROMMON upgrade failed to complete.
Explanation An error occurred during the upgrade process.
Recommended Action If the module reloads successfully, please check the file and try again, otherwise please contact your Cisco technical support representative.


%CWAN_RP-6-AUX_FILE : Slot [int]: Found VPN-SM Firmware in File: [chars]
Explanation The file specified in the message was found and will be loaded by the VPN Services Module instead of the bundled image.
Recommended Action No action is required.


%CWAN_RP-6-ADF_FILE : Slot [int]: Using VPN-SM Upgrade File: [chars]
Explanation Booting specified upgrade image for VPN Services Module.
Recommended Action No action is required.


%CWAN_RP-6-OVERRIDE : Slot [int]: ...Overriding Intrinsic VPN-SM Firmware.
Explanation Specified image will be used instead of bundled image.
Recommended Action No action is required.


%CWAN_RP-1-OVERRIDE_MAC_INVALID : [chars] has invalid override-mac-address.
Explanation The user has issued an override-mac-address that does not match the mac address of the MSFC. This can occur if the config has been moved to new hardware or the mac-address command has been used on another interface. while the system automatically corrects this, the config needs to be adjusted.
Recommended Action Modify the override-mac-address command in the config.


%CWAN_RP-3-WAN_BRIDGING_CFG_EXCD : The number of VPLS/EoMPLS/Bridging/QinQ VCs exceeded the maximum([int]) supported by slot: [int] [chars]
Explanation The user has attempted to configure more VPLS, EoMPLS, Bridging VCs than the number that is supported by the platform.Review the configuration guidelines for the features that are being configured and reduce the number of VPLS, EoMPLS, Bridging to the number that is supported by the platform.
Recommended Action


%CWAN_RP-6-OUT_OF_RESOURCE : [chars] configuration has exceeded available internal resources.
Explanation The resources required for configuration are no longer available. They may have been acquired by another application.
Recommended Action If the requested resources have not been allocated to another application, call your technical support representative for further assistance.


%CWAN_RP-4-EMPTY_CWANBAYS : FLEXWAN in slot [dec] is empty. Please remove the Flexwan or insert it with atleast one PA
Explanation The FLEXWAN in the specified slot does not contain any Port Adapters.
Recommended Action The FLEXWAN should be removed as this is an unsupported configuration


%CWAN_RP-6-LC_RESET : The RP is reloaded, resetting slot [dec] is necessary. Please ignore errors if any, till the linecard comes up.
Explanation If the system is running Catalyst operating system software on the supervisor engine and Cisco IOS software on the MSFC, the WAN line cards that power up before the RP powers up will be reset automatically.
Recommended Action No action is required.


%CWAN_RP-3-FAILED_CONFIG : Failed to send line card config message [chars] for slot [int] port [int]
Explanation The RP could not send the specified configuration message to the line card
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.


%CWAN_RP-4-INVALID_UNIT : Invalid 7600 Unit: [[dec]/[dec]].
Explanation The specified 7600 slot/cpu beyonds the Chassis's limit.
Recommended Action Power cycle the redundant supervisor


%CWAN_RP-4-INCR_CFG_SYNC_FAIL : 7600 incremental running-config sync for [[dec]/[dec]] failed - [chars]([dec]) , Reload Standby
Explanation The specified 7600 incremental running-config sync failed
Recommended Action Power cycle the redundant supervisor


%CWAN_RP-4-CONFIG_MISMATCH : Irreconcilable Configuration difference between Active & Standby Supervisors due to OIR/Config Event for [dec]/[dec] -> Reloading Standby Supervisor to synchronize the configuration.
Explanation Unexpected configuration difference between Supervisors.
Recommended Action None. This is expected behavior.


%CWAN_RP-6-NOPWRISSU : Spa inserted in [chars] powered down because ISSU is in progress
Explanation The Spa insertion detected during ISSU upgrade process. It will be acted upon completion of the ISSU process.
Recommended Action No action is required.


%CWAN_RP-3-CWAN_IFCOM_RMI : Cwan ifcom RMI failure - [chars]([dec])
Explanation The CWAN IFCOM RMI Registration.
Recommended Action No action is required.


%CWAN_RP-6-COREDUMP_ENABLED : No heartbeat or keepalive resets will occur for slot [int] since coredump has been enabled
Explanation The module in the slot has crashed and is configured to generate a coredump file. The module will not be reset due to heartbeat and keepalive failures to ensure the coredump file generation is not prematurely terminated.
Recommended Action No action is required.


%CWAN_RP-6-SESS_LIMITS_CHASSIS : Exceeded max number of sessions supported. Supported limit 32000/chassis
Explanation Total number of subscriber sessions on this chassis exceeded the allowed limits. The supported limit is 32000 sessions per chassis
Recommended Action Avoid bringing up more number of sessions than the supported limit


%CWAN_RP-6-SESS_LIMITS_SIP400 : Exceeded max number of sessions supported on SIP400 LC in slot [dec]. Supported limit 8000/SIP400
Explanation Total number of subscriber sessions on SIP400 line card exceeded the allowed limits. The supported limits is, 8000 sessions per SIP400
Recommended Action Avoid bringing up more number of sessions than the supported limit


%CWAN_RP-6-SESS_LIMITS_ES_PLUS : Exceeded max number of sessions supported on ES+ LC in slot [dec]. Supported limit 16000/ES+
Explanation Total number of subscriber sessions on ES+ line card exceeded the allowed limits. The supported limit is 16000 sessions per ES+
Recommended Action Avoid bringing up more number of sessions than the supported limit


%CWAN_RP-6-SESS_LIMITS_PORT_GROUP : Exceeded max number of sessions supported on port-group Gig[dec]/[dec] to Gig[dec]/[dec].Supported limit 4000/port-group on ES+ LC
Explanation Total number of subscriber sessions on a single port-group in ES+ exceeded the allowed limits. The supported limit is 4000 sessions per port-group
Recommended Action Rearrange the subscribers on ES+ in such a way maximum number of sessions supported in a port-group is 4000.


%CWAN_RP-6-SESS_LIMITS_TEN_GIG_PORT : Exceeded max number of sessions supported on port Te[dec]/[dec]. Supported limit 8000/port on a Ten Gig port on ES+ LC.
Explanation Total number of subscriber sessions on a single Ten Gig port in ES+ exceeded the allowed limits. The supported limit is 8000 sessions per Ten Gig port.
Recommended Action Rearrange the subscribers on ES+ in such a way that maximum number of sessions per Ten Gig port is 8000


%CWAN_RP-6-PLAT_AVL_DEL_FAILED : Platform AVL delete failed for PPPoE session due to wrong slot id [dec]
Explanation Deletion of session related information from the AVL tree failed, because the slot number used to index it is wrong
Recommended Action No action is required.


CWAN_SLOT

%CWAN_SLOT-1-CF_NOBUF : Failed to get chkpt buffer, client = [dec]
Explanation Failed to get enough memory for checkpointing.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%CWAN_SLOT-1-CF_ADDFAILED : Failed to register chkpt client, client = [dec]
Explanation The CF 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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


CWAN_SPA

%CWAN_SPA-3-CREATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].
Explanation Failed to create a SPA object.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-SPA_CREATION_FAILURE : slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].
Explanation Failed to create a SPA object.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-FAILURE : [chars]: SPA failure - cause: [chars] ([hex]), recovery action: [chars] ([dec])
Explanation The SPA failed for the specified reason
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-NULL_VFT : [chars] virtual function table is not initialized. spaType=[hex]
Explanation A required function table is not initialized
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-NULL_VFUNC : [chars] vector is not initialized. spaType=[hex]
Explanation A required function vector is not initialized
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-MEM_ALLOC_ERROR : [chars]
Explanation Memory allocation error.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-NULL_SPA_PTR :
Explanation Pointer to a SPA object is NULL.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-INVALID_INDX_RANGE : index1= [dec], index2= [dec], maxIndex= [dec]
Explanation Invalid index range.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-INVALID_IF_INDEX : index= [dec], cardType=[hex], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec]
Explanation Index for the interface is not valid.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-INVALID_DATA_INSTANCE : interface type [chars], slot [dec] port [dec] vc [dec] : [chars]
Explanation Data required to support the interface is not available.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-NULL_ATM_DB : Unable to create ATM DB for [chars]
Explanation Data required to support the interface is not available.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-POWER_CYCLE : [chars] occurred on Shared Port Adapter [int]/[int]
Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-DIAG_CONFIG : [chars] did not complete [dec]/[dec]
Explanation An error has occured during diagnostic test.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWAN_SPA-3-INTR_THROTTLE : Interface [chars] MAC interrupt was throttled. Reenabling MAC interrupts via one sec spa process
Explanation MAC interrupt burst has occurred on one of the interfaces on the link daughtercard. The error message indicates that a throttling mechanism has been applied to this port to avoid any operational damage that could be provoked by this event. The cause for this problem could be bad transceiver, highly frenquent flapping optical signals, or mismatched path signals (e.g. receiving 10GBASE-W signal on 10GE LAN interface), etc.
Recommended Action Check the interface configuration and received signal characteristics. Also verify the XFP transceiver and receive signal path to determine the If this message recurs, LOG_STD_ACTION


CWAN_T3E3

%CWAN_T3E3-3-IFCONFIG_ERR : Interface config error on T3 port [dec]/[dec], cmd [dec], retval [dec]
Explanation A configuration command sent from the system to a linecard 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.


CWMP_DOWNLOAD

%CWMP_DOWNLOAD-5-CONFIG_SUCCESS : CWMP download: config file successfully downloaded and applied [chars]
Explanation The configuration apply operation with CWMP DOWNLOAD RPCmethod is success.
Recommended Action No action required.


%CWMP_DOWNLOAD-5-CONFIG_FAILURE : CWMP download: config apply operation failed [chars]
Explanation The configuration apply operation with CWMP DOWNLOAD RPCmethod is failed.
Recommended Action No action required.


CWRPSPA through DFP

CWRPSPA

%CWRPSPA-3-NO_HOST_INFO : slot [dec] subSlot [dec], spaType [hex]
Explanation Failed to get information about the host linecard.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWRPSPA-3-MAX_SPA : Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec])
Explanation The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2G


%CWRPSPA-3-SPA_NO_HOST_INFO : slot [dec] subSlot [dec], PID [chars]
Explanation Failed to get information about the host linecard.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWRPSPA-3-HWIDB_FAILURE : Creation: slot [dec] subSlot [dec] port [dec] vc [dec]
Explanation Failed to create an interface hwidb.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWRPSPA-3-INVALID_PORT_NUM : slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex]
Explanation The port number is out of range.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%CWRPSPA-4-SPA_RESP_CMD_MISMATCH : [chars]: Expecting response to interface configuration command [chars] but received response to command [chars].
Explanation An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message is repeatable, please LOG_STD_SH_TECH_ACTION


%CWRPSPA-6-CARDRELOAD : Module [int] reload due to SPA insert in [int]/[int].
Explanation When inserting a SPA on this carrier card, the card is reset.
Recommended Action No action is required.


%CWRPSPA-4-SPA_CMD_NO_RESP : [chars]: No response for interface configuration command [chars]
Explanation A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.
Recommended Action No action is required.


%CWRPSPA-5-OUT_OF_RESOURCES : [chars]: Unable to create [chars] due to SPA resource limitations.
Explanation The SPA was unable to create the requested resource due to limited hardware or software resources
Recommended Action No action is required.


CWS

%CWS-5-CWS_ON_PATH_DEBUG : NSH D-bit set for SIP: %CA DIP: %CA Src_node: [dec] Src_If_Id: [dec] Tenant_Id: [dec]
Explanation CTR has seen an NSH header with D-bit set
Recommended Action This message is for informational purposed only, and used for CWS Per Flowing debugging in the Cloud. LOG_STD_NO_ACTION


%CWS-5-CWS_INVALID_REF_COUNT : Invalid ref count [dec] in chunk [hex]
Explanation CTR has seen an invalid ref count in the NSH pool
Recommended Action This message is for informational purposed only, and used for CWS troubleshooting. LOG_STD_NO_ACTION


%CWS-3-IPC_INVALID_MSG : CWS-Invalid request [int]
Explanation Received Invalid message from CWS client proxy
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CWS-3-IPC_OPEN_REPLY : CWS-IPC Open Reply failed, request [chars]
Explanation For a request from CWS client proxy opening the reply buffer failed
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CWS-3-IPC_NORES : CWS-No space for the IPC reply, size [int], request [chars]
Explanation For a request from CWS client proxy it was not possible to allocate space for a reply for the specified size.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%CWS-3-IPC_SEND_FAILED : CWS-IPC [chars] [chars] send failed [int]
Explanation IPC message send failure
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.


%CWS-2-IPC_INIT_FAILED : CWS-IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CWS feature failed. This will cause the feature to not function.
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.


DAPR

%DAPR-4-INTERNAL_ERROR : [chars]
Explanation Internal error
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.


DAPR_BR

%DAPR_BR-5-STATUS : [chars]
Explanation Border-Router status
Recommended Action No action is required.


%DAPR_BR-5-RESET : reason: [chars]
Explanation Border-Router reset due to mentioned reason
Recommended Action No action is required.


%DAPR_BR-5-RM_ROUTE_INVALID : No route or route is via egress
Explanation Invalid route from Border-Router to Route-Manager
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.


%DAPR_BR-5-NBR_ROUTE_INVALID : Neighbor-BR [IP_address]
Explanation Invalid route to neighbor Border-Router
Recommended Action No action is required.


%DAPR_BR-5-NBR_TUNNEL_UPDOWN : Neighbor-BR [IP_address] tunnel [chars]
Explanation Status of tunnel to neighbor Border-Router
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.


%DAPR_BR-5-EGRESS_INTF_THRESHOLD_EXCEED : [chars] curr-util [int]%%, max-util %ld%%
Explanation DAPR egress interface utilization threshold exceeded
Recommended Action No action is required.


%DAPR_BR-5-EGRESS_INTF_NOT_VIABLE : [chars] curr-bw(kbps) [int] min-bw(kbps) %ld
Explanation DAPR egress interface not viable
Recommended Action No action is required.


%DAPR_BR-5-EGRESS_INTF_UPDOWN : [chars] [chars]
Explanation DAPR egress interface status
Recommended Action No action is required.


%DAPR_BR-5-INGRESS_INTF_UPDOWN : [chars] [chars]
Explanation DAPR ingress interface status
Recommended Action No action is required.


%DAPR_BR-4-PREFIX_LIMIT_EXCEEDED : curr [dec], max [dec]
Explanation DAPR RIB prefixes exceeded
Recommended Action No action is required.


%DAPR_BR-4-FLOW_LIMIT_EXCEEDED : curr [dec], max [dec]
Explanation DAPR Flows exceeded
Recommended Action No action is required.


%DAPR_BR-4-RMAP_LIMIT_EXCEEDED : curr [dec], max [dec]
Explanation DAPR route-map entries exceeded max allowed
Recommended Action No action is required.


DAPR_RM

%DAPR_RM-6-APP_RT_INSTALL : [chars] (BW:[dec]) [chars]
Explanation App route installed for flow-group
Recommended Action No action is required.


%DAPR_RM-6-APP_RT_DEL : [chars] (BW:[dec])
Explanation App route deleted for flow-group
Recommended Action No action is required.


%DAPR_RM-4-NO_VIABLE_PATH : [chars]
Explanation No viable path found for flow-group
Recommended Action No action is required.


%DAPR_RM-3-APP_RT_COMPUTE_FAILED : [chars]
Explanation App route compute failed for flow-group
Recommended Action No action is required.


%DAPR_RM-4-APP_REROUTE_FAILED : [chars]
Explanation App route re-compute failed for flow-group
Recommended Action No action is required.


%DAPR_RM-5-BR_STATUS : BR [chars] [chars]
Explanation Border-Router status on RM
Recommended Action No action is required.


%DAPR_RM-3-BR_RESET : BR [chars] reason: [chars]
Explanation RM reset the BR due to mentioned reason
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.


%DAPR_RM-6-BR_EVENT : BR [chars] event: [chars]
Explanation RM received event from BR
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.


%DAPR_RM-4-RIB_MISMATCH : route-count: old [dec] new [dec]
Explanation Mismatch of RIB database between BRs and RM
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.


%DAPR_RM-3-BR_REG_FAILED : BR [chars] reason: [chars]
Explanation BR Registration 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.


%DAPR_RM-6-RM_RESET : reason: [chars]
Explanation RM reset due to the mentioned reason
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.


%DAPR_RM-5-RM_STATUS : [chars]
Explanation Route-Manager status
Recommended Action No action is required.


%DAPR_RM-4-FLOW_EXP_PKT_INVALID_SEQ : BR [chars] last-seq [dec] curr-seq [dec]
Explanation Unexpected seq num in flow export pkt
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.


%DAPR_RM-3-FLOW_EXP_PKTS_MISSED : BR [chars] missed-pkts [dec]
Explanation Flow export packets missed
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.


%DAPR_RM-4-FLOW_DATA_RECS_IGNORED : BR [chars] reason: [chars]
Explanation Flow data records ignored
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.


%DAPR_RM-3-FLOW_INVALID_EGRESS : flow-group [chars]/[chars]/[dec], state [chars], uptime [dec]s, last-transition [dec]s, ingress-BR [chars], expected-egress [chars]/[dec], reported-egress [chars]/[dec]
Explanation Flow discovered from unexpected egress
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.


%DAPR_RM-4-FLOW_INVALID_INGRESS : flow-group [chars]/[chars]/[dec], state [chars], uptime [dec]s, last-transition [dec]s, ingress-BR [chars], egress-BR/intf [chars]/[dec], ingress-intf [chars]
Explanation Flow discovered from unexpected ingress
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.


%DAPR_RM-4-FLOW_MULTI_EGRESS : flow-group [chars]/[chars]/[dec], state [chars], uptime [dec]s, num-egress [dec], prev-egress [chars]/[dec], curr-egress [chars]/[dec]
Explanation New flow discovered from multiple egresses
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.


DATACORRUPTION

%DATACORRUPTION-1-DATAINCONSISTENCY : [chars], -PC= [chars]
Explanation
Recommended Action


%DATACORRUPTION-1-DATAINCONSISTENCY : [chars], -PC= 0x[chars]
Explanation Software has detected that some internal data structures may be corrupt. This may 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 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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


DATA_DESCR

%DATA_DESCR-3-HWIDB_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor hwidb)


%DATA_DESCR-3-SWIDB_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor swidb)


%DATA_DESCR-3-CTRLR_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor controller)


%DATA_DESCR-3-GENERIC_VIRTUAL_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor [hwidb|swidb])


%DATA_DESCR-3-GENERIC_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor [hwidb|swidb|controller])


%DATA_DESCR-3-GENERIC_ENCODE : Encode failure: [chars], descriptor type=[dec]
Explanation An internal data descriptor could not be encoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the 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.


%DATA_DESCR-3-DEFER_FAILURE : Defer failure on [chars] for descriptor [int]-[int]/[int]/[int]/[int]
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Copy the 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.


%DATA_DESCR-3-QUEUE_INTERNAL_ERROR : Internal error on data descriptor queue: [chars]
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Copy the 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.


%DATA_DESCR-3-ENTRY_EXPIRED : Found expired message entry for descriptor [int]-[int]/[int]/[int]/[int]
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Copy the 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.


DBAL

%DBAL-3-MQIPC_EVENTLOSS :
Explanation MQIPC event notifying of non-empty queue not delivered to DBAL
Recommended Action Report this occurance to Cisco TAC


%DBAL-3-MQIPC_PEEKERR :
Explanation MQIPC fails to peek and fetch a msg in DBAL
Recommended Action Report this occurance to Cisco TAC


%DBAL-3-MQIPC_ADVANCEERR :
Explanation MQIPC fails to advance to the next msg in DBAL
Recommended Action Report this occurance to Cisco TAC


%DBAL-4-DELAYED_BATCH :
Explanation DBAL batch with an extended lifetime. This may or may not be a problem depending on the circumstances
Recommended Action Collect log archive and show tech-support and report this occurance to Cisco TAC


%DBAL-4-LONG_EXEC_BATCH :
Explanation DBAL batch execution took an extended period of time. This may or may not be a problem depending on the circumstances
Recommended Action Collect log archive and show tech-support and report this occurance to Cisco TAC


%DBAL-3-MQIPC_READER_INIT_BY_TIMER :
Explanation MQIPC reader initialized by timer not chasfs watcher.
Recommended Action Report this occurance to Cisco TAC


%DBAL-3-BIPC_MSG_ALLOC_FAIL :
Explanation BIPC msg size beyond limit.
Recommended Action Report this occurance to Cisco TAC


DC

%DC-4-FILE_OPEN_WARNING : Not able to open [chars]
Explanation The device classifier did not find the default profile file or it may be corrupted. DC is working using built-in profiles.
Recommended Action Perform archive download using the tar bundle image to install the profile file in the flash. Reload the switch with the image to see the warning message is gone.


%DC-3-PATTERN_NOT_FOUND : [chars]
Explanation The device profiles file parsing failed. This indicates that the file may be corrupt. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reload the Device Profiles file to the flash and re-enable the device classifier


%DC-3-INCOMPATIBLE_PROFILE_VERSION : Incompatible version of Profile detected in [chars]. Expected version:[dec], Version found:[dec]
Explanation An incompatible profile version is detected. The device classifier feature will be operationally down.
Recommended Action Reload the expected version of device profiles file to the system and re-enable the device classifier


%DC-3-BUILTIN_INIT_FAIL : [chars]
Explanation Initilization of Device classifier Built-in database failed. So the device classifier will be operationally down.
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.


%DC-6-DEFAULT_INIT_INFO : [chars]
Explanation The default profiles are not loaded and those devices will not be classified. Device classifier will continue to work with built-in profiles.
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.


%DC-3-SM_INIT_FAIL : Device Classifier disabled. [chars] initialization failed
Explanation Registraton of Device classifier with SM failed. So the device classifier will be operationally down.
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.


%DC-3-OUI_INIT_FAIL : OUI Table initialization failed for [chars]
Explanation Loading of the OUI databae in Device classifier 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.


%DC-3-CHECK_INIT_FAIL : [chars]
Explanation Loading of the Checks databae in Device classifier 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.


%DC-3-DB_INIT_FAIL : Device Classifier disabled. [chars] initialization failed
Explanation Initilization of Device classifier Internal database failed So the device classifier will be operationally down.
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.


%DC-3-MAX_RULES_EXCEEDED : [chars].
Explanation The maximum number of rules that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reduce the number of rules in the device profiles file and reload it into the system and re-enable the device classifier


%DC-3-MAX_PROFILES_EXCEEDED : [chars].
Explanation The maximum number of profiles that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reduce the number of rules in the device profiles file and reload it into the system and re-enable the device classifier


%DC-3-MAX_OUI_EXCEEDED : [chars].
Explanation The maximum number of OUI codes that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reduce the number of rules in the device profiles file and reload it into the system and re-enable the device classifier


%DC-3-NO_MEM : [chars].
Explanation There is no memory left to allocate in the system The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Increase the memory size in the system and re-enable the device classifier


%DC-3-DC_DISABLED : [chars].
Explanation The device classifier is disabled due to an error condition encountered during initialization or parsing the profiles
Recommended Action The specified error message is logged. After the error condition is resolved re-enable the device classifier


%DC-3-SM_UPDATE : Failed to update [chars].
Explanation Internal error occured during device classification . This may cause the device to be unknown.
Recommended Action


%DC-3-SM_API : [chars] return [chars].
Explanation Internal error returned by Session Manager api.
Recommended Action


%DC-3-FILE_READ_ERROR : Error [chars] the profile file: [chars]
Explanation There was an error reading the profile file contents. The profiles in the errored file cannot be loaded into the device classifier.
Recommended Action


%DC-3-FILE_CHECKSUM : Checksum [chars] failed for the profile file: [chars]
Explanation Checksum computation or verification failed for the profiles file. The profiles in the errored file cannot be loaded into the device classifier.
Recommended Action


%DC-3-SM_GET : Failed to get [chars].
Explanation Internal error occured during communication with Session Manager. This may cause the show command not to display the device classification results.
Recommended Action


%DC-3-DISABLE_FAIL : Failed to disable DC.
Explanation Internal error occured trying to disable Device Classifier.
Recommended Action Please run the command: show macro auto monitor clients and try disabling the clients


%DC-3-ENABLE_FAIL : Failed to enable DC.
Explanation Internal error occured trying to enable Device Classifier.
Recommended Action Please check the previous DC error messages and take the relevant action


%DC-3-HRPC_SYNC : Error on member switch [dec], error_code = [dec]
Explanation Internal error occured while trying to sync Device Classifier.state
Recommended Action Please check the state of the stack members


DFP

%DFP-4-UKN_CON : Manager [IP_address] Service [chars] - Unknown connection state [int]
Explanation Unknown connection state processing DFP timer
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-BAD_SEND : Manager [IP_address]:[int] - Send failed
Explanation Sending a message to DFP Manager failed
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-SOCK_ERR : Manager [IP_address]: Service [chars] - Socket_recv error [dec]
Explanation Socket_recv error receiving message from DFP Manager
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-READ_ERR : Manager [IP_address]: Service [chars] - Too many read errors
Explanation Too many errors reading message header from DFP Manager
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-NO_PARSE : Manager [IP_address]: Service [chars] - Could not parse message
Explanation Could not parse message from DFP Manager
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-UNK_TYPE : Manager [IP_address]: Service [chars] - Unknown message type [int]
Explanation Message from DFP Manager has unknown type
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-ENQUEUE : Process enqueue failed: [chars]
Explanation An unexpected error occurred while enqueueing a DFP element
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-BAD_POINTER : [chars] Application did not set pointer
Explanation Application passed invalid pointer to DFP subsystem
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-NUM_TOO_LARGE : [chars] Application sent too many values
Explanation Application sent too many values to DFP subsystem
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-AGENT_NOT_FOUND : [chars] Service has not been registered with DFP.
Explanation No such service registered with DFP subystem.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-BAD_LISTEN : Service [chars] - Listen failed
Explanation Listen for DFP Manager failed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-NO_PROCESS_START : Could not start process for service [chars]
Explanation Could not start DFP Process for service %s
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-STRING_TOO_LONG : The string [chars] exceeds 15 characters - too long for service name.
Explanation The user input a service string that exceeds 15 characters
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-PACKET_TOO_SMALL : The DFP packet is too small from manager [IP_address] service [chars].
Explanation A DFP packet has been received that is too small.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-REPEAT_SERVICE_INIT : Service [chars] is already intialized, cannot re-initialize
Explanation The application has atempted to re-initialize a service
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-NO_QUEUE_REQUEST : Could not queue request for [chars] for service [chars]
Explanation Could not queue request to the DFP process for specific action
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-SUBSYS_NOT_UP : Service [chars] - attempted to register before DFP Subsytem is up.
Explanation Problem with order of subsystem initialization.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DFP-4-SECURITY_FAIL : [chars] security information in CASA packet from manager [IP_address] service [chars].
Explanation Security check failed.
Recommended Action Make sure all CASA/DFP systems are configured with the same password.


%DFP-4-BIND_FAIL : Failure binding port [int] to socket for service [chars].
Explanation Problem with call to socket bind.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


DHCP through DLC

DHCP

%DHCP-6-ADDRESS_ASSIGN : Interface [chars] assigned DHCP address [IP_address], mask [IP_address], hostname [chars]
Explanation The interface has been allocated an address via DHCP
Recommended Action This is an informational message. No action is required


%DHCP-5-RESTART : Interface [chars] is being restarted by DHCP
Explanation DHCP is restarting the interface.
Recommended Action No action is required.


%DHCP-3-HA_INIT_FAIL : Function [chars] in DHCP client failed to initialize: [chars]
Explanation A high availability related function in the DHCP client failed to initialize properly. If you are using a platform with a redundant processor or box-to-box redundancy, DHCP client settings may fail to be preserved if the main processor fails forcing use of the standby.
Recommended Action Please contact the TAC for assistance.


DHCPD

%DHCPD-2-NO_PROCESS : DHCP could not start its [chars] process.
Explanation DHCP could not start one of its processes.
Recommended Action Add more memory.


%DHCPD-2-SOCKET_ERROR : DHCP could not open UDP port [int].
Explanation DHCP could not open UDP port 67 (bootps).
Recommended Action Check if another application is using UDP port 67. If the port is available, add more memory.


%DHCPD-2-MALLOC_ERROR : There is inadequate memory for DHCP services.
Explanation DHCP could not allocate mandatory data structures.
Recommended Action Add more memory.


%DHCPD-2-RECVMSG_ERROR : Recvmsg failed unexpectedly. DHCP services have been terminated.
Explanation Reason for failure is unknown.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DHCPD-4-RELAY_ONLY : DHCP will run as a relay agent only.
Explanation DHCP could not start its database process. The server component has been disabled. Only the relay agent is active.
Recommended Action Add more memory.


%DHCPD-3-READ_ERROR : DHCP could not read bindings from [chars].
Explanation The DHCP server could not read bindings from the specified database agent.
Recommended Action Verify that the URL is correct and connectivity exists between the server and database agent. Check for a corrupt database file. The file must contain the *time* and *end* keywords. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the database transfer timeout.


%DHCPD-2-READ_DEADLOCK : DHCP has detected a deadlock condition (excessive read failures).
Explanation The DHCP server could not read bindings from any database agent. All read attempts have failed. To prevent a possible deadlock, the server has made all pool addresses available for assignment.
Recommended Action Verify that all URLs are correct and connectivity exists between the server and all database agents. Check for corrupt database files. All files must contain the *time* and *end* keywords. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the appropriate timeouts. Restart the DHCP server.


%DHCPD-3-WRITE_ERROR : DHCP could not write bindings to [chars].
Explanation The DHCP server could not write bindings to the specified database agent.
Recommended Action Verify that the URL is correct and connectivity exists between the server and database agent. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the database transfer timeout.


%DHCPD-4-PING_CONFLICT : DHCP address conflict: server pinged [IP_address].
Explanation The DHCP server has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, execute the command, clear ip dhcp conflict.
Recommended Action Resolve the misconfiguration. Clear the conflict from the DHCP database.


%DHCPD-4-DECLINE_CONFLICT : DHCP address conflict: client [chars] declined [IP_address].
Explanation The DHCP client has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, execute the command, clear ip dhcp conflict.
Recommended Action Resolve the misconfiguration. Clear the conflict from the DHCP database.


%DHCPD-4-HA_CONFIG_MISMATCH : DHCP pool [chars] configuration on Active is not matched on the Standby.
Explanation The software has detected a possible DHCP configuration mismatch on the Active and Standby units. Please verify that the configuration on the Standby matches that of the Active.
Recommended Action Resolve the misconfiguration.


%DHCPD-2-HA_INSUFFICIENT_BUFFER : DHCP insufficient buffer; information is not synced to Standby.
Explanation Reason for failure is unknown.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DHCPD-6-HIGH_UTIL : Pool [chars] is in high utilization state ([int] addresses used out of [int]). Threshold set at [int]%%.
Explanation The pool's utilization has exceeded the user configured high watermark.
Recommended Action Examine the DHCP pool and determine if the pool needs more IP addresses than currently allocated.


%DHCPD-6-LOW_UTIL : Pool [chars] is in low utilization state ([int] addresses used out of [int]). Threshold set at [int]%%.
Explanation The pool's utilization has fallen below the user configured high watermark.
Recommended Action Examine the DHCP pool and determine if the pool needs more IP addresses than currently allocated.


%DHCPD-3-HA_INIT_FAIL : Function [chars] in DHCP server failed to initialize: [chars]
Explanation A high availability related function in the DHCP server failed to initialize properly. If you are using a platform with a redundant processor or box-to-box redundancy, DHCP server data may fail to be preserved if the main processor fails forcing use of the standby.
Recommended Action Please contact the TAC for assistance.


%DHCPD-3-NO_AAA_CONTEXT : AAA configured, but no AAA context in [chars]
Explanation DHCP is attempting to use AAA to grant a DHCP lease, but no AAA context is associated with the binding
Recommended Action Please contact the TAC for assistance.


DHCPV6C

%DHCPV6C-3-NOSOCKET : Cannot create DHCPv6 client socket
Explanation Most likely no IP enabled on any interface or a resource problem within the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DHCPV6C-3-NOPACKET : Cannot setup or duplicate a socket packet
Explanation Most likely a resource problem within the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DHCPV6C-4-ZEROXID : Calculated DHCPv6 Lease Query xid is zero. Nothing is wrong, just drop the LQv6 msg
Explanation After multiple tries, the generated LQv6 msg xid is zero by accident. Just drop the LQv6 msg.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


DHCPV6R

%DHCPV6R-3-INVALID_USR_SRCADDR : Invalid user specified source-address [IPV6 address] idb [chars] in ipv6 dhcp relay CLI. Removing user specified invalid address from the CLI and auto-computing source with SAS.
Explanation Invalid source-address has been provisioned in the ipv6 relay destination CLI.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DHCPV6R-3-INVALID_USR_LINKADDR : Invalid user specified link-address [IPV6 address] idb [chars] in ipv6 dhcp relay CLI. Removing user specified invalid address from the CLI.
Explanation Invalid link-address has been provisioned in the ipv6 relay destination CLI.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


DHCPV6S

%DHCPV6S-3-NOPACKET : Cannot setup or duplicate a DHCPv6 server socket packet
Explanation Most likely a resource problem within the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DHCPV6S-3-DBNOTLOADED : Binding database not loaded
Explanation Fail to load the DHCPv6 binding database.
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.


%DHCPV6S-3-DBOPEN : Openning [chars]: [chars]
Explanation Fail to open a DHCPv6 binding database file.
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.


%DHCPV6S-3-DBWRITE : Writing file: [chars]
Explanation Fail to write a DHCPv6 binding database file.
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.


%DHCPV6S-3-DBREAD : Reading file: [chars]
Explanation Fail to read a DHCPv6 binding database file.
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.


DHCP_SNOOPING

%DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR : DHCP Snooping internal error, [chars]
Explanation A software sanity check failed in the DHCP Snooping process.
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/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%DHCP_SNOOPING-4-DHCP_SNOOPING_PVLAN_WARNING : DHCP Snooping configuration may not take effect on secondary vlan [dec]. [chars]
Explanation If private vlan feature is enabled, DHCP Snooping configuration on primary vlan will automatically propagate to all secondary vlans.
Recommended Action No action is required.


%DHCP_SNOOPING-4-IP_SOURCE_BINDING_PVLAN_WARNING : IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [chars]
Explanation If private vlan feature is enabled, IP source filter on primary vlan will automatically propagate to all secondary vlans.
Recommended Action No action is required.


%DHCP_SNOOPING-4-IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING : IP source binding is configured on non existing vlan [dec].
Explanation IP source binding is configured on a non existing vlan.
Recommended Action Please make sure that the L2 VLAN is configured before configuring a DHCP Snooping Binding. If you see this message even though L2 VLAN is configured in the system, please contact Cisco Technical Assistance Center.


%DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING : DHCP Snooping received [dec] DHCP packets on interface [chars]
Explanation DHCP Snooping detected a DHCP packet rate limit violation on a particular interface. The interface will be error disabled.
Recommended Action No action is required.


%DHCP_SNOOPING-4-AGENT_OPERATION_FAILED : DHCP snooping binding transfer failed. [chars]
Explanation This message provides the reason of failure when a database transfer has failed.
Recommended Action No action is required.


%DHCP_SNOOPING-4-STANDBY_AGENT_OPERATION_FAILED : DHCP snooping binding transfer failed on the Standby Supervisor. [chars]
Explanation This message provides the reason of failure when a database transfer has failed on the Standby Supervisor.
Recommended Action No action is required.


%DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N : DHCP snooping binding transfer failed([dec]). [chars]
Explanation This message provides the reason of failure when a database transfer has failed. This log message is rate limited.
Recommended Action No action is required.


%DHCP_SNOOPING-6-AGENT_OPERATION_SUCCEEDED : DHCP snooping database [chars] succeeded.
Explanation This message indicates that the given binding transfer has succeeded. This message is logged only once after some failure to indicate that the switch has recovered from failures.
Recommended Action No action is required.


%DHCP_SNOOPING-6-BINDING_COLLISION : Binding collision. [dec] bindings ignored
Explanation This message indicates that the given number of bindings from the database file have been ignored when the file is read. The bindings are ignored because the system has a binding for the given mac address and vlan combination by the time the switch read the ignored binding from the file.
Recommended Action No action is required.


%DHCP_SNOOPING-6-LEASE_EXPIRED : Lease Expired. [dec] bindings ignored.
Explanation This message indicates that the given number of bindings from the database file have been ignored when the file is read. The bindings are ignored because their lease has expired.
Recommended Action No action is required.


%DHCP_SNOOPING-6-INTERFACE_NOT_VALID : Interface not valid. [dec] bindings ignored.
Explanation This message indicates that the given number of bindings from the database file have been ignored when the file is read. The bindings are ignored because the interface indicated by the ignored binding either does not exist in the system or it's a router or dhcp snooping trusted port.
Recommended Action No action is required.


%DHCP_SNOOPING-6-VLAN_NOT_SUPPORTED : Vlan not supported. [dec] bindings ignored.
Explanation This message indicates that the given number of bindings from the database file have been ignored when the file is read. The bindings are ignored because the vlan indicated by the ignored binding no longer exists in the system.
Recommended Action No action is required.


%DHCP_SNOOPING-4-DHCP_SNOOPING_DATABASE_FLASH_WARNING : Saving DHCP snooping bindings to [chars] can fill up your device causing the writes of bindings to device, to fail.
Explanation Saving DHCP Snooping bindings to a flash file system such as bootflash or slot0 could cause the flash to fill up. Possible consequences include the long delay to regain console, write failures for database config, regular squeeze requirements, and reduced life of flash due to regular squeeze operations, etc.
Recommended Action Alternate destination locations for database agent include tftp, ftp, rcp, etc. Please see the help at command line for a complete list of options.


%DHCP_SNOOPING-6-PARSE_FAILURE : Parsing failed for [dec] bindings.
Explanation This message indicates that the given number of bindings from the database file have been ignored when the file is read. The bindings are ignored because of parsing failures.
Recommended Action No action is required.


%DHCP_SNOOPING-4-SSO_SYNC_ACK_ERROR : Error is encountered in processing acknowledgement for DHCP snooping binding sync, [chars]. ack message txn id: [hex]
Explanation This message indicates that there is an error in handling of the dhcp snooping binding sync acknowledgement. In most of these cases, the ack message is ignored.
Recommended Action No action is required.


%DHCP_SNOOPING-4-QUEUE_FULL : Fail to enqueue DHCP packet into processing queue: [chars], the queue is most likely full and packet will be dropped.
Explanation This message indicates that DHCP packets are coming into cpu at a much higher rate than DHCP snooping process can handle them. These unhandled DHCP packets will be dropped to prevent system from denial of service attack.
Recommended Action No action is required.


%DHCP_SNOOPING-4-NTP_NOT_RUNNING : NTP is not running; reloaded binding lease expiration times are incorrect.
Explanation If the DHCP snooping bindings are loaded by the DHCP snooping database agent and NTP is not running, then the calculated lease duration for the bindings will be incorrect.
Recommended Action Configure NTP on the switch to provide an accurate time and date for the system clock. Then disable and re-enable DHCP snooping to clear the bindings database.


%DHCP_SNOOPING-4-NTP_NOT_SYNC : NTP is not sync; reloaded binding lease expiration times are incorrect.
Explanation If the DHCP snooping bindings are loaded by the DHCP snooping database agent and NTP is not sync, then the calculated lease duration for the bindings will be incorrect.
Recommended Action Synchronize NTP on the switch to provide an accurate time and date for the system clock. Then disable and re-enable DHCP snooping to clear the bindings database.


%DHCP_SNOOPING-4-DHCP_SNOOPING_RATE_LIMIT_EXCEEDED : The interface [chars] is receiving more than the threshold set
Explanation This message indicates that a DHCP packets are coming into cpu at a much higher rate than the specified threshold.
Recommended Action No action is required.


%DHCP_SNOOPING-5-DHCP_SNOOPING_UNTRUSTED_PORT : [chars] drop message on untrusted port, message type: [chars], MAC sa: [enet]
Explanation DHCP Snooping discovers certain types of DHCP message not allowed on the untrusted interface, some host maybe trying to act as a DHCP server.
Recommended Action No action is required.


%DHCP_SNOOPING-5-DHCP_SNOOPING_NONZERO_GIADDR : [chars] drop message with non-zero giaddr or option82 value on untrusted port, message type: [chars], MAC sa: [enet]
Explanation DHCP Snooping discovers DHCP packet with certain option value not allowed on the untrusted port, some host maybe trying to act as a DHCP relay or server.
Recommended Action No action is required.


%DHCP_SNOOPING-5-DHCP_SNOOPING_FAKE_INTERFACE : [chars] drop message with mismatched source interface, the binding is not updated, message type: [chars], MAC sa: [enet]
Explanation DHCP Snooping discovers some host is trying to act as another host on the network and trying to carry out a DOS attack on that host.
Recommended Action No action is required.


%DHCP_SNOOPING-5-DHCP_SNOOPING_MATCH_MAC_FAIL : [chars] drop message because the chaddr doesn't match source mac, message type: [chars], chaddr: [enet], MAC sa: [enet]
Explanation DHCP Snooping enables match-source-mac validation and the check is failed. There maybe a malicious host trying to carry out a DOS attack on the DHCP server.
Recommended Action No action is required.


%DHCP_SNOOPING-4-OPTION82_INSERTION_FAIL : The interface [chars] is not able to insert opt82 into the packet because of insufficient space in the packet
Explanation This message indicates that a DHCP packet was not inserted with opt82 data due to insufficient space in the packet.
Recommended Action No action is required.


%DHCP_SNOOPING-4-INVALID_RELEASE_OR_DECLINE_PKT : The interface [chars] has received a DHCP Release/Decline packet with no existing binding entry for it
Explanation This message indicates that a DHCP Release/Decline packet was received with no corresponding binding entry.
Recommended Action No action is required.


DIALER

%DIALER-2-NOSWIDB : No software interface associated with hw interface [chars]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)


%DIALER-2-CIRCUITCOUNT : Dialer count 0 on [chars]
Explanation An internal software error occurred.
Recommended Action LOG_STD_SH_TECH_ACTION


%DIALER-2-NULLPTR : Unexpected null pointer in [chars]
Explanation An internal software error occurred.
Recommended Action LOG_STD_SH_TECH_ACTION


%DIALER-6-BIND : Interface [chars] bound to profile [chars]
Explanation This is a status message indicating that a dialer interface has been bound to a dialer profile.
Recommended Action LOG_STD_NO_ACTION


%DIALER-6-UNBIND : Interface [chars] unbound from profile [chars]
Explanation This is a status message indicating that a dialer interface has been unbound to a dialer profile.
Recommended Action LOG_STD_NO_ACTION


%DIALER-4-MTU_WARNING : Current MTU setting of [dec] on [chars] is being overwritten by setting of [dec] defined by [chars].
Explanation This is a warning message indicating that an interface setting is changed based on a dialer rotary group memebership.
Recommended Action LOG_STD_NO_ACTION


%DIALER-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action LOG_STD_ACTION


DIALER_LIST_PROXY

%DIALER_LIST_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization 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.


%DIALER_LIST_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
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.


%DIALER_LIST_PROXY-3-PROXY_MEM_EXTEND_FAILED : IPC subtype: [dec]
Explanation add more memory 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.


%DIALER_LIST_PROXY-3-PROXY_IPC_FAILED : [chars] failed to send ipc rc: [int]
Explanation send ipc 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.


%DIALER_LIST_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
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.


%DIALER_LIST_PROXY-3-PROXY_ALLOC_PAK_FAILED : alloc pak failed, MSGDEF_LIMIT_MEDIUM
Explanation alloc pak 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.


DIALPEER_DB

%DIALPEER_DB-3-ADDPEER_MEM_THRESHOLD : Addition of dial-peers limited by available memory
Explanation The available memory does not permit the addition of more dial-peers.
Recommended Action Increase the processor memory in order to be able to add more dialpeers.


%DIALPEER_DB-6-ADDPEER_WARNING : Addition of too many dial-peers may affect performance
Explanation The number of dial-peers is high. This will have an effect on the dial-peer lookup time, resulting in longer call setup time.
Recommended Action Use the minimum number of dial-peers necessary for your numbering plan.


%DIALPEER_DB-3-ADDPEER_PLATFORM_LIMIT : Addition of dial-peers limited by platform
Explanation This platform does not permit the addition of more dial-peers.
Recommended Action Reduce the number of dial-peers in your numbering plan.


%DIALPEER_DB-3-NOMAP : Could not load dnis-map [chars] url=[chars] errno=[dec]=[chars]
Explanation Could not read in the dnis-map
Recommended Action Check that map exists on the server, and is readable.


%DIALPEER_DB-3-DP_MALLOC_FAIL : Could not allocate memory in [chars] for tag [dec]
Explanation Ran out of memory
Recommended Action Observe why memory is exhausted


%DIALPEER_DB-6-FB_ENTRY_NOT_CREATED : Could not create probe for tag [dec]
Explanation Fallback cache full
Recommended Action Increase Fallaback cache size


%DIALPEER_DB-3-DIALPEER_ACCOUNTING : Connections for dial-peer [dec] is negative. Resetting connections to 0.
Explanation Active Connections for dial-peer is negative.
Recommended Action Verify if dial-peers were removed with active calls associated to them and added back while the calls were still connected.


%DIALPEER_DB-3-NODEPMAP : Could not load e164-pattern-map [dec] url=[chars] errno=[dec]=[chars]
Explanation Could not read in the e164-pattern-map
Recommended Action Check that map exists on the server, and is readable.


%DIALPEER_DB-3-NOE164TRANSURL : Could not load e164-translation [dec] url=[chars] error=[chars]([dec])
Explanation Could not get the voice class e164-translation url data file
Recommended Action Check that url data file exists on the server, and is readable.


DLC

%DLC-3-BADPARAM : Function [chars]: value [hex] passed in parameter [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. 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.


%DLC-2-NOMEMORY : no memory for [chars]
Explanation There was not enough free memory to complete the operation.
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.


%DLC-3-WPUTERR : unknown port type [hex]
Explanation An internal software error occurred.
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.


%DLC-3-INVPCEP : Close Station, invalid P_CEP
Explanation An internal software error occurred.
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.


DLEP_MSG through DOT1X

DLEP_MSG

%DLEP_MSG-4-CONNECT_ERROR : TCP connect to Radio [IP_address] failed via [chars]. Error code: [chars]
Explanation TCP Connect to IP address and port of the Radio failed.
Recommended Action Take action based on the error code shown. Reconfigure correct IP address and port, if necessary.


DLEP_SET_MSG

%DLEP_SET_MSG-6-DLEP_HEARTBEAT_THRESHOLD : new Threshold value configured will have effect for the new sessions only not for the currently running DLEP sessions
Explanation If the threshold value should be updated at Router side, it must be configured before the Radio launch
Recommended Action Once the DLEP session is established and if you want to change the threshold value kill the Radio and reconfigure the dlep on Router interface and make the Radio UP to see the updated threshold value


%DLEP_SET_MSG-6-DLEP_NBR_ACTIVITY_TIMEOUT : new nbr-activity-timeout value configured will have effect for the new sessions only not for the currently running DLEP sessions
Explanation If the nbr-activity-timeout value should be updated at Router side it must be configured before the Radio launch
Recommended Action Once the DLEP session is established and if you want to change the nbr-activity-timeout value kill the Radio and reconfigure the dlep on Router interface and make the Radio UP to see the updated value


%DLEP_SET_MSG-6-DLEP_NBR_DOWN_ACK_TIMEOUT : new nbr-down-ack-timeout value configured will have effect for the new sessions only not for the currently running DLEP sessions
Explanation If the nbr-down-ack-timeout value should be updated at Router side,it must be configured before the Radio launch
Recommended Action Once the DLEP session is established and if you want to change the nbr-down-ack-timeout value kill the Radio and reconfigure the dlep on Router interface and make the Radio UP to see the updated Value


%DLEP_SET_MSG-6-DLEP_PEER_TERMINATE_ACK_TIMEOUT : new peer-terminate-ack-timeout value configured will have effect for the new sessions only not for the currently running DLEP sessions
Explanation If the peer-terminate-ack-timeout value should be updated Router side it must be configured before the Radio launch
Recommended Action Once the DLEP session is established and if you want to change the peer-terminate-ack-timeout value, kill the Radio and reconfigure the dlep on Router interface and make the Radio UP to see the updated value


DLINK

%DLINK-3-BAD_QELEM : Bad queue elem - [hex]: flink [hex], blink [hex] , flink->blink [hex], blink->flink [hex]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DLINK-3-NULL_QELEM : Null queue elem
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


DLSWC

%DLSWC-3-NODLSW : [chars] [dec]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-IDMGR : [chars]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-NOPEER : [chars]
Explanation A data-link switching system error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DLSWC-3-BADPEEROP : bad peer op in peer_to_core [dec]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-BADSSPHDR : bad ssp hdr in proc ssp - [chars] = [hex]
Explanation A Silicon Switch Processor (SSP) header received from the remote peer contains errors in one of the fields.
Recommended Action If the remote peer is a nonCisco router, confirm that it supports the DLSw RFC 1795 standard.


%DLSWC-3-BADCLSIIND : [chars] Invalid indication [chars], [chars]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-BADCLSIRET : [chars] Invalid ret code ([hex]) [chars], [chars]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-BADCLSICNF : [chars] Invalid confirm [chars] [chars]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-BADCLSI : [chars] primitive not valid for dlsw [chars] [chars]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-BADCLSISAP : [chars] Bad clsi SAP id = [hex] [chars]
Explanation A data-link switching system error occurred.
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.


%DLSWC-3-SENDSSP : SSP OP = [dec]([chars]) [chars] to [chars] [chars]
Explanation A Silicon Switch Program (SSP) frame was sent to the remote peer.
Recommended Action No action is required.


%DLSWC-3-RECVSSP : SSP OP = [dec]([chars]) [chars] from [chars]
Explanation A Silicon Switch Program (SSP) frame was received from the remote peer.
Recommended Action No action is required.


DLSWMasterSlave

%DLSWMasterSlave-3-DLSWMS : [chars]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.


%DLSWMasterSlave-3-DLSWMSCSM : [chars], [chars]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.


%DLSWMasterSlave-3-DLSWMSFSM : [chars]: [chars] from [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.


%DLSWMasterSlave-3-DLSWMSTX : [chars]: [chars] to [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.


%DLSWMasterSlave-3-DLSWMSDLX : [chars] [hex] from [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.


%DLSWMasterSlave-3-DLSWMSSAP : [chars]: [chars]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.


%DLSWMasterSlave-3-DLSWMSRCV : [chars] from [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.


DLSWP

%DLSWP-3-PGENERAL : [chars]
Explanation A general error condition was detected as described in the message text. This error should not cause any network problems unless it happens repeatedly.
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.


%DLSWP-3-PNOMEM : No memory to [chars]
Explanation The router ran out of system memory for operation, as described in the message text. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your Cisco technical support representative about memory requirements for a specific image.


%DLSWP-3-PPASSIVE : passive open failed from [IP_address]([dec]) -> [dec]
Explanation The system does not have enough main memory (RAM) for TCP to allocate the data structures required to accept an incoming TCP connection. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your Cisco technical support representative about memory requirements for a specific image.


%DLSWP-3-PBADVALUE : [chars]: invalid [chars] [dec]
Explanation A bad parameter value was passed to function chars1 - invalid parameter chars2 with value. This error should not cause any network problems unless it happens repeatedly.
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.


%DLSWP-3-PCAPMISMATCH : [chars]: [chars]
Explanation Priority keyword was used on one router but not on the other. The priority keyword is an option on the DLSW remote peer definition. If priority keyword is used on one router, it must be used on the other.
Recommended Action If you wish to use prioritization, use it on both routers.


%DLSWP-3-PLFCHANGE : [chars] [dec]; [chars]
Explanation The largest frame size configured in the DLSW remote peer definition is being changed because the MTU size configured on the interface, used by DLSW, is less than the configured value of the largest frame on DLSW remote peer definition. The largest frame size is being changed to that configured on the interface.
Recommended Action If you wish to use this largest frame size for DLSW, increase the MTU on the interface to a value larger than the configured largest frame size.


%DLSWP-3-PNOCOOKIE : uninitalized peer [chars] from [IP_address]([dec]) to [IP_address]([dec])
Explanation DLSw received a packet on an uninitialized peer connection.
Recommended Action Verify configuration and DLSw peer status on both routers.


%DLSWP-5-PEERUPDOWN : [chars] [chars]
Explanation A DLSW peer is either connected or disconnected
Recommended Action None, informational message only.


%DLSWP-3-PEERFAILURE : [chars] [chars]
Explanation A DLSW peer failed: - keepalive failure, dlsw between cisco peers is sending a peer keepalive by default every 30 sec. After missing 3 consecutive keepalives the peer is taken down. - We are not promiscuous, Rej conn from peer a.b.c.d The local dlsw peer is not configured for promiscuous and we receive a request to open a dlsw peer for which we have no corresponding dlsw remote peer statement. - received tcp fini, dlsw peer code has received a tcp fini from the underlaying tcp subsystem. To obey the tcp fini dlsw wring bring down the peer connection for which the tcp fini was received.
Recommended Action - keepalive failure Check end to end connectivity between the DLSW peers - We are not promiscuous, Rej conn from peer a.b.c.d correct your configuration. - received tcp fini, Check the underlaying tcp connection between the two dlsw peers.


DMI

%DMI-3-MEM_UNAVAIL :
Explanation Insufficient system memory is available to perform the DMI action.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DMI-5-CONFIG_I :
Explanation A change to the running configuration was performed using NETCONF or RESTCONF.
Recommended Action Informational only. No action required.


%DMI-5-SYNC_COMPLETE :
Explanation An external change (outside of NETCONF or RESTCONF) has been detected thus, the running-config has been sent to Confd to
Recommended Action Informational only. No action required.


%DMI-3-SYNC_FAIL :
Explanation An external change (outside of NETCONF or RESTCONF) has been detected. An attempt to send the running-config to Confd to repopulate its data store has failed.
Recommended Action Force a full sync via the 'sync-from' RPC.


%DMI-5-SYNC_START :
Explanation An external change (outside of NETCONF or RESTCONF) has been detected thus, the running-config will be sent to Confd to
Recommended Action Informational only. No action required.


%DMI-5-SYNC_NEEDED :
Explanation A configuration change that may trigger additional changes has been detected thus, the running-config will be sent to Confd to
Recommended Action Informational only. No action required.


%DMI-3-DIFF_FAIL :
Explanation An operating system error occurred while performing a diff of two files and redirecting to a third file.
Recommended Action Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help.


%DMI-3-SAVE_FAIL :
Explanation An operating system error occurred while opening or writing to a diagnostic file.
Recommended Action Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help.


%DMI-3-CLI_ENGINE_WRITE_FAIL :
Explanation A CLI engine error occurred while send a command line to the network element's CLI parser
Recommended Action Enter the command line in question manually via the network element's console or vty. If successful, stop and restart netconf-yang and retry.


%DMI-3-INTERNAL_ERROR :
Explanation An unexpected internal error has occurred.
Recommended Action Consult man page for impacted area to interpret the error code and string.


%DMI-3-DIR_EXISTS :
Explanation A existing file is conflicting with a directory name.
Recommended Action Remove or rename the offending file.


%DMI-3-CDB_START_FAIL :
Explanation A Confd error has occurred attempting to open the DMI data store.
Recommended Action Stop and restart netconf-yang.


%DMI-3-CDB_SET_NAMESPACE_FAIL :
Explanation A Confd error has occurred attempting to set a specific model namespace for accessing the DMI data store.
Recommended Action Stop and restart netconf-yang.


%DMI-3-CDB_READ_FAIL :
Explanation A Confd error has occurred attempting to read a specific model path from the DMI data store.
Recommended Action Download the model in question from the network element and verify the path exists. Update the model if needed.


%DMI-3-CLI_ENGINE_CONNECT_FAIL :
Explanation DMI cannot connect to the network element in order to interact with its CLI parser.
Recommended Action Check the CLI engine protocol settings.


%DMI-2-CDB_MAN_SUB_FAIL :
Explanation A Confd error has occurred attempting to mark DMI as a mandatory subscriber
Recommended Action Stop and restart netconf-yang.


%DMI-2-NESD_CREATE_FAIL :
Explanation Either an out-of-memory condition has been encountered, or the DMI CLI engine cannot connect to the network element.
Recommended Action Stop and restart netconf-yang.


%DMI-4-SUB_READ_FAIL :
Explanation A Confd error has occurred attempting to read the subscription socket.
Recommended Action DMI will reset. No action necessary.


%DMI-3-CDB_SYNC_FAIL :
Explanation A Confd error has occurred attempting to sync the subscription socket.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-CDB_ABORT_FAIL :
Explanation A Confd error has occurred attempting to abort a transaction.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-4-CONTROL_SOCKET_CLOSED :
Explanation The control socket connection to Confd has closed unexpectedly.
Recommended Action DMI will reset. No action necessary.


%DMI-2-CONTROL_SOCKET_ERROR :
Explanation The control socket connection to Confd has returned an error.
Recommended Action DMI will reset. No action necessary.


%DMI-2-WORKER_SOCKET_CLOSED :
Explanation The worker socket connection to Confd has closed unexpectedly.
Recommended Action DMI will reset. No action necessary.


%DMI-2-WORKER_SOCKET_ERROR :
Explanation The worker socket connection to Confd has returned an error.
Recommended Action DMI will reset. No action necessary.


%DMI-2-NOTIFICATION_READ_FAIL :
Explanation An attempt to read an event from the Confd notification socket failed.
Recommended Action DMI will reset. No action necessary.


%DMI-2-CLI_CHANNEL_CLOSED :
Explanation The CLI engine event channel to the network element closed unexpectedly.
Recommended Action DMI will reset. No action necessary.


%DMI-3-CLI_GEN_FAIL :
Explanation A Confd error has occurred when requesting the CLI change set for a transaction.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-4-CLI_ROLLBACK_WARN :
Explanation A Confd induced CLI transaction was aborted and during the rollback CLIs, an error was returned
Recommended Action Confirm that the network element's running configuration is in the original state before the failed transaction


%DMI-4-NETCONF_TRACE_WARN :
Explanation An error occurred saving the Netconf trace information.
Recommended Action Please enable netconfTraceLog in Confd. Check for free file system space.


%DMI-4-CONFD_ROLLBACK_WARN :
Explanation An error occurred saving the Confd rollback information.
Recommended Action Please enable rollback in Confd. Check for free file system space.


%DMI-4-DIAG_WARN :
Explanation An error occurred saving DMI message diagnostics.
Recommended Action Check for free file system space.


%DMI-2-NESD_INIT_FAIL :
Explanation The nesd daemon failed to initialize.
Recommended Action Stop and restart netconf-yang.


%DMI-2-SD_INIT_FAIL :
Explanation The syncfd daemon failed to initialize.
Recommended Action Stop and restart netconf-yang.


%DMI-2-NESD_PREHOOK_INIT_FAIL :
Explanation The nesd daemon failed to initialize its component-specific add-ons.
Recommended Action Stop and restart netconf-yang.


%DMI-2-MAAPI_CONNECT_FAIL :
Explanation A Confd error has occurred attempting to connect via MAAPI socket.
Recommended Action Stop and restart netconf-yang.


%DMI-3-MAAPI_SAVE_FAIL :
Explanation A Confd error has occurred attempting to save a model path via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-MAAPI_START_USER_FAIL :
Explanation A Confd error has occurred attempting to start a user session via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-MAAPI_START_TRANS_FAIL :
Explanation A Confd error has occurred attempting to start a transaction via MAAPI.
Recommended Action via MAAPI. Stop and restart netconf-yang.


%DMI-3-MAAPI_DELETE_FAIL :
Explanation A Confd error has occurred attempting to delete a model path via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-MAAPI_LOAD_FAIL :
Explanation A Confd error has occurred attempting to load commands to a model path via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-MAAPI_LOAD_FILE_FAIL :
Explanation A Confd error has occurred attempting to load commands from a file via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-MAAPI_APPLY_TRANS_FAIL :
Explanation A Confd error has occurred attempting to apply a transaction via MAAPI.
Recommended Action via MAAPI. Stop and restart netconf-yang.


%DMI-3-MAAPI_FINISH_TRANS_FAIL :
Explanation A Confd error has occurred attempting to finish a transaction via MAAPI.
Recommended Action via MAAPI. Stop and restart netconf-yang.


%DMI-3-MAAPI_LOCK_FAIL :
Explanation A Confd error has occurred attempting to lock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-MAAPI_UNLOCK_FAIL :
Explanation A Confd error has occurred attempting to unlock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-SYNC_LOCK_FAIL :
Explanation A Confd error has occurred attempting to lock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-3-SYNC_UNLOCK_FAIL :
Explanation A Confd error has occurred attempting to unlock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.


%DMI-4-CLI_UNLOCK_FAIL :
Explanation An IOS parser error has occurred attempting to unlock the parser lock.
Recommended Action Retry NETCONF operation.


%DMI-4-CLI_LOCK_FAIL :
Explanation An IOS parser error has occurred attempting to obtain a configuration parser lock.
Recommended Action Retry NETCONF operation.


%DMI-2-MAAPI_WAIT_FAIL :
Explanation Confd did not initialize properly.
Recommended Action Back out any recent yang model updates. Stop and restart netconf-yang.


%DMI-2-CONFD_INIT_FAIL :
Explanation Confd did not initialize properly.
Recommended Action Back out any recent yang model updates. Stop and restart netconf-yang.


%DMI-2-CONFD_CONNECT_FAIL :
Explanation A DMI application cannot connect to Confd via a particular socket type.
Recommended Action Stop and restart netconf-yang.


%DMI-2-CONFD_SUB_FAIL :
Explanation A DMI application cannot subscribe for changes to a particular yang model.
Recommended Action Back out any recent model updates. Stop and restart netconf-yang.


%DMI-2-CONFD_SUB_DONE_FAIL :
Explanation A DMI application cannot complete subscriptions for changes to yang models.
Recommended Action Back out any recent model updates. Stop and restart netconf-yang.


%DMI-2-CONFD_CB_REG_FAIL :
Explanation A DMI application cannot register a particular callback with Confd.
Recommended Action Stop and restart netconf-yang.


%DMI-2-CONFD_CB_REG_DONE_FAIL :
Explanation A DMI application cannot complete callback registration with Confd.
Recommended Action Stop and restart netconf-yang.


%DMI-2-NES_RESET_FAIL :
Explanation The network element synchronizer daemon cannot reset in order to recover from a critical error.
Recommended Action Stop and restart netconf-yang.


%DMI-2-SD_RESET_FAIL :
Explanation The syncfd daemon cannot reset in order to recover from a critical error.
Recommended Action Stop and restart netconf-yang.


%DMI-2-CHG_VRF_FAIL :
Explanation The DMI application failed to set the correct virtual routing and forwarding network thus, it cannot communicate with Confd.
Recommended Action Stop and restart netconf-yang.


%DMI-3-CLI_ENGINE_EVENT_FAIL :
Explanation DMI cannot retrieve its CLI engine event in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-CLI_ENGINE_LOG_LVL_FAIL :
Explanation DMI cannot set its CLI engine logging level.
Recommended Action Stop and restart DMI.


%DMI-3-CLI_ENGINE_READ_FAIL :
Explanation DMI cannot read its CLI engine results in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-CLI_ENGINE_READ_EVENT_FAIL :
Explanation DMI cannot read its CLI engine event in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang


%DMI-3-CLI_ENGINE_POLL_FAIL :
Explanation DMI cannot read its CLI engine results in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang


%DMI-4-CLI_ENGINE_STATE_FAIL :
Explanation DMI cannot read its CLI engine state.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang


%DMI-3-CLI_ENGINE_VTY_CREATE_FAIL :
Explanation The DMI CLI engine cannot create a VTY instance.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DMI-3-CLI_ENGINE_VTY_OPEN_FAIL :
Explanation The DMI CLI engine cannot open a VTY.
Recommended Action Free up available VTY resources by closing unused VTYs. Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang


%DMI-4-CLI_ENGINE_RC_FAIL :
Explanation DMI cannot read CLI engine return code for the particular command.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang


%DMI-3-MODEL_RESTORE_FAIL :
Explanation DMI failed to restore the model '%s' from the network element's running configuration to the DMI data store.
Recommended Action Check the netconf-yang section of the network element's running configuration. If populated with non-default values, stop and restart netconf-yang. If problem continues, restore the model's configuration in question via Netconf


%DMI-3-VTY_NUM_FAIL :
Explanation DMI must keep track of its tty number it uses to send command lines to the network element's parser in order to avoid triggering its own sync events
Recommended Action Check that the 'show users line' command line is working


%DMI-3-CLI_ENGINE_VTY_TIMEOUT_FAIL :
Explanation DMI disables the VTY timeout for the network element synchronizer's VTY connection to ensure its number cannot be silently claimed by other VTY sessions.
Recommended Action None required


%DMI-3-CLI_ENGINE_RECONNECT_FAIL :
Explanation The CLI engine has lost its connection to the network element and attempted to reconnect with an error occurred.
Recommended Action Stop and restart netconf-yang.


%DMI-4-CLI_ENGINE_ENABLE_FAIL :
Explanation DMI cannot enter privileged mode when communicating with the network element's CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. Check AAA settings for the Netconf/Restconf user account.


%DMI-3-CLI_ENGINE_CONNECT_LOSS :
Explanation DMI has lost connection to the network element.
Recommended Action No action necessary.


%DMI-3-SYNC_CLI_FILTER_CREAT_FAIL :
Explanation DMI cannot create a CLI filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-SYNC_CLI_FILTER_MODE_FAIL :
Explanation DMI cannot set the mode for its CLI filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-SYNC_CLI_FILTER_ADD_FAIL :
Explanation DMI cannot add a CLI filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-SYNC_SYSLOG_FILTER_CREAT_FAIL :
Explanation DMI cannot create a syslog filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-SYNC_SYSLOG_FILTER_ADD_FAIL :
Explanation DMI cannot add a syslog filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-SYNC_MODULE_CHECK_ADD_FAIL :
Explanation DMI cannot add a module up check to monitor for module up status.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-SYNC_OIR_FILTER_CREAT_FAIL :
Explanation DMI cannot create an OIR filter to monitor for OIR induced configuration changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-SYNC_OIR_FILTER_ADD_FAIL :
Explanation DMI cannot add an OIR filter to monitor for OIR induced configuration changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-INIT_SYNC_FAIL :
Explanation DMI failed to synchronize the network element's running configuration with the DMI data store upon DMI startup.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.


%DMI-3-LOAD_SCHEMAS_FAIL :
Explanation DMI failed to load Confd schemas for yang model namespaces.
Recommended Action Back out any recent yang model updates. Stop and restart netconf-yang.


%DMI-3-VTY_SERVER_CREAT_FAIL :
Explanation Failed to create VTY server utility instance for DMI operational data use.
Recommended Action Stop and restart netconf-yang.


%DMI-3-VTY_SERVER_START_FAIL :
Explanation Failed to start VTY server utility instance for DMI operational data use.
Recommended Action Stop and restart netconf-yang.


%DMI-2-VTY_SERVER_RESET_FAIL :
Explanation Failed to reset VTY server utility in order to recover from critical error.
Recommended Action Stop and restart netconf-yang.


%DMI-3-INVALID_PRESERVE_PATH :
Explanation A non-existent XPath has been specified to be preserved during complete syncs.
Recommended Action Remove the offending path from the /native/cisco-ia/preserve-ned-path list.


%DMI-7-GEN_DEBUG :
Explanation A debug message for syslog consumption. For troubleshooting wihtout btrace
Recommended Action Not applicable


%DMI-2-NETCONF_SSH_CRITICAL :
Explanation A critical message from the NETCONF SSH daemon.
Recommended Action Not applicable


%DMI-3-NETCONF_SSH_ERROR :
Explanation An error message from the NETCONF SSH daemon.
Recommended Action Not applicable


%DMI-6-NETCONF_SSH_INFO :
Explanation An informational message from the NETCONF SSH daemon.
Recommended Action Not applicable


%DMI-3-INVALID_REG_EXP :
Explanation An invalid regular expression has been specified which will not compile.
Recommended Action Remove the offending regular expression from the specified model or via o CLI\.


%DMI-3-EDIT_REJECTED :
Explanation A NETCONF running datastore edit request occurred simultaneously with a database synchronization operation. Thus, the request has been rejected.
Recommended Action Retry the NETCONF edit again later.


%DMI-5-AUTH_PASSED :
Explanation A user authenticated successfully and was authorized for a service.
Recommended Action No action is required.


%DMI-5-AUTHENTICATION_FAILED :
Explanation A user failed to authenticate.
Recommended Action No action is required.


%DMI-5-AUTHORIZATION_FAILED :
Explanation A user was not authorized for the requested service.
Recommended Action No action is required.


%DMI-3-AUTH_TIMED_OUT :
Explanation A AAA request timed out.
Recommended Action Check connectivity to the configured AAA server.


%DMI-3-MAAPI_KILL_SESSION_FAIL :
Explanation A parser lock timeout has occurred, and DMI attempted to kill the session holding the global lock, but failed.
Recommended Action Kill the NETCONF user session holding the global lock manually.


%DMI-3-NETCONF_KILL_SESSION :
Explanation A parser lock timeout has occurred, and DMI has killed the corresponding NETCONF session.
Recommended Action Establish a new NETCONF session. Adjust your application to hold global locks for a shorter interval -- seconds, not minutes


%DMI-5-NACM_INIT :
Explanation The running-config under the /nacm tree has been set to its initial configuration.
Recommended Action No action is required.


%DMI-5-INITIALIZED :
Explanation process has initialized.
Recommended Action Informational only. No action required.


%DMI-5-ACTIVE :
Explanation process is in steady state.
Recommended Action Informational only. No action required.


%DMI-5-RESET :
Explanation process internal state reset.
Recommended Action Informational only. No action required.


%DMI-4-CLI_LOCK_OVERRIDE :
Explanation An IOS parser lock has been cleared to avoid conflict with NETCONF session.
Recommended Action Retry CLI operation after NETCONF session completes.


%DMI-4-CDB_MAINTENANCE_MODE :
Explanation A Cisco-support only NETCONF mode has been enabled as a recovery mechanism for an out-of-sync condition.
Recommended Action Disable this mode in order to return the device to normal NETCONF operation.


DNET

%DNET-4-MAPCON : Map entry [dec].[dec] conflicts with adjacency to [dec].[dec]
Explanation Your DECnet configuration is incorrect. A host that is specified as nonlocal is present on your local network.
Recommended Action Correct the configuration. Call your technical support representative if you need assistance.


%DNET-3-HEARSELF : Hello type [hex] for my address from [dec].[dec] via [chars]
Explanation The system is receiving its own DECnet packets. Either a serial line is looped back or another host with the same DECnet address is already present on the LAN.
Recommended Action Check the serial lines (if present) and the DECnet configuration.


%DNET-3-NOMEMORY : Insufficient memory for DECnet accounting entry
Explanation The traffic information for a particular pair of DECnet nodes cannot be recorded due to a low memory condition.
Recommended Action LOG_STD_REDUCE_ACTION


%DNET-4-DUPENTRY : Duplicate DECnet Accounting List Entry for nodes [dec].[dec] - [dec].[dec]
Explanation A synchronization problem has occurred whilst a new transit DECnet Accounting List Entry was being added and a duplicate entry has been found.
Recommended Action LOG_STD_SH_CMD_ACTION(show decnet accounting)


DOSFS

%DOSFS-5-DIBERR : [chars] [chars]
Explanation The system cannot boot a image from the Flash disk because the Device Information Block is different. The Flash disk can be read by the router, but will require formatting by the router before an image can be booted from it.
Recommended Action Follow any instructions provided in the error message. Before storing a image in the Flash disk and trying to boot from this device, enter the format command to format the flash disk from the router. Then copy the desired image to the Flash disk and then boot from this device.


%DOSFS-3-RESETERR : [chars] [chars]
Explanation disk could not be reset while the system is initiated reload. This will cause a transient disk error, disk timeout error, when the ROMMON initialization code tries to reads the DIB. This is a transient error and the system will be able to access the disk and continue normal operation.
Recommended Action No action is required.


%DOSFS-5-DFS_CLOSE_ERR : Error during close of the file [chars]. [chars]
Explanation An error occured during a file close operation.
Recommended Action Enter the fsck filesystem prefix: command to check and attempt to repair the disk. If this does not fix the problem, format the disk.


%DOSFS-4-DFS_FSCK_ERR : Error while running fsck on the file [chars].
Explanation Fsck is running in a loop while walking through the cluster chain of a file and has aborted.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.


DOT1X

%DOT1X-5-SUCCESS :
Explanation Dot1x authentication was successful.
Recommended Action No action is required.


%DOT1X-5-FAIL :
Explanation Dot1x authentication was unsuccessful.
Recommended Action No action is required.


%DOT1X-5-RESULT_OVERRIDE :
Explanation Authentication result was overridden
Recommended Action No action is required.


%DOT1X-3-PROC_START_ERR :
Explanation The system failed to create the Dot1x process.
Recommended Action Restart Dot1x process by entering dot1x system-auth-control command. If this message recurs, Reload the device.


%DOT1X-3-UNKN_ERR :
Explanation The Dot1x process cannot operate due to an internal system error.
Recommended Action Reload the device/process


%DOT1X-4-MEM_UNAVAIL :
Explanation Insufficient system memory is available to perform the Dot1x Authentication.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DOT1X-4-INFO_EAPOL_PING_RESPONSE :
Explanation An EAPOL ping was sent out on this port to determine 802.1x readiness of the client attached. An EAPOL response has been received by the device such as a PC.
Recommended Action No action required.


%DOT1X-5-IGNORE_LARGER_EAPOL :
Explanation Targetted EAPOL packet size is larger than mtu size of the port on which client is connected and hence ignoring the packet to be sent out
Recommended Action Configure AAA server to fragement eap-method data so that EAPOL size is smaller than interface MTU size


DOT1X_SWITCH through DSPDUMP

DOT1X_SWITCH

%DOT1X_SWITCH-4-PROC_START_ERR : Unable to start dot1x switch process.
Explanation The system failed to create the Dot1x switch process.
Recommended Action Reload the device


%DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND : Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VTP database.
Recommended Action Make sure the VLAN exists and is not shutdown or use another VLAN.


%DOT1X_SWITCH-5-ERR_VLAN_RSPAN : Attempt to assign RSPAN VLAN [chars] to 802.1x port [chars]. 802.1x is incompatible with RSPAN AuditSessionID [chars]
Explanation An attempt was made to assign a Remote SPAN VLAN to an 802.1x port. Remote SPAN should not be enabled on a VLAN in which ports are configured with 802.1x enabled.
Recommended Action Either disable Remote SPAN configuration on the VLAN OR disable 802.1x on all the ports in this VLAN.


%DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN : Data VLAN [chars] on port [chars] cannot be equivalent to the Voice VLAN AuditSessionID [chars]
Explanation An attempt was made to assign a data VLAN to an 802.1x port that is the same as the voice VLAN.
Recommended Action Change either the Voice VLAN or the access/802.1x assigned VLAN on the interface so they are not equal anymore. This will cause the authentication to proceed normally on the next retry.


%DOT1X_SWITCH-5-ERR_VLAN_INTERNAL : Attempt to assign internal VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is used internally and cannot be assigned to this port.
Recommended Action Update the configuration not to use this VLAN.


%DOT1X_SWITCH-5-ERR_VLAN_RESERVED : Attempt to assign reserved VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port.
Recommended Action Update the configuration not to use this VLAN.


%DOT1X_SWITCH-5-ERR_VLAN_INVALID : Attempt to assign invalid VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is out of range and cannot be assigned to this port.
Recommended Action Update the configuration to use a valid VLAN.


%DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN : Attempt to assign invalid secondary VLAN [chars] to PVLAN host 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign a non-secondary VLAN to a PVLAN host 802.1x port.
Recommended Action Change the mode of the port so that it is no longer a PVLAN host port or use a valid secondary VLAN.


%DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN : Attempt to assign primary VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign a primary VLAN to an 802.1x port, which is not allowed.
Recommended Action Update the configuration to use a different VLAN.


%DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND : Attempt to assign VLAN [chars], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shutdown.
Recommended Action Make sure the primary VLAN exists and is not shutdown. Also verify that the private VLAN is associated with a primary VLAN.


%DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT : Attempt to assign VLAN [chars] to routed 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign a VLAN to a routed 802.1x port, which is not allowed.
Recommended Action Change the mode of the port so that it is no longer a routed port or change the configuration so that no VLAN is assigned.


%DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT : Attempt to assign VLAN [chars] to promiscuous 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign a VLAN to a promiscuous 802.1x port, which is not allowed.
Recommended Action Change the mode of the port so that it is no longer a promiscuous port or change the configuration so that no VLAN is assigned.


%DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID : Attempt to assign secondary VLAN [chars] to non-PVLAN host 802.1x port [chars] AuditSessionID [chars]
Explanation An attempt was made to assign a secondary VLAN to a port that is not a PVLAN host port, which is not allowed.
Recommended Action Change the mode of the port so that it is configured as a PVLAN host port or use a different VLAN that is not configured as a secondary VLAN.


%DOT1X_SWITCH-5-ERR_SPAN_DST_PORT : Attempt to assign VLAN [chars] to 802.1x port [chars], which is configured as a SPAN destination AuditSessionID [chars]
Explanation An attempt was made to assign a VLAN to an 802.1x port which is configured as a SPAN destination port
Recommended Action Change the SPAN configuration so that the port is no longer a SPAN destination port or change the configuration so that no VLAN is assigned.


%DOT1X_SWITCH-5-ERR_ADDING_ADDRESS : Unable to add address [enet] on [chars] AuditSessionID [chars]
Explanation The authenticated host's address could not be added. This is likely because either the TCAM is full or the address exists as a secure address on another port.
Recommended Action If the TCAM is full, clear some dynamic addresses to make room for the host's address. If the host's address is secured on another port, manually remove it from that port.


%DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE : Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port AuditSessionID [chars]
Explanation Multi-Domain Authentication host mode cannot activate if the configured Data VLAN on a port is the same as Voice VLAN.
Recommended Action Change either the Voice VLAN or the access VLAN on the interface so they are not equal anymore. This will cause Multi-Domain authentication to activate.


DPSS

%DPSS-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for DPSS
Explanation DPSS Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION


%DPSS-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for DPSS
Explanation DPSS Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION


%DPSS-3-DPSS_INIT_FAILED : DPSS [chars] Register failed
Explanation DPSS Initialization of registration failed.
Recommended Action LOG_STD_ACTION


%DPSS-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper DPSS software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%DPSS-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper DPSS 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 monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%DPSS-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the DPSS feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the DPSS feature will not function. LOG_STD_ACTION


DRIP

%DRIP-3-DRIPFAIL : DRIP: Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_ACTION


%DRIP-6-DRIP_CONFLICT : DRIP conflict with CRF [dec].
Explanation A DRIP conflict has occured. The virtual ring or pseudo ring's CRF is being re-used in the network.
Recommended Action Make sure that the CRF vlanid of the virtual ring and the pseudo ring is unique in the network.


DRP

%DRP-3-SUBNETTED : unable to determine metric for [IP_address], [IP_address] subnetted
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.


%DRP-7-NOROUTE : no route for destination [IP_address]
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.


%DRP-3-NOWRITE : unable to send response to [IP_address]:[dec]
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.


%DRP-3-MULTICOMMAND : multiple DRP commands encountered
Explanation Multiple DRP commands were found in a single DRP packet.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DRP-3-NOSOCKET : Unable to open socket
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.


DS0_DUMP

%DS0_DUMP-3-MALLOC_PROC_MEM : Process memory allocation failed for PCM capture: size [hex].
Explanation The free process memory in the system is not enough for the PCM capture session.
Recommended Action Refer to the user guide for the estimation of process memory needed for PCM capture. Do 'show memory' to make sure there is enough memory before PCM capture starts.


%DS0_DUMP-3-INIT_FAIL : DS0 PCM Tracer is not initialized.
Explanation DS0 dump process can't be initialized.
Recommended Action Make sure there is enough memory in the system and IOS is properly installed.


%DS0_DUMP-3-PCM_TRACER_RUNNING : A previous session of PCM capture is in progress.
Explanation Can't start new PCM capture session since there is one going on now.
Recommended Action Make sure there is no other PCM capture session going on before start the new capture.


%DS0_DUMP-3-PCM_TRACE_NOT_SUPPORTED : PCM Trace/ds0 dump is not supported on slot [int].
Explanation Can't execute this command on the slot number specified.
Recommended Action Refer to the user guide for which slot ds0 dump is supported on.


%DS0_DUMP-3-PCM_TRACE_START_FAILED : PCM capture start failed.
Explanation Failed to start the ds0 dump in the TDM driver.
Recommended Action Make sure there is no hardware defect and there is no other ds0 dump/test tdm dump session going on.


%DS0_DUMP-6-PCM_TRACE_STARTED : PCM capture started.
Explanation
Recommended Action


%DS0_DUMP-6-PCM_TRACE_RSP_STARTED : module start PCM capture for [dec]/[dec]/[dec]/[dec]
Explanation
Recommended Action


%DS0_DUMP-6-PCM_TRACE_RSP_STOPPED : module stop or complete PCM capture for [dec]/[dec]/[dec]/[dec]
Explanation
Recommended Action


%DS0_DUMP-6-PCM_TRACE_RSP_ERROR : module fail and terminate the pcm capture for [dec]/[dec]/[dec]/[dec]
Explanation
Recommended Action


%DS0_DUMP-6-PCM_TRACE_RSP_UNKNOWN : module send unkonwn pcm capture response [dec] for [dec]/[dec]/[dec]/[dec]
Explanation
Recommended Action


%DS0_DUMP-6-PCM_TRACE_STOPPING : stopping PCM capture
Explanation
Recommended Action


%DS0_DUMP-6-PCM_TRACE_STOP_FAILED : failed to stop PCM capture
Explanation
Recommended Action


%DS0_DUMP-6-PCM_TRACER_NOT_RUNNING : no PCM capture is in progress.
Explanation
Recommended Action


DSA_PROXY

%DSA_PROXY-3-PROXY_MEM_EXTEND_FAILED :
Explanation Extending memory failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IPC_INVALID_PARAM :
Explanation IPC Invalid parameters.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-4-PROXY_IPC_INVALID_MSG :
Explanation Invalid IPC message
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_DEBUG_REG_FAILED :
Explanation DSA Conditional Debugging registration failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IPC_SEND_CLEAR_FAILED : [dec]
Explanation DSA clear ip cache failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IPC_SEND_UNINIT_FAILED : [dec]
Explanation DSA Send UNINIT IPC failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IPC_SEND_INIT_FAILED : [dec]
Explanation Send initialization IPC failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_UNINIT_FAILED :
Explanation UNINIT cleanup failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IPC_ALLOC_FAILED :
Explanation Generating IPC failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_CHUNK_CLEAR_FAILED :
Explanation Chunk clear failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_CHUNK_CREATION_FAILED :
Explanation Chunk creation failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_LOW_MEM_REQ_FAILED :
Explanation Send low mem IPC failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_RETURN_MEM_FAILED :
Explanation return mem IPC failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_NO_IP_POOL_MEM :
Explanation IP Cache pool is not allocated.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_TBL_INIT_FAILED :
Explanation IP Cache table init failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IP_CLEAR_FAILED : [dec]
Explanation IP Cache clear failed.
Recommended Action LOG_STD_ACTION


%DSA_PROXY-3-PROXY_IP_CLEAR_TO_FAILED : [dec] [dec]
Explanation IP Cache clear failed.
Recommended Action LOG_STD_ACTION


DSM

%DSM-6-SESSION_DATABASE_FAILED : Cannot create DSM session database
Explanation Failed to create DSM session.
Recommended Action Check the size of free memory to make sure there is enough memory.


%DSM-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The session continued but may have experienced problems.
Recommended Action Contact your technical support representative, include the full text of the error message.


%DSM-3-NOEVENT : no free event structure available from [chars] for DSM message
Explanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Contact your technical support representative, include the full text of the error message.


%DSM-3-DSPALARM : channel [chars], DSP ID [hex]: status=[hex] message=[hex] text=[chars]
Explanation The DSP reported a fatal error. All sessions on the DSP were dropped and a DSP reload was attempted.
Recommended Action Contact your technical support representative, include the full text of the error message.


%DSM-3-DSP_TIMEOUT : DSP timeout on channel [chars], event [hex]: DSP ID=[hex]: [chars]
Explanation Timeout on DSP response.
Recommended Action The DSP has been automatically reset. If problem persists, contact your technical support representative


%DSM-3-INTERNAL : Internal Error : [chars]
Explanation DSM Internal error
Recommended Action Contact your technical support representative


DSMP

%DSMP-6-SESSION_DATABASE_FAILED : Cannot create DSMP session database
Explanation Failed to create DSMP session.
Recommended Action Check the size of free memory to make sure there is enough memory.


%DSMP-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The session continued but may have experienced problems.
Recommended Action Contact your technical support representative, include the full text of the error message.


%DSMP-3-NOEVENT : no free event structure available from [chars] for DSMP message
Explanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Contact your technical support representative, include the full text of the error message.


%DSMP-3-DSPALARM : Alarm on DSP [chars]: status=[hex] message=[hex] text=[chars]
Explanation The DSP reported a fatal error. All sessions on the DSP were dropped and a DSP reload was attempted.
Recommended Action Contact your technical support representative, include the full text of the error message.


%DSMP-3-DSP_TIMEOUT : DSP timeout on DSP [chars]: event [hex], [chars]
Explanation Timeout on DSP response.
Recommended Action The DSP has been automatically reset. If problem persists, contact your technical support representative


%DSMP-3-INTERNAL : Internal Error : [chars]
Explanation DSMP Internal error
Recommended Action Contact your technical support representative


%DSMP-4-WARNING : Warning : [chars]
Explanation Resource temporarily not available
Recommended Action Contact your technical support representative if condition lasts


%DSMP-3-INVALID_EVENT : Unhandled event: current state:[chars] event:[chars]
Explanation The event is not handled in the DSMP gateway state machine specification
Recommended Action Contact your technical support representative


%DSMP-3-SUBSYS_UNINITIALIZED : Internal Error : [chars]
Explanation DSMP Subsystem not initialized
Recommended Action Contact your technical support representative


%DSMP-3-PRG_ERROR : Programming Error : [chars]
Explanation Progaramming error in DSMP subsys
Recommended Action Contact your technical support representative


%DSMP-3-NOLICENSE : [chars]:No License available, Tivan Recording could not be Triggered
Explanation There are no recording license remaining in the license pool
Recommended Action Check your configuration for smart license availability


DSP

%DSP-5-UPDOWN : DSP [dec] is [chars]
Explanation DSP device changed state up/down
Recommended Action No action is required.


%DSP-5-DNLD : DNLD started for device [dec]
Explanation DSP bootloader DNLD starte
Recommended Action No action is required.


%DSP-3-FIRMWARE_VER_INFO : Downloading streamware... for device [dec]. DSP firmware(ver:[int].[int]) contained in image has different version from the firmware(ver:[int].[int]) in harddisk or bootflash
Explanation DSP firmware version check
Recommended Action No action is required.


%DSP-3-DSP_DNLD : DSP device [dec] DNLD process exited. Trying to recover DSP device by rebooting the DSP
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.


%DSP-3-TIMER : [chars] timer expired for DSP [dec]
Explanation DSP timer has expired
Recommended Action No action is required.


%DSP-3-DSP_WATCHDOG : DSP device [dec] is not responding. Trying to recover DSP device by reloading
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.


%DSP-3-DSP_ALARM : DSP device [dec] is not responding. Trying to recover DSP device by reloading
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.


%DSP-3-DSP_KEEPALIVE : DSP device [dec] is not responding. Trying to recover DSP device by reloading
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.


DSPDUMP

%DSPDUMP-5-DUMPSTART : DSP [dec] ([hex]) in slot [dec] starting dump
Explanation The DSP resource is beginning crash dump collection
Recommended Action No action is required.


%DSPDUMP-5-RX_CONTROL_DROP : DSP [dec] in slot [dec] Rx Control Message Dropped by DSP
Explanation The DSP has reported that a Rx Control Message was dropped
Recommended Action No action is required.


%DSPDUMP-5-TX_CONTROL_DROP : DSP [dec] in slot [dec] Tx Control Message Dropped by DSP
Explanation The DSP has reported that a Tx Control Message was dropped
Recommended Action No action is required.


DSPFARM through DYNCMD

DSPFARM

%DSPFARM-3-ERROR : Errors on DSPFARM module [chars]
Explanation Errors on DSPFARM module
Recommended Action Check sh dspfarm all


%DSPFARM-4-WARNING : Warning on DSPFARM module [chars]
Explanation Warning on DSPFARM module
Recommended Action Check sh dspfarm all


%DSPFARM-4-NOTICE : Failure on DSPFARM module [chars]
Explanation Failure on DSPFARM module
Recommended Action Check sh dspfarm


%DSPFARM-4-INFO : Info on DSPFARM module [chars]
Explanation Info on DSPFARM module
Recommended Action Check sh dspfarm


DSPRM

%DSPRM-5-UPDOWN : DSP [dec] in slot [dec], changed state to [chars]
Explanation The DSP resource changed state.
Recommended Action No action is required.


%DSPRM-5-UP_DOWN : DSP [dec] in subslot [chars], changed state to [chars]
Explanation The DSP resource changed state.
Recommended Action No action is required.


%DSPRM-5-KEEPALIVE : DSP [dec] in slot [chars], NOT RESPONDING - auto restart([dec] times)
Explanation The DSP failed the background keep-alive test.
Recommended Action No action is required.


%DSPRM-3-INSUFFICIENT : Insufficient DSP resources for timeslot [dec] on port [chars]
Explanation The configuration requires more DSP resources than are available.
Recommended Action Change the configuration to specify fewer used timeslots. Install additional DSP resources to allow more complex configurations.


%DSPRM-3-INSUFFICIENT_DSP : voice-port : [chars] Not initialized due to insufficient DSP resources
Explanation More DSP resources are needed to initialize the analog voice-port
Recommended Action Install additional DSP resources to allow voice-port initialization


%DSPRM-5-DSPFAIL : DSP [dec] in slot [chars], is in the failed state
Explanation The DSP entered the FAILED state due to alarm indications.
Recommended Action Replace the DSP resource.


%DSPRM-5-DSPMSGFAIL : Failed to get dsprm msg for msg id [chars]
Explanation Unable to get dsprm control message
Recommended Action No action is required.


%DSPRM-5-JUKEBOX : Jukebox transmit overlay resp [dec] on slot [chars], failed
Explanation The Jukebox received failed response code.
Recommended Action


%DSPRM-5-JUKEBOX_UPDOWN : DSP Jukebox([dec]) in slot [chars], changed state to [chars]
Explanation The DSP JUKEBOX changed state.
Recommended Action No action is required.


%DSPRM-5-SETCODEC : Configured codec [dec] is not supported with this dsp image.
Explanation Codec negotiation failed.
Recommended Action


%DSPRM-2-DSPALARM : Received alarm indication from dsp ([dec]/[dec]). Resetting the DSP.
Explanation Fatal error detected in DSP.
Recommended Action contact your technical support representative.


%DSPRM-3-DSPALARMINFO : [chars]
Explanation DSP Alarm Data
Recommended Action


%DSPRM-5-NULLIDB_CREATE_FAIL : VoIP Null IDB creation failed.
Explanation VoIP nullidb creation failed.
Recommended Action


%DSPRM-2-FORKFAIL : Process creation of [chars] failed.
Explanation Failed to create the process.
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.


%DSPRM-5-DSP_VIC_CONFIG_NAK : Received VIC config NAK from DSP([dec]/[dec]), resetting the DSP.
Explanation Receieved NAK message from DSP. Re-attempt initialization.
Recommended Action No action is required.


DSPU

%DSPU-3-CLSIBadLength : CLSI bad length, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIBadPrimitiveType : CLSI bad primitive type, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIBadPrimitiveCmd : CLSI bad primitive command, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIBadIdentifierType : CLSI bad identifier type, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIBadIdentifier : CLSI bad identifier, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIBadReturnCode : CLSI bad return code: [dec], header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIUnexpctActSapCnf : CLSI unexpected ActivateSapCnf, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIUnexpctDeactSapCnf : CLSI unexpected DeactivateSapCnf, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIUnexpctIdStnInd : CLSI unexpected IdStnInd, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIUnexpctEnableCnf : CLSI unexpected EnableCnf, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-CLSIBadAdptCorr : CLSI bad Adaptor correlator, header= [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-DSPU_BufferCorrupted : DSPU could not free buffer - buffer corrupted
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl) . 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.


%DSPU-3-UnknownXid : XID Format not supported, XID= [chars]
Explanation Unsupported XID received from the remote station; connection with remote station could not be established.
Recommended Action Configure the remote station to send supported XID (if possible). Supported XID formats are: XID Format 0 XID Format 3


%DSPU-3-LSXIDNegotiationError : XID Negotiation Error, bad byte= [dec], bad bit= [dec], sense data= [chars]
Explanation XID3 with an error indication was received from the remote station; connection with the remote station could not be established.
Recommended Action Determine, from the CV 22 byte or bit information, which field in the XID3 is rejected by the remote station, and correct the link station configuration parameters at either the router or the remote station.


%DSPU-3-LSNoACTPUCapability : Connection attempt failed from XID= [chars], ACTPU not supported
Explanation The remote station did not request PU 2.0 activation; connection with remote station is terminated.
Recommended Action Correct link station configuration parameters at the remote station to request a system services control point (SSCP)-PU session with the router.


%DSPU-3-LSInvalidMaxIFrame : Connection attempt failed from XID= [chars], Invalid MaxIFrame= [dec]
Explanation An invalid MaxIFrame value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link station configuration at the remote station.


%DSPU-3-LSInvalidWindowSize : Connection attempt failed from XID= [chars], Invalid WindowSize= [dec]
Explanation An invalid WindowSize value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link station configuration at the remote station.


%DSPU-3-LSConnOutToHostFailed : Connect out to host [chars] failed.
Explanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests.


%DSPU-3-LSConnOutToPuFailed : Connect out to pu [chars] failed.
Explanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests.


%DSPU-3-LSConnInFromHostFailed : Connect in from host [chars] with remote address [chars] failed.
Explanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the router is configured to accept connection from this host.


%DSPU-3-LSConnInFromPuFailed : Connect in from pu [chars] with remote address [chars] failed.
Explanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept connectIn from this remote PU.


%DSPU-3-LSConnInFailed : Connect in from remote address [chars] failed.
Explanation Connection with remote station could not be established.
Recommended Action Verify configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connectIn from this remote station.


%DSPU-3-LSConnInFailedNoMem : Connect in from remote address [chars] failed; insufficient memory.
Explanation Connection with the remote station could not be established because of insufficient memory in the router.
Recommended Action Correct low memory problem in the router. If the problem persists, call your technical support representative for assistance.


%DSPU-3-SnaBadData : Bad SNA data received from PU [chars], data= [chars]
Explanation Unrecognized SNA data was received from the remote PU.
Recommended Action Correct the problem at the remote PU. If the problem persists, call your Cisco technical support representative for assistance.


%DSPU-3-ActpuNegResponse : ACTPU Neg rsp received from PU [chars]
Explanation Remote PU rejected the router's request for an SSCP-PU session.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and correct it. If the problem persists, call your Cisco technical support representative for assistance.


%DSPU-3-NotifyNegRsp : LU [dec] received a Notify Neg Resp from host [chars]
Explanation Remote host rejected the router's request to activate/deactivate an SSCP-LU session.
Recommended Action Verify host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and correct it. If the problem persists, call your technical support representative for assistance.


DSP_SPA

%DSP_SPA-2-INITFAIL : Not Enough Resources:[chars]
Explanation The shared port adaptor failed to complete software initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DSP_SPA-3-BUFF_FAIL : Not Enough MEM Buffers [chars]
Explanation Not enought memory buffers for shared port adaptor operation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DSP_SPA-3-FILE_OP_FAIL : Failed to open file [chars] : [chars]
Explanation Failed to open file
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DSP_SPA-3-FILE_RD_FAIL : Failed to read [int] bytes from file: [chars]
Explanation Failed to read data from file
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DSP_SPA-3-NULL_FAIL : Non-Initialized ptr: [chars]
Explanation About to Access non-initialized pointer
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%DSP_SPA-3-HW_ERROR : [chars]: A Hardware device error was detected. Trying to recover the SPA by reload. Error information : [chars]
Explanation An internal hardware device error has occurred on the services SPA. The error message indicates the slot, subslot, the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure.
Recommended Action Perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.


%DSP_SPA-3-HW_ERROR_INFO : [chars]: Non fatal hardware device error was detected. Error information : [chars]
Explanation An internal hardware device error has occurred on the services SPA. The error message indicates the slot, subslot, the SPA type and the name of the hardware device. This message is likely due to a recoverable hardware failure.
Recommended Action Perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.


DSS

%DSS-5-UPDOWN : DSP core [dec] is [chars]
Explanation DSP core changed state up/down
Recommended Action No action is required.


%DSS-3-ACK_FAIL : Ack failed for dsp_id [dec], seq_no [dec]
Explanation DSP core not responding to host messages
Recommended Action No action is required.


%DSS-3-DSPID_INVALID : Invalid DSPID [dec]
Explanation Invalid DSP ID detetced in the message
Recommended Action No action is required.


%DSS-3-TIMER : [chars] timer expired for DSPID [dec]
Explanation DSS timer has expired
Recommended Action No action is required.


DSX

%DSX-4-ALARM : [chars] [chars]: [chars]
Explanation The specified T1/E1 or T3/E3 Alarm has been asserted or cleared
Recommended Action The recommended action is to isolate and repair the source of the asserted alarm


DTLS

%DTLS-3-REPLAY_ERROR_DTLS : DTLS anti-replay error, src_addr: %Ci, src_port: [dec], dest_addr: %Ci, dst_port: [dec], MSGDEF_LIMIT_GLACIAL
Explanation Anti-replay error is encountered for this DTLS session.
Recommended Action LOG_STD_ACTION


%DTLS-3-REPLAY_ERROR_IPV6_DTLS : DTLS anti-replay error, ipv6 src_addr: %CI, src_port: [dec], ipv6 dest_addr: %CI, dst_port: [dec], MSGDEF_LIMIT_GLACIAL
Explanation Anti-replay error is encountered for this DTLS session.
Recommended Action LOG_STD_ACTION


DTP

%DTP-4-MEM_UNAVAIL : Memory was not available to perform the trunk negotiation action
Explanation Unable to negotiate trunks because of a lack of memory
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%DTP-4-UNKN_ERR : An unknown operational error occurred
Explanation Unable to negotiate trunks because an internal operation generated an error which was not expected to ever happen.
Recommended Action Because of the unexpected nature of the problem, the only recommended action is to reload the device


%DTP-5-TRUNKPORTON : Port [chars] has become [chars] trunk
Explanation The specified port has changed from being an access port to a trunk port using the specified encapsulation.
Recommended Action


%DTP-5-NONTRUNKPORTON : Port [chars] has become non-trunk
Explanation The specified port has changed from being a trunk port to an access port.
Recommended Action


%DTP-5-TRUNKPORTCHG : Port [chars] has changed from [chars] trunk to [chars] trunk
Explanation The specified trunk port has changed the encapsulation type is uses.
Recommended Action


%DTP-5-ILGLCFG : Illegal config(on,isl--on,dot1q) on [chars]
Explanation The two ports on the link are set to the ON mode, but one is set to 802.1Q encapsulation, while the other is set to ISL encapsulation. When both ports on a link are set to the ON mode, their encapsulation types must match
Recommended Action Configure both ports on the link to have the same encapsulation.


%DTP-4-TMRERR : An internal timer error occurred when trunking on interface [chars]
Explanation There might be some instances in which a timer used by the trunking protocol expires at a time when it is unexpected. This problem is corrected internally.
Recommended Action There is likely no long-term ramifications from this problem. However, if further problems with trunking are seen, it is recommended that you reload the device.


%DTP-5-DOMAINMISMATCH : Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch.
Explanation The two ports involved in trunk negotiation belong to different VTP domains. Trunking is possible only when the ports involved belong to the same VTP domain.
Recommended Action Ensure that the two ports that are involved in trunk negotiation belong to the same VTP domain.


DUAL

%DUAL-3-SIA : Route [chars] stuck-in-active state in [chars] [dec]. Cleaning up
Explanation A hardware or software error occurred.
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.


%DUAL-3-NOMATCH : Nexthop and infosource don't match. N = [chars], I = [chars]
Explanation A hardware or software error occurred.
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.


%DUAL-3-NOHANDLE : Handle [dec] is not allocated in pool.
Explanation A hardware or software error occurred.
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.


%DUAL-3-LINKSTILLUP : Link [dec] [chars] still exists on [chars]
Explanation A hardware or software error occurred.
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.


%DUAL-3-LINKSEXIST : Interface [chars] going down and [dec] links exist
Explanation An interface is going down or is being removed from routing through IGRP, but not all links (neighbors) have been removed from the topology table.
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.


%DUAL-3-BADCOUNT : Route [chars], [dec] successors, [dec] rdbs
Explanation A hardware or software error occurred.
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.


%DUAL-6-EVENT : [chars], [chars]
Explanation A hardware or software error occurred.
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.


%DUAL-3-NOSOCKET : Unable to open socket for AS [dec]
Explanation A hardware or software error occurred.
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.


%DUAL-3-NOBUFFER : No buffers available for [int] byte packet
Explanation The DUAL software was unable to allocate a packet buffer. 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%DUAL-3-UNKTIMER : Unknown timer type [dec] expiration
Explanation A hardware or software error occurred.
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.


%DUAL-3-REFCOUNT : Negative refcount in pakdesc [hex]
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. 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.


%DUAL-3-MULTIFLOW : Flow control error, [chars], on [chars]
Explanation A hardware or software error occurred.
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.


%DUAL-3-PEERSEXIST : [dec] peers exist on IIDB [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. 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.


%DUAL-3-ANCHORCOUNT : Anchor count negative
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. 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.


%DUAL-5-NBRCHANGE : [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]
Explanation A neighbor went up or down.
Recommended Action No action is required.


%DUAL-6-NBRINFO : [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]
Explanation Information regarding a neighbor.
Recommended Action No action is required.


%DUAL-3-RDBLEFT : Lingering DRDB deleting IIDB, dest [chars], nexthop [chars] ([chars]), origin [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. 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.


%DUAL-3-INTERNAL : [chars] [dec]: Internal Error
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. 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.


%DUAL-4-PFXLIMITTHR : [chars] [dec]: [chars] threshold prefix level([int]) reached.
Explanation Number of prefixes in the topology database has reached the configured or default threshold level.
Recommended Action Take preventive action by identifying the source of the prefixes. Use show ip eigrp accounting for details.


%DUAL-3-PFXLIMIT : [chars] [dec]: [chars] prefix limit reached([int]).
Explanation Number of prefixes for eigrp has reached the configured or default limit.
Recommended Action Use show ip eigrp accounting for details on the source of the prefixes and take corrective measures.


%DUAL-3-BADIGRPSAP : Cannot send incremental SAP update to peer on [chars]. tIncreasing output-sap-delay may help
Explanation An incremental SAP update could not be sent, because this might cause the SAP tables between peers to become out of synch.
Recommended Action Increase the output SAP delay on the listed interface to reduce buffer usage. If, after changing the delay the message remains, copy the error message exactly as it appears and report it to your technical support representative.


%DUAL-3-BADIGRPSAPTYPE : Unsupported SAP type for EIGRP being [chars] - type [hex]
Explanation There are two types of service access points (SAPs)-general queries and general responses. This message is sent when you receive or attempt to send an SAP with a type code which is not a general query or a general response. It is also sent when you receive a general query not addressed to the broadcast address.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the debug ipx sap activity and debug ipx sap event commands for the period during which this message appeared.


DYNCMD

%DYNCMD-3-MSGDISPATCHNULL : Received NULL TDL message
Explanation An unexpected condition in which IOS has received a NULL TDL message for Dynamic Commands.
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.


%DYNCMD-3-MSGDISPATCH : Unable to dispatch received TDL messages for Dynamic Commands
Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Dynamic Commands.
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.


%DYNCMD-3-MSGMISSINGFIELD : Missing field '[chars]' in TDL message '[chars]' received from the Shell Manager
Explanation A message missing a required field was received from the Shell Manager
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.


%DYNCMD-3-MSGINVALIDFIELDINT : Invalid field '[chars]' in TDL message '[chars]' received: value '[int]' for Dynamic Commands
Explanation A message with an invalid field value was received for Dynamic Command creation
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.


%DYNCMD-3-MSGINVALIDFIELDSTR : Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received for Dynamic Commands
Explanation A message with an invalid field value was received for Dynamic Command creation
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.


%DYNCMD-3-MSGERROR : Error '[chars]' handling a received TDL message '[chars]' for Dynamic Commands
Explanation An unexpected condition has occurred while IOS is processing a received Dynamic Command TDL message
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.


%DYNCMD-3-MSGBUILDERROR : Error '[dec]' building TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred while IOS is building a TDL message to send to the Shell Manager
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.


%DYNCMD-3-MSGMARSHALERROR : Error '[dec]' marshaling TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred while IOS is marshaling TDL message to send to the Shell Manager
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.


%DYNCMD-3-MSGENQUEUEERROR : Error queueing TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred when IOS attempted to queue a TDL message to send to the Shell Manager
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.


%DYNCMD-3-MSGBIPCERR : Unable to process received BIPC messages for Dynamic Commands, error: [chars]
Explanation An unexpected condition has occurred while IOS was trying to process a received BIPC message for Dynamic Commands.
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.


%DYNCMD-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer for sending messages.
Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation 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.


%DYNCMD-3-TREETOP : Unable to link top-level keyword '[chars]' into parse tree
Explanation IOS received a message to add a command into the CLI. The appropriate location to link in the command could not be found.
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.


%DYNCMD-3-TREETOPNOTKW : The top-level parser transition '[chars]' is not a keyword
Explanation IOS received a message to add a command into the CLI. The top-level node must be a keyword node.
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.


%DYNCMD-3-FLAGSINUSE : New feature flags list [int] invalid while feature flags in use [int]
Explanation IOS received a message to set the feature flags for the CLI. The message received to set the feature flags changed the number of feature flags which is unexpected. The message is ignored.
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.


%DYNCMD-3-FLAGSINVALID : New feature flag list values ([int]) different than expected ([int])
Explanation IOS received a message to set the feature flags for the CLI. The message received does not contains the number of feature flag values that the message list size indicated.
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.


%DYNCMD-3-NODEOUTOFSEQ : Create node message received when in mode '[chars]'
Explanation IOS received a message to add a command node into the CLI. The message was received out of sequence
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.


%DYNCMD-3-LINKOUTOFSEQ : Create node message received when in mode '[chars]'
Explanation IOS received a message to add a command node into the CLI. The message was received out of sequence
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.


%DYNCMD-3-NODETYPEUNKNOWN : Create node message received for unknown node type '[dec]', '[chars]'
Explanation IOS received a message to add a command into the CLI. One of the command nodes to be created is of a type unknown to IOS
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.


%DYNCMD-3-NODEDUPLICATE : Create node message received for duplicate node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the command nodes to be created has an identifier of an existing node. The new node is ignored.
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.


%DYNCMD-3-LINKUNKNOWNNODE : Link node message received for unknown node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS
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.


%DYNCMD-3-LINKUNKNOWNACCEPTNODE : Link node message received for unknown accept ([chars]) node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS
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.


%DYNCMD-3-LINKUNKNOWNALTNODE : Link node message received for unknown alternate node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS
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.


%DYNCMD-3-LINKINVALIDALT : Link alternate node message received for node '[chars]', which cannot have an alternate.
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction.
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.


%DYNCMD-3-LINKINVALIDTRANS : Link transition '[chars]' message received for node '[chars]', which cannot have such a transition.
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction.
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.


%DYNCMD-3-CHAINADDFAIL : Parse chain link add failed for '[chars]'
Explanation An error has occurred when a dynamic command is being added to the IOS command set. The commands specified will not be available.
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.


%DYNCMD-3-CHAINDELFAIL : Parse chain link delete failed for '[chars]'
Explanation An error has occurred when a dynamic command is being removed from the IOS command set. The commands specified will stil not be available.
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.


%DYNCMD-7-CMDSET_LOADED : The Dynamic Command set has been loaded from the Shell Manager
Explanation IOS has completed loading the set of commands published and processed by components running in packages other than the IOS package.
Recommended Action No action is required.


%DYNCMD-7-CMDSET_UNLOADED : The Dynamic Command set from the Shell Manager has been unloaded
Explanation IOS has completed unloading the Dynamic Command set. This should only occur when a new package has been installed and should shortly be followed by a message indicating that the new Dynamic Command set has been loaded.
Recommended Action No action is required.


%DYNCMD-3-INIT : Dynamic command subsystem failed to initialize '[chars]'
Explanation Some features depend on portions of the dynamic command infrastructure. Such features will be unavailable.
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.


%DYNCMD-3-PKGINT_LOAD : Failed to load '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
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.


%DYNCMD-3-PKGINT_SYMBOL : Package [chars] incompatible: symbol '[chars]' is of type [chars], expected [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
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.


%DYNCMD-3-PKGINT_VALIDATE : Failed to validate '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
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.


%DYNCMD-3-PKGINT_API : Package interface failure for package '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
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.


%DYNCMD-3-PKGINT_INSTALL : Failed to install '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
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.


%DYNCMD-3-PKGINT_ARGS : Incorrect argument count for package '[chars]', operation '[chars]': [dec] not [dec]
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
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.


%DYNCMD-3-PKGINT_ARG : Incorrect argument type for package '[chars]', operation '[chars]': [chars] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
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.


%DYNCMD-3-PKGINT_ARG_NUMBERVAL : Invalid argument value for package '[chars]', operation '[chars]': [int] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
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.


%DYNCMD-3-PKGINT_ARG_OPAQUEVAL : Invalid argument value for package '[chars]', operation '[chars]': [IPV6 address] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
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.


%DYNCMD-3-PKGINT_OFFSET : Invalid offset argument for package '[chars]', operation '[chars]': [chars] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
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.


%DYNCMD-3-PKGNODE_ADD_FAIL : Parse node add failed for package '[chars]', [chars] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The node could not be added and the commandset for the package will not be available.
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.


%DYNCMD-3-PKGHANDLER_FILE_WRITE : Package '[chars]' failed to write: [chars] ([chars])
Explanation An error has occurred when a package was attempting to write a file. The configuration for the package could not be propagated to associated components.
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.


%DYNCMD-3-PKGHANDLER_FILE_REMOVE : Package '[chars]' failed to remove: [chars] ([chars])
Explanation An error has occurred when a package was attempting to remove a file. This should never fail.
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.


%DYNCMD-3-PKGINT_DIR_CREATE : Package integration failed to create directory: [chars] ([chars])
Explanation An error has occurred when attempting to create a package export directory. This should never fail.
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.


%DYNCMD-3-PKGINT_DIR_OPEN : Package integration failed to open directory: [chars] ([chars])
Explanation An error has occurred when attempting to open a package export directory. This should never fail.
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.


%DYNCMD-3-PKGINT_DIR_REMOVE : Package integration failed to remove directory: [chars] ([chars])
Explanation An error has occurred when attempting to remove a package export directory. This should never fail.
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.


%DYNCMD-3-PKGINT_DIR_MOVE : Package integration failed to move directory: [chars] to [chars] ([chars])
Explanation An error has occurred when attempting to move a package export directory. This should never fail.
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.


%DYNCMD-3-PKGINT_FILE_OPEN : Package integration failed to open file: [chars] ([chars])
Explanation An error has occurred when attempting to open a file in a package export directory. This should never fail.
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.


%DYNCMD-3-PKGINT_FILE_REMOVE : Package integration failed to remove: [chars] ([chars])
Explanation An error has occurred when attempting to remove a package export file. This should never fail.
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.


%DYNCMD-3-PKGINT_LOCK : Failed to acquire package list lock for [chars]: [chars]
Explanation An error occurred when a configuration package was being installed or removed. This may indicate a timeout which may be a temporary condition.
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.


%DYNCMD-3-PKGINT_PKGLOCK : [chars] failed to acquire package lock for [chars]
Explanation An error occurred when locking a configuration package. The package needs to be locked for processing configuration commands or timer-based processing of configuration data.
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.


%DYNCMD-3-PKGINT_UNLOCK : Failed to release the package list lock: [chars]
Explanation An error occurred when a configuration package was being installed or removed. This should not occur.
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.


%DYNCMD-7-PKGINT_INSTALLED : The command package '[chars]' has been succesfully installed
Explanation IOS has completed installation of the specified command package. Configuration commands for the package are now available.
Recommended Action No action is required.


%DYNCMD-7-PKGINT_UNINSTALLED : The command package '[chars]' has been succesfully uninstalled
Explanation IOS has completed uninstallation of the specified command package. Configuration commands for the package are no longer available.
Recommended Action No action is required.


%DYNCMD-3-PKGERR_LOG_FAIL : Failed to log errors for package '[chars]'
Explanation An error has occurred updating the commandset for a newly installed package. The commands which failed to transfer could not be saved for further analysis.
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.


%DYNCMD-4-CMD_DEPRECATION : The command 'platform trace runtime' is being deprecated. Please use the exec mode command 'set platform software trace' instead. Note that using this command and 'set platform software trace' together will lead to indeterministic results
Explanation The command 'platform trace runtime' is being deprecated.
Recommended Action No action is required.


E911 through EM_ISSU

E911

%E911-4-CALLBACK_UNREACHABLE : Unable to contact the last emergency caller at [chars].
Explanation The Public Safety Answering Point is calling an Emergency Line Identification Number (ELIN). The last caller from that ELIN has its calling number saved for three hours from the time the emergency call was originated. If the ELIN cannot be translated to the caller's calling number, then one of the following has happened: 1) The emergency call information has expired. Forwarding has not been set-up when calls have expired. 2) A system reload has occurred, thereby erasing the emergency call information.
Recommended Action The dial-peer created to accept ELIN calls could set-up Call Forwarding to a corporate operator or main help desk to avoid having the call backs rejected.


%E911-5-EMERGENCY_CALL_HISTORY : calling number[[chars]]; called number[[chars]]; ELIN[[chars]]
Explanation A call has been made to an emergency response number. This message simply informs system administrators of the call.
Recommended Action The administrator determines the policy for outbound emergency calls. The administrator may set-up an application to page or email a technician everytime this message is emitted.


%E911-3-MISSING_DEFAULT_NUMBER : It is mandatory to configure an ELIN under 'voice emergency response settings.'
Explanation The administrator has enabled the Enhanced 911 feature without configuring a default ELIN under 'voice emergency response settings.'
Recommended Action The administrator should enter the 'voice emergency response settings' mode and configure a value for the 'elin' CLI.


EAP

%EAP-2-PROCESS_ERR :
Explanation This is critical condition where the router could not perform EAP process related operation.
Recommended Action Review SM logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Reload the device/process.


%EAP-6-MPPE_KEY :
Explanation This messages informs that the router received MPPE KEY for the specified host.
Recommended Action No action is required.


%EAP-3-BADPKT :
Explanation This messages informs that the router received an invalid or malformed EAP packet from the specified host.
Recommended Action Check specified host for EAP operation.


%EAP-6-FIPS_UNSUPPORTED_METHOD :
Explanation This message informs that a method is not supported in FIPS mode.
Recommended Action Use FIPS supported methods - PEAP, TLS and FAST


EC

%EC-5-MINLINKS_NOTMET : Port-channel [chars] is down bundled ports ([dec]) doesn't meet min-links
Explanation The administrative configuration of minimum links is greater than the number of bundled ports. Therefore this port channel has been brought down
Recommended Action Reduce the min-links configuration for this group or add more ports to this port-channel to have them bundle.


%EC-5-MINLINKS_MET : Port-channel [chars] is up as its bundled ports ([dec]) meets min-links
Explanation The administrative configuration of minimum links is equal or less than the number of bundled ports. Therefore this port channel has been brought up
Recommended Action None.


%EC-3-BWMISMATCH : [chars] should be removed from the Port-channel[dec]
Explanation The member-link shouldn't have been part of the port-channel bundle because the bandwidth of the member-link doesn't match the bandwidth of the bundle. This configuration shouldn't have been allowed. This error indicates it was allowed due to some software issue.
Recommended Action Remove the member-link from the port-channel for proper operation.


ECFM_PROXY

%ECFM_PROXY-3-ECFM_MEM_REQ_FAILED : ECFM IPC subtype: [dec]
Explanation Requesting more memory 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.


%ECFM_PROXY-3-ECFM_MEM_EXTEND_FAILED : ECFM IPC subtype: [dec]
Explanation Extending memory 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.


%ECFM_PROXY-4-PROXY_INVALID_MSG_LEN : QFP ECFM Proxy IPC invalid length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Cisco internal software error. QFP ECFM Proxy received invalid IPC message length from control plane. This message will be ignored.
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.


%ECFM_PROXY-4-PROXY_INVALID_MSG : QFP ECFM Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP ECFM Proxy received an invalid message from control plane. This message will be ignored.
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.


%ECFM_PROXY-2-PROXY_IPC_INIT_FAILED : QFP ECFM Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP ECFM Proxy initialization detected that the IPC interface initialization failed. QFP ECFM proxy will not be functional while this condition exists.
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.


%ECFM_PROXY-3-PROXY_BAD_MSG : QFP ECFM Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP ECFM Proxy received a corrupted message from control plane. This message will be ignored.
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.


%ECFM_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP ECFM Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP ECFM Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition.
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.


%ECFM_PROXY-3-PROXY_IPC_SEND_FAILED : QFP ECFM Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP ECFM Proxy message processing detected a message sent failure. The message is lost as the result of this condition.
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.


EDSP

%EDSP-6-CEF_WAIT : NULL /* defined elsewhere */msgdef(CEF_TOOLONG, EDSP, LOG_WARNING, 0, NULL/* defined elsewhere */CEF_TOOLONG, EDSP, LOG_WARNING, 0, NULL/* defined elsewhere */msgdef(IPV6_ENABLED, EDSP, LOG_INFO, 0, NULL /* defined elsewhere */IPV6_ENABLED, EDSP, LOG_INFO, 0, NULL /* defined elsewhere */msgdef(IPV6_FAILED, EDSP, LOG_INFO, 0, NULL /* defined elsewhere */IPV6_FAILED, EDSP, LOG_INFO, 0, NULL /* defined elsewhere */voidedsprm_create_idb_for_vrfs (void
Explanation
Recommended Action


%EDSP-6-VEC_CHANGE : EDSP0's LES switching vector set to [chars]
Explanation To monitor CEF initialization for the hidden interface.
Recommended Action No action is required.


%EDSP-6-CEF_WAIT : Waiting for CEF initialization to complete first ... [dec]
Explanation Initialization of CEF RTP sending relies on system's CEF readiness.
Recommended Action No action is required.


%EDSP-4-CEF_TOOLONG : CEF to SCCP devices may be disabled! See message below.
Explanation Given up waiting for CEF initialization to complete.
Recommended Action Check the message about CEF and the EDSP0 interface below. If the vector is EVENTUALLY set to Null, CEF RTP sending for SCCP devices is disabled. You may try to recover by restarting ip cef in IOS configuration.


%EDSP-6-IPV6_ENABLED : IPv6 on interface [chars] added.
Explanation IPv6 capability has been enabled for the (sub-)interface.
Recommended Action No action is required.


%EDSP-6-IPV6_FAILED : IPv6 on interface [chars] failed.
Explanation IPv6 initialization has failed for the (sub-)interface.
Recommended Action Please check IPv6 and interface related configurations.


EEM

%EEM-6-SUCCESS : [chars]
Explanation EEM Policy provisioning by the Auto deploy is successful.
Recommended Action No action is required.


%EEM-6-SUCCESS : [chars]
Explanation EEM Policy provisioning by the Auto-deploy is successful.
Recommended Action No action is required.


EFP_STORMCTRL

%EFP_STORMCTRL-6-ACTION_DEFAULT : Service Instance [dec] on interface [chars] has dropped packets due to storm-control
Explanation Configured Storm Control Threshold on Ethernet Service Instance Reached
Recommended Action No Action


EM

%EM-3-EXCEED : EM exceed maximum open events ([dec]).
Explanation The total number of open events exceeded the maximum number of possible open events. The maximum number that the EM server permits is specified in the error message. EM clients are either opening too many events or not closing events within the permitted time period.
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/). Issue the show em state | inc <em_type> command to gather data that may help identify the nature of the error. 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.|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/). Issue the show em state | inc <em_type> command to gather data that may help identify the nature of the error. 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.


%EM-3-NULLPTR : The pointer in a specified EM function ([chars]) is incorrectly NULL.
Explanation The pointer in the specified EM function is incorrectly NULL. This condition might be caused by incorrect logic or a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show em state command or the show em status command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.


%EM-3-FAIL : The specified EM Function failed ([chars]).
Explanation The specified EM function failed. This condition might be caused by incorrect logic or a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show em state command or the show em status command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.


%EM-3-NOMEM : The EM failed to allocate memory resources for the specifiedEM function ([chars]).
Explanation The EM failed to allocate memory resources for the specified function because memory is running low.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show memory summary command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.


%EM-4-AGED : The specified EM client ([chars] type=[dec], id=[dec]) did not close the EM event within the permitted amount of time ([dec] msec).
Explanation A timeout occurred. This condition is minor and should not affect the functionality of the switch.
Recommended Action This message should not affect switch functionality but can be sign of a software bug condition. Please check Bug Toolkit on the Cisco web-site for relevant bugs against this message. If you do not find any, please contact the TAC with the output of show em client


%EM-4-INVALID : The specified EM function ([chars]) received Invalid operands <[dec]>.
Explanation The EM client used invalid API parameters.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show em state command or the show em status command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.


%EM-4-SENDFAILED : The specified EM client (type=[dec]) failed to send messages to standby.
Explanation Because the specified EM client failed to send messages to the standby supervisor engine, the standby supervisor engine is not updated. Do not attempt to failover to standby supervisor engine.
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/). Issue the show checkpoint clients command to gather data that may help identify the nature of the error. 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.


%EM-4-NOTUP : The EM is not available ([chars]).
Explanation Because some basic initialization failed, the EM is not available. This condition might be caused by failure of a basic infrastructure functionality or a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show em state command or the show em status command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.


%EM-4-SEARCH : The EM function ([chars]) searched for the specified open event ([dec]),but the search failed.
Explanation The specified EM function could not find the specified open event. This condition might be caused by a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show em state command or the show em status command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.


%EM-4-LIMIT : EM exceed open events limit ([dec]).
Explanation The EM has exceeded the permitted number of open events. The open event limit is 5000.
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.


EMD

%EMD-3-PFU_INITIALIZATION : The RP has failed to initialize a Power Supply/Fan module controller because [chars]
Explanation The route processor (RP) failed to initialize a power supply or a fan module controller. This error could be caused by a hardware defect or a C2W access failure.
Recommended Action Examine the logs for C2W and hardware errors.


%EMD-3-IDPROM_ACCESS : Failed access or process an IDPROM because [chars]
Explanation The system failed to access an IDPROM or an IDPROM process failed. This error can occur from a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.


%EMD-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].
Explanation One or more IDPROM sensor fields failed to parse properly. The most likely reason is a checksum failure in the IDPROM from incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.


%EMD-3-SENSOR_INITIALIZATION : Failed to initialize sensor monitoring because [chars].
Explanation The system failed to initialize an IDPROM sensor monitoring process. This error can occur from a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.


%EMD-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation An event facility initialization or maintenance function failed. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.


%EMD-0-RESOLVE_FRU : Failed to determine [chars] card because [chars]
Explanation The system was unable to to determine a card state. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.


%EMD-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]
Explanation The system failed to initialize the application services. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.


EM_ISSU

%EM_ISSU-2-INIT : Event Manager ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Event Manager 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.


%EM_ISSU-3-TRANSFORM_FAIL : Event Manager ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The Event Manager 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 Event Manager 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>)


%EM_ISSU-3-MSG_NOT_OK : Event Manager ISSU client 'Message Type [dec]' is not compatible
Explanation The Event Manager ISSU client received an incompatible message from the peer device. The message cannot be processed.
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>)


%EM_ISSU-3-OPAQUE_MSG_NOT_OK : Event Manager ISSU client 'Opaque Message Type [dec]' is not compatible
Explanation The Event Manager ISSU client received an incompatible message from the peer device. The opaque message cannot be processed.
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>)


%EM_ISSU-3-MSG_SIZE : Event Manager ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Event Manager ISSU client failed to calculate the MTU for the specified message. The Event Manager ISSU client is 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>)


%EM_ISSU-3-INVALID_SESSION : Event Manager ISSU client does not have a valid registered session.
Explanation The Event Manager 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>)


%EM_ISSU-2-SESSION_REGISTRY : Event Manager ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Event Manager 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>)


%EM_ISSU-3-SESSION_UNREGISTRY : Event Manager ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Event Manager 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>)


%EM_ISSU-2-SESSION_NEGO : Event Manager ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The Event Manager 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>)


%EM_ISSU-2-SEND_NEGO_FAILED : Event Manager ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Event Manager 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)


%EM_ISSU-2-GET_BUFFER : Event Manager ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Event Manager ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)