Skip to content
Skip to search
Skip to footer

Cisco SD-WAN System Error Messages Guide for Cisco IOS XE SD-WAN 16.11.x

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents

Find Matches in This Book

Results

Updated:: May 2, 2019

Chapter: MPLS_TP_LSP through RPL

MPLS_TP_LSP through RPL
MPLS_TP_LSP through NAT
NAT64 through NETWORK_RF_API
NIF_MGR through ONEP_LISP
OOM through PBUF
PCE through PKTLOG
PLATFORM through PLATFORM_TAM
PLIM_QOS through POS_SPA_SPI4
PRELIB_DL through QOS
RAC through RFS
RG_AR through RPL

MPLS_TP_LSP through RPL

MPLS_TP_LSP through NAT

MPLS_TP_LSP
MPLS_TP_LSP_FSM
MPLS_TP_MEM
MPLS_TP_PROC
MPLS_TP_TIMER
MSG_FIFO
MSG_POS_OC3_OC12_SPA
MTRIE
MX
NAT

MPLS_TP_LSP


%MPLS_TP_LSP-3-UPDOWN : [chars] LSP [chars] is [chars][chars][chars]
Explanation	The indicated MPLS-TP LSP has gone up or down. If the LSP went down, the failure condition, and the fault source information is provided.
Recommended Action	Examine the failure condition and source information to determine why the LSP went down.


%MPLS_TP_LSP-5-LOCKOUT : [chars] LSP [chars] [chars] lockout state
Explanation	The indicated LSP has entered or exited lockout state due to administrative action at one endpoint
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MPLS_TP_LSP-5-CONFIG_CHANGED : LSP [chars] is [chars]
Explanation	The configuration of the MPLS-TP midpoint LSP has changed. This message is to notify the NMS of changes.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

MPLS_TP_LSP_FSM


%MPLS_TP_LSP_FSM-3-LSP_FSM_ERROR : LSP FSM Error occurred. Received event:[chars] in state:[chars]
Explanation	An erroneous event was received by the TP LSP. This is an error internal to MPLS-TP
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

MPLS_TP_MEM


%MPLS_TP_MEM-3-NO_MEM : Could not allocate memory for MPLS-TP context
Explanation	Could not allocate memory for MPLS-TP context. This is an internal issue to MPLS-TP
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

MPLS_TP_PROC


%MPLS_TP_PROC-3-PROC_CREATE_FAIL : [chars] [chars] [dec]
Explanation	Could not create MPLS-TP process. This is an internal issue to MPLS-TP
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MPLS_TP_PROC-3-UNKNOWN_MESSAGE : Received unknwon message:[dec]
Explanation	An unknown message was posted to the MPLS-TP process. This is an internal issue to MPLS-TP
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MPLS_TP_PROC-3-UNKNOWN_EVENT : Received unknown event: Major:[dec] Minor:[dec]
Explanation	An unknown event was posted to the MPLS-TP queue. This is an internal issue to MPLS-TP.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

MPLS_TP_TIMER


%MPLS_TP_TIMER-3-UNKNOWN_TIMER_TYPE_EXPIRY : Unknown timer type expired:[dec]
Explanation	An unknown MPLS-TP timer type expired. This is an issue internal to MPLS-TP
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

MSG_FIFO


%MSG_FIFO-2-MSG_FIFO_CREATE : [chars]: Bad parameter to message fifo creaate [chars] = [hex]
Explanation	Failed to create message fifo, invalid memory size or other parameter.
Recommended Action	LOG_STD_ACTION

MSG_POS_OC3_OC12_SPA


%MSG_POS_OC3_OC12_SPA-3-IOFPGA_INIT : [chars] (slot [dec]; bay [dec]) Device IOFPGA initialization failed.
Explanation	IOFPGA Device initialization failed. It indicates FPGA associated PLL lock or interrupt issues. It may also indicate a hardware failure.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-FRAMER_INIT : [chars] (slot [dec]; bay [dec]) Device Framer initialization failed.
Explanation	Framer device initialization failed. It indicates a hardware failure.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-SPI42_INIT : [chars] (slot [dec]; bay [dec]) Device SPi42 initialization failed.
Explanation	SPi42 Device initialization failed. It indicates a hardware failure.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-AUXC2W_INIT : [chars] (slot [dec]; bay [dec]) Device Auxiliary C2W initialization failed.
Explanation	Auxiliary C2W bus initialization failed. It indicates a hardware failure.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-SMM665_INIT : [chars] (slot [dec]; bay [dec]) Device SMM665 initialization failed.
Explanation	SMM665 Summit Controller initialization failed. It indicates a hardware failure.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-MAX1668_INIT : [chars] (slot [dec]; bay [dec]) Device MAX1668 initialization failed.
Explanation	MAX1668 temperature sensor initialization failed. It indicates a hardware failure.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-DS1844_INIT : [chars] (slot [dec]; bay [dec]) Device DS1844 initialization failed.
Explanation	DS1844 potentiometer initialization failed. It indicates a hardware failure
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-RESOURCE_ERROR : [chars] ([hex], [hex], [hex]) [chars]
Explanation	Failed to get required interface.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%MSG_POS_OC3_OC12_SPA-3-IOFPGA_CREATE : [chars] (slot [dec]; bay [dec]) Device IOFPGA creation failed.
Explanation	IOFPGA Device creation failed.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-FRAMER_CREATE : [chars] (slot [dec]; bay [dec]) Device Framer creation failed.
Explanation	Framer device creation failed.
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-SPI42_CREATE : [chars] (slot [dec]; bay [dec]) Device SPi42 creation failed.
Explanation	SPi4.2 Device creation failed
Recommended Action	Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.


%MSG_POS_OC3_OC12_SPA-3-XCVR_RATE_NOTSUPPORTED : [chars] (slot [dec]; bay [dec]) Tranceiver rate not supported on the SPA.
Explanation	Tranceiver rate not supported on the SPA.
Recommended Action	Remove the tranceiver module and insert a valid module with rate that is supported on the SPA.


%MSG_POS_OC3_OC12_SPA-3-XCVR_ANALYZE : [chars] (slot [dec]; bay [dec]; port [dec]) Tranceiver analyze failed.
Explanation	Tranceiver analyze failed
Recommended Action

MTRIE


%MTRIE-4-MTRIECORRUPTLEAF : [IP_address]/[dec] - [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.


%MTRIE-4-MTRIELEAFOPFAIL : [IP_address]/[dec] - [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.


%MTRIE-4-PLACEALLOC : Failed to allocate place holder
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.


%MTRIE-4-MTRIEMISALIGNEDNODEPTR : [hex] - [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.

MX


%MX-6-NOMEM : [chars] bufhdr allocation failure, MSGDEF_LIMIT_MEDIUM
Explanation	An attempt to allocate memory failed. This could cause features that manage packets in multiple pieces, or that directly export data, not to work properly in some cases.
Recommended Action	LOG_STD_ACTION


%MX-3-CARVE : [chars]: size [int] too small
Explanation	A software error resulted in an attempt to create buffers in an area of memory that was too small.
Recommended Action	LOG_STD_ACTION


%MX-3-RESIZE : [chars]: non-contiguous resize: orig [hex]/[hex], new [hex]/[hex], MSGDEF_LIMIT_MEDIUM
Explanation	A software error was detected during a resize operation on the specified memory region.
Recommended Action	LOG_STD_ACTION


%MX-6-NOBUFHDR : [chars]
Explanation	An attempt to add buffers within a memory region failed.
Recommended Action	LOG_STD_ACTION


%MX-3-MAXPOOLS : too low
Explanation	A source code inconsistency was detected.
Recommended Action	Increase the number of pools allowed.


%MX-3-INITBUFHDR : [chars]: mgmt memory allocation failure (size [int])
Explanation	insufficient mgmt memory provided for initialization of the external memory manager, which will cause features that manage packets in multiple pieces, or that directly export data, not to work properly.
Recommended Action	LOG_STD_ACTION


%MX-3-BADSTART : [chars]: [hex] (current [hex], size [int])
Explanation	A software error was detected during an attempt to increase the size of an external memory region.
Recommended Action	LOG_STD_ACTION


%MX-3-BADPOOL : [chars]: [int]
Explanation	Software detected the use of an invalid pool index, which may be the result of incompatible software versions on different system components.
Recommended Action	LOG_STD_ACTION


%MX-3-BADFEAT : [chars]: [dec]
Explanation	Software detected the use of an invalid feature enumeration, which may be the result of incompatible software versions on different system components.
Recommended Action	LOG_STD_ACTION


%MX-3-BADMAGIC : [chars]: [hex] in [hex], MSGDEF_LIMIT_MEDIUM
Explanation	A data structure inconsistency was detected in a buffer header, perhaps as the result of memory corruption. A buffer has been dropped because of this, resulting in a memory leak and potential system unreliability.
Recommended Action	Please report the problem Cisco technical support, along with the text of the error message. If the system becomes unstable, restarting or reloading the affected component should correct the instability.


%MX-3-SUBRGNINDX : [chars]: Subregion Index allocation failure
Explanation	Unable to obtain a sub region index so unable add sw managed memory
Recommended Action	LOG_STD_ACTION

NAT


%NAT-3-ALLOC_FAIL : data [hex], MSGDEF_LIMIT_GLACIAL
Explanation	A request exceeded for memory allocation failed
Recommended Action	LOG_STD_ACTION


%NAT-3-RMAP_OP_FAIL : Routemap hash table not set up (attempted [chars]), MSGDEF_LIMIT_MEDIUM
Explanation	An operation was attempted on the route map hash table, but the hash table hash not yet been initialized.
Recommended Action	LOG_STD_ACTION


%NAT-3-MAPPING_REFCNT_FAIL : refcount [dec], MSGDEF_LIMIT_MEDIUM
Explanation	The mapping reference count is below zero. This indicates that the reference count incrementing and decrementing operations are out of sync
Recommended Action	LOG_STD_ACTION


%NAT-3-DYN_PAT_MAP_UPD_OR_ADD_FAIL : rc [dec], MSGDEF_LIMIT_MEDIUM
Explanation	The add or update of a dynamic pat mapping failed with the assoicated return code. This will generally mean that the IOS configuration is now out of sync with the data plane. The mapping should be removed from the configuration to try to get things back in sync.
Recommended Action	LOG_STD_ACTION


%NAT-3-EMPTY_CHUNK : id [int], MSGDEF_LIMIT_MEDIUM
Explanation	The memory provided by the client to the datapath initilization is NULL
Recommended Action	LOG_STD_ACTION


%NAT-3-CHUNK_ID_MISMATCH : id [int] not found, MSGDEF_LIMIT_MEDIUM
Explanation	The chunk ID provided by the client doesn't match any of the available chunk IDs. Hence a valid chunk could not be found for the given chunk ID.
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_NO_BUF : , MSGDEF_LIMIT_MEDIUM
Explanation	There was not enough memory to send the HA record
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_BULK_SYNC_FAIL : flags [hex] rg [dec], MSGDEF_LIMIT_MEDIUM
Explanation	There was a failure such that NAT Bulk Sync did not occur
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_FIND_SESS : in_orig adr [hex] port [hex] out_trans adr [hex] port [hex] vrf [hex] prot [hex] cook [hex] [hex], MSGDEF_LIMIT_MEDIUM
Explanation	Standby could not find the session indicated by the HA message
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_FIND_MATCHING_SESS : values (msg/sess): in_orig adr ([hex]/[hex]) port ([hex]/[hex]) out_trans adr ([hex]/[hex]) port ([hex].[hex]), MSGDEF_LIMIT_MEDIUM
Explanation	Standby could not find the matching session indicated by the HA message
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_STANDBY_CLR_DB_FAILED : rc=[dec], MSGDEF_LIMIT_MEDIUM
Explanation	Standby failed trying to clear databased with indicated return code
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_CREATE_SESS : in_orig adr [hex] port [hex] out_trans adr [hex] port [hex] vrf [hex] prot [hex] cook [int] rg [dec], MSGDEF_LIMIT_MEDIUM
Explanation	Standby could not create the session indicated by the HA message
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_LOCK_PARENT : in_orig adr [hex] port [hex] out_trans adr [hex] port [hex] vrf [hex] prot [hex] cook [int], MSGDEF_LIMIT_MEDIUM
Explanation	Standby could not lock parent of the session; thus session not created
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_CREATE_BIND : idomain [dec] orig adr [hex] port [hex] trans adr [hex] port [hex] vrf [hex] prot [hex] rg [dec], MSGDEF_LIMIT_MEDIUM
Explanation	Standby could not create the bind indicated by the HA message
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_INVALID_MSG_RCVD : invalid value [dec] opcode [hex] version [hex], MSGDEF_LIMIT_MEDIUM
Explanation	Standby received an invalid NAT HA message
Recommended Action	LOG_STD_ACTION


%NAT-4-HA_INVALID_MSGVER_RCVD : invalid version [dec], MSGDEF_LIMIT_GLACIAL
Explanation	Standby received an invalid NAT HA message
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_INVALID_STATE : state [dec], MSGDEF_LIMIT_MEDIUM
Explanation	An invalid HA state was received from the HA infrastructure.
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_ALLOC_ADDR : addr %Ci port [hex], MSGDEF_LIMIT_MEDIUM
Explanation	The standby NAT could not allocate the address requested by the active
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_FIND_POOL : pool_id [dec], MSGDEF_LIMIT_MEDIUM
Explanation	The standby NAT could find the pool indicated by the active
Recommended Action	LOG_STD_ACTION


%NAT-3-HSL_ALLOC_FAIL : [chars], MSGDEF_LIMIT_MEDIUM
Explanation	High Speed logging memory allocation failed. When this happens the event will not be exported to the collector. This indicates a temporary condition when the system runs low on memory. The failure does not have any effects on the operation of NAT
Recommended Action	LOG_STD_ACTION


%NAT-6-LOG_TRANSLATION : [chars] Translation [chars] %Ci:[dec] %Ci:[dec] %Ci:[dec] %Ci:[dec] [dec]
Explanation	A translation was created as a result of either a configuration or traffic flowing through the NAT subsystem
Recommended Action	This message is for debugging purposes only and gets logged only when logging is turned on


%NAT-3-STATIC_MAP_ADD_FAIL : local addr %Ci global addr %Ci [chars], MSGDEF_LIMIT_MEDIUM
Explanation	An add of a static NAT mapping failed due to listed reason. This mapping will be in the IOS configuration, but is not active in the data plane. It is recommended to remove the mapping from the configuration
Recommended Action	LOG_STD_ACTION


%NAT-4-DEFAULT_MAX_ENTRIES : default maximum entries value [dec] exceeded; frame dropped, MSGDEF_LIMIT_MEDIUM
Explanation	This is an information message which occurs when NAT is configured and a frame is dropped due to the default maximum entries limit. Starting with release 5, XNE, NAT will use a default max-entries in the data plane based on the ESP type. This will not show in the configuration and is overriden by any user configuration of 'ip nat trans max-entries <value>'. The purpose of the default data plane limit is to protect the box from memory exhaustion which could occur if no limit is enforced.
Recommended Action


%NAT-6-ADDR_ALLOC_FAILURE : Address allocation failed; pool [dec] may be exhausted [[dec]], MSGDEF_LIMIT_MEDIUM
Explanation	This message indicates that an address could not be allocated from a pool because there were no free addresses in the pool at that time.
Recommended Action


%NAT-6-POOL_WATERMARK_HIGH : [chars] High watermark reached for pool [dec], MSGDEF_LIMIT_FAST/100
Explanation	This message indicates that pool usage has crossed its high watermark. Pool may exhaust soon.
Recommended Action


%NAT-6-CLEAR_FAIL_TRANS_IN_USE : , MSGDEF_LIMIT_MEDIUM
Explanation	The requested clear failed because the transaction was in use. Some clear commands support a 'forced' keyword which allows you to override this.
Recommended Action	LOG_STD_ACTION


%NAT-3-PER_VFR_HSL_ADD_FAILED : , MSGDEF_LIMIT_MEDIUM
Explanation	The attempt to turn on NAT HSL for a vrfid %d failed. Please remove configuration and try again.
Recommended Action	LOG_STD_ACTION


%NAT-3-POOL_ADD_FAIL : pool-id [dec] rc [dec], MSGDEF_LIMIT_MEDIUM
Explanation	A request to the data plane to add or update a pool has failed To clean up remove pool configuration and try re-adding it
Recommended Action	LOG_STD_ACTION


%NAT-3-HA_COULD_NOT_CLR : Standby temporarily unable to process clear; please retry, MSGDEF_LIMIT_MEDIUM
Explanation	A request from the active to process a clear translation failed. Please retry.
Recommended Action	LOG_STD_ACTION


%NAT-3-SHOW_TRANS_FAIL : unable to show [dec] entries from bucket [int], MSGDEF_LIMIT_MEDIUM
Explanation	Unable to show some entries from session database. If using verbose, try using non-verbose. Otherwise situation is likely to be temporary. Or it may be wise to do 'clear ip nat trans *' as a very odd session distribution has occurred.
Recommended Action	LOG_STD_ACTION


%NAT-3-SHOW_LIMIT_FAIL : unable to show [int] entries from bucket [int], MSGDEF_LIMIT_MEDIUM
Explanation	Unable to show some entries from limit database. The situation is likely to be temporary. Or it may be wise to do 'clear ip nat trans *' as a very odd limit entry distribution has occurred.
Recommended Action	LOG_STD_ACTION


%NAT-4-SHOW_BIND_NOT_COMPLETE : Unable to show all of NAT binds due to internal error; try again, MSGDEF_LIMIT_MEDIUM
Explanation	This is an information message which occurs when NAT is unable to show all address binds due to an internal error. Please try operation again.
Recommended Action


%NAT-3-STATIC_MAP_ADD_FAILED : local addr %Ci global addr %Ci [chars], MSGDEF_LIMIT_MEDIUM
Explanation	An add of a static NAT mapping failed due to listed reason. This mapping will be in the IOS configuration, but is not active in the data plane. It is recommended to remove the mapping from the configuration
Recommended Action	LOG_STD_ACTION


%NAT-3-DYN_MAP_ADD_FAIL : [chars], MSGDEF_LIMIT_MEDIUM
Explanation	The add of a dynamic mapping failed. This will generally mean that the IOS configuration is now out of sync with the data plane. The mapping should be removed and then re-added to try to get things back in sync.
Recommended Action	LOG_STD_ACTION


%NAT-4-FORCED_DEL_BIND_FAILED : Unable to find bind to forcibly delete, MSGDEF_LIMIT_MEDIUM
Explanation	This is an information message which occurs when NAT is unable to find a bind even though IOS thinks the bind exists. Please try other methods of clearing transaction.
Recommended Action


%NAT-3-DP_REL_FAIL : DP REL FAIL, retry count [dec] exceeded max, MSGDEF_LIMIT_MEDIUM
Explanation	The dp release fail due to too many retry on freeing session chunk
Recommended Action	LOG_STD_ACTION


%NAT-4-SEQ_DELTA_LIST_CORRUPT : Sequence Delta list tail pointer null in error, MSGDEF_LIMIT_MEDIUM
Explanation	For unknown reasons, sequence delta list tail pointer is null
Recommended Action	LOG_STD_ACTION

NAT64 through NETWORK_RF_API

NAT64
NATMIB_HELPER
NCS4200IM
NCS4200INTF
NCS4200_RP_ATM_SPA
NDBMAN
NDBUTIL
NETCLK
NETWORK_CLOCK_SYNCHRONIZATION
NETWORK_RF_API

NAT64


%NAT64-3-EINVAL : NULL
Explanation	An unexpected input value to a function was incorrect
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-3-UNINITIALIZED : NAT64 feature is not properly initialized
Explanation	A function call was made when the system was not properly 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-3-INIT_FAILED : An initialization failed, rc([chars])
Explanation	An initialization in the system 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.


%NAT64-3-ENOENT : NULL
Explanation	A lookup failed unexpectedly.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-3-EEXIST : NULL
Explanation	An item unexpectedly exists already.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-3-ENOMEM : Memory allocation failed
Explanation	A attempt to allocae memory 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.


%NAT64-3-NAT64_REGISTRY_RC : A NAT64 registry call failed with rc([chars])
Explanation	The return code from a NAT64 registry call indicates an 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.


%NAT64-3-BAD_MAGIC : Invalid magic number(%#10x)
Explanation	An internal data structure is corrupt.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-3-API_FAILED : NULL
Explanation	A call to the API of another component has indicated an 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.


%NAT64-3-RUNAWAY_LOOP : NULL
Explanation	A loop has exceeded the expected number of iterations.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-5-ALIAS_NOT_FOUND : Unable to find alias, address([IP_address]) table_id([int])
Explanation	An attempt was made to remove an IP alias for a NAT64 address and the alias does not exist. This is a notification that such an event happened and should not have any functional impact. This could happen under heavy load if, for example, a previous best effort message to add the alias was dropped.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-6-HA_RELOAD : Reloading [chars], reason([chars])
Explanation	A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-6-HA_RELOAD_DISABLED : Standby reload has been disabled, NAT64 RP state is out of sync and the standby should be reloaded manually
Explanation	The active and standby RPs are out of sync and the standby RP would have been reloaded, but this reload was suppressed based on the configured environment.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NAT64-6-HA_PEER_READY : NULL
Explanation	The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action


%NAT64-6-HA_FLOW_CTRL_TIMEOUT : Bulk sync is flow controlled by [chars]
Explanation	The bulk synchronization of the NAT64 configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

NATMIB_HELPER


%NATMIB_HELPER-3-NOCREAT : NATMIB Helper Process not created - NAT MIB will not work properly
Explanation	Attempt to start NATMIB Helper Process failed whenthe natmib subsystem was initialised.
Recommended Action	The NATMIB Helper process was notcreated,possibly due to lack of memory. If you want to use the NATMIB, reconfigure the box so that less memory is used byother features, or add more memory to the system. Reload the boxafter reconfiguring.

NCS4200IM


%NCS4200IM-3-INCOMPATIBLE : [chars]-[dec]
Explanation	P1D and onwards, Cu IM.... is not backward compatible with P1A/P1B/P1C Cu IM, use the same build of Cu IM or reload the router to use the new build.
Recommended Action


%NCS4200IM-3-UNSUPPORTED : This Interface Module is not supported in subslot [dec]
Explanation	The inserted IM is not supported in the specified subslot. Kindly check the supported slots for the IM type.
Recommended Action


%NCS4200IM-3-UNSUPPORTED_PLATFORM : This Interface Module is not supported in [chars] platform
Explanation	The inserted IM is not supported in the specified platform
Recommended Action


%NCS4200IM-3-DIFF_IM_INSERTED : [chars] - [chars] in bay [dec]
Explanation	A different IM type has been inserted in the bay which previously had another IM type. If the interfaces were set to default before swap, the IM will boot up fine. If not, IM will goto Out-of-service state. Kindly insert the previous IM type, use hw-module subslot 0/x default and then proceed with the IM swap. If not, might need to reload the box for recovery
Recommended Action


%NCS4200IM-3-INVALID_COMBINATION : [chars] is not allowed in bay [dec], can be supported only in bay(s) [chars]
Explanation	The inserted IM is not supported in the specified subslot given the combination of existing IMs in the chassis.
Recommended Action


%NCS4200IM-3-INVALID_MODE : [chars] with mode [chars] is not allowed in bay [dec], can be supported only in bay(s) [chars]
Explanation	The inserted IM is not supported in the specified subslot given the combination of existing IMs in the chassis.
Recommended Action

NCS4200INTF


%NCS4200INTF-3-UNSUPPORTED : Interface [chars] is not supported in subslot [dec] by the [chars] module
Explanation	The Interface specified in the error message is not supported in the specified Subslot by the version of the operating system currently running on the system.
Recommended Action

NCS4200_RP_ATM_SPA


%NCS4200_RP_ATM_SPA-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED : total active atm vc per ATM SPA reached limitation of [dec]
Explanation	total number of active atm vc per ATM SPA has reached max limit
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

NDBMAN


%NDBMAN-5-ACTIVE :
Explanation	All data providers active.
Recommended Action	Informational only. No action required.


%NDBMAN-5-RESET :
Explanation	At least one data provider has stopped.
Recommended Action	Informational only. No action required.

NDBUTIL


%NDBUTIL-4-OUT_OF_RANGE_FOR_DECIMAL64_AND_FD : Double (%1$s) with value (%2$lf) is out-of-range (-%3$ld to %3$ld, exclusive) for a Decimal64 with fraction-digits = %4$d.
Explanation	The value of the EI double cannot be reliably converted to Yang Decimal64 with the specified fraction-digits with the proper precision, so the EI to Yang conversion is intentionally failing. The EI value should not be this big, so there's an error with the module setting the attribute's value.
Recommended Action	Report an error to the Cisco engineering team responsible for the module that's setting the attribute.

NETCLK


%NETCLK-5-NETCLK_CHANGE : Network clock source transitioned from priority [dec] [chars] to priority [dec] [chars]
Explanation	This notice indicates a change in the clock source.
Recommended Action	No action required.


%NETCLK-5-NETCLK_MODE_CHANGE : Network clock source not available. The network clock has changed to [chars]
Explanation
Recommended Action	No action required


%NETCLK-5-NETCLK_PHASE_LOST : Network clock source not available. Phase-lost on clock priority [dec] [chars]
Explanation
Recommended Action	No action required


%NETCLK-4-NETCLK_CMD_FAIL : NULL
Explanation	This message indicates that a network clock command from RP to IOS-SR or SPAs has failed
Recommended Action	The message can be ignored if the carrier card was reloaded or powered down. Otherwise, LOG_STD_SH_CMD_ACTION(show logging and show network-clocks)


%NETCLK-6-SRC_REM : Synchronization source [chars] is removed from [chars] selection process.
Explanation	Synchronization source is removed from synchronization source selection process(es), i.e. T0 or selection process per T4. Source Removal is always through configuration.
Recommended Action	No action is required.


%NETCLK-6-ALL_SRC_REM : All synchronization sources have been removed from [chars] selection process.
Explanation	All synchronization sources are removed from synchronization source selection process(es), i.e. T0 or selection process per T4. Source Removal is always through configuration.
Recommended Action	No action is required.


%NETCLK-6-SRC_ADD : Synchronization source [chars] is added to [chars] selection process.
Explanation	Synchronization source is added to synchronization source selection process(es), i.e. T0 or selection process per T4. Source Addition is always through configuration.
Recommended Action	No action is required.


%NETCLK-6-SRC_UPD : Synchronization source [chars] status [chars] is posted to all selection process.
Explanation	Synchronization source status (event) is updated to synchronization source selection process(es), i.e. T0 or selection process per T4. Status update is in the message.
Recommended Action	No action is required.


%NETCLK-6-SEL_CLOCK_SRC : Synchronization source [chars][chars] is selected by selection process(T0) to synchronize the system and generate [chars] output[chars]
Explanation	Synchronization source selection process has selected source q receive clock to synchronize the system and generate T0(transmit SEC clock). T0 clock is used as TX clock on all participating slots.
Recommended Action	No action is required.


%NETCLK-6-SEL_T4_CLOCK_SRC : Synchronization source [chars] is selected by selection process to synchronize the system and generate T4([chars]) output[chars]
Explanation	Synchronization source selection process for T4(external interface) has selected source q receive clock to synchronize external interface transmit clock.
Recommended Action	No action is required.


%NETCLK-6-ENTER_HOLDOVER : System Internal synchronization source is selected.
Explanation	System Internal synchronization source Internal is selected as all other nominated synchronization source are not valid for Synchronization selection process.
Recommended Action	No action is required.


%NETCLK-6-INV_QL : invalid QL [chars] received for [chars] on network option [chars].
Explanation	The platform has notify RP the clock quality of an input source. But the value appears to be invalid based on the current configured network option.
Recommended Action	No action is required.


%NETCLK-4-FAIL : The Network Clock protocol has encountered the error: [chars].
Explanation	The protocol has run into a failure condition. The reason should be given in the parenthesis.
Recommended Action	LOG_STD_SH_CMD_ACTION( show network-clock synchronization and show network-clock synchronization detail and show module)


%NETCLK-4-PD_REG : [chars] [dec]
Explanation	The platform has failed to provide the protocol one of the mandatory functions.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETCLK-6-QL_CHANGE : Input QL for [chars] is [chars]
Explanation	The input QL used for a network-clock input changed
Recommended Action	No action is required.


%NETCLK-3-ESMC_EVENT_CREATE_FAIL : Failed to create ESMC event.
Explanation	Failed to create an ESMC event to be queued.
Recommended Action	No action is required.


%NETCLK-3-ESMC_EVENT_ENQUEUE_FAIL : Failed to enqueue ESMC event.
Explanation	Failed to add an ESMC event to the event queue.
Recommended Action	No action is required.


%NETCLK-3-ESMC_EVENT_QUEUE_INIT_FAIL : Failed to initialize ESMC event queue.
Explanation	Failed to initialize the ESMC event queue.
Recommended Action	No action is required.


%NETCLK-3-ESMC_EVENT_QUEUE_ALLOC_FAIL : Failed to allocate memory for ESMC event queue.
Explanation	Failed to allocate memory for the ESMC event queue.
Recommended Action	No action is required.

NETWORK_CLOCK_SYNCHRONIZATION


%NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_FAIL : Active network clock source [chars], priority [dec] failure
Explanation	This warning message indicates that there has been a failure of active clock source
Recommended Action	No action required


%NETWORK_CLOCK_SYNCHRONIZATION-6-NETCLK_ACTIVE : Active network clock source is [chars], priority [dec]
Explanation	This indicates the presence of an active network clock along with its priority
Recommended Action	This is an informational message only, no action required.

NETWORK_RF_API


%NETWORK_RF_API-6-IDB_TRANSITIONS_PENDING : Switchover terminated with [dec] transitions pending after there was no transition activity for [dec] seconds
Explanation	The system terminated the switchover idb transitioning phase with a number of idb transitions still pending because no switchover related IDB transitions were logged during the specified time interval. Some connected routes may experience a temporary loss of traffic.
Recommended Action	No action is required.


%NETWORK_RF_API-3-FAILSENDMSGTOSTDBY : Failed to send [chars] message to standby for [chars], rc=[dec]
Explanation	The specified synchronization message, which is an internal IPC message, could not be sent to the standby unit in the specified run-time module. The failure most likely occurred because of a software error. The numeric error code 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-FAILSENDMSGTOACTIVE : Failed to send [chars] message to active for [chars], [chars]
Explanation	The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-FAILDECODEDATADESC : Cannot decode data descriptor for [chars], descriptor type=[chars]
Explanation	An internal data descriptor could not be decoded 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 descriptor the failure occurred with. 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 both the active and the standby units. LOG_STD_SH_CMD_ACTION(show redundancy idb-sync-history)


%NETWORK_RF_API-3-NO_MSG_BUFFER : No message buffer for [chars]
Explanation	A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.
Recommended Action	If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, LOG_STD_SH_TECH_ACTION


%NETWORK_RF_API-3-NO_CHKPT_BUFFER : No checkpointing buffer for [chars], rc=[dec]
Explanation	A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.
Recommended Action	If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, LOG_STD_SH_TECH_ACTION


%NETWORK_RF_API-3-INVALID_MSG_RECEIVED : Invalid [chars] message received
Explanation	A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-INVALID_CHKPT_STATUS_CODE : Invalid checkpointing status code received, rc=[dec]
Explanation	An invalid checkpoint status code has been detected. An internal status code that is associated with checkpointing was found to be invalid. The return code that is specified in the message output identifies the invalid code that was detected. The failure most likely occurred because of a software error. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-CLIENT_REGISTER_FAIL : Failed to register with [chars], rc =[dec]
Explanation	A redundancy client could not be registered. An internal failure associated with client registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-NO_RESOURCES : [chars]
Explanation	A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action	If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, LOG_STD_SH_TECH_ACTION


%NETWORK_RF_API-3-ISSU_REG_SES_INFO : Failed to register ISSU session information: [chars]
Explanation	The system failed to register the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-ISSU_UNREG_SES_INFO : Failed to register ISSU session information: [chars]
Explanation	The system failed to unregister the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-ISSU_START_NEGO_SES : Failed to start ISSU session: [chars]
Explanation	The system failed to start the ISSU negotiation session required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-ISSU_MSG_TYPE_INCOMPAT : The active and standby ISSU message types are incompatible
Explanation	A message that is used for state synchronization is deemed to be incompatible. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-ISSU_TRANSFORM_FAIL : The ISSU message [chars] transformation failed: [chars]
Explanation	A message that is used for state synchronization could not be transformed correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-ISSU_MSG_MTU_INVALID : The ISSU message MTU is invalid: [chars]
Explanation	A message buffer size that is used for state synchronization was found to be invalid. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. 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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%NETWORK_RF_API-3-CHKPT_ENTITY_FAIL : A checkpointing entity [chars] operation failed, rc=[dec]
Explanation	An internal operation that is associated with checkpointing failed. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.
Recommended Action	Issue 'show checkpoint entities' and 'show checkpoint clients' to determine the problem

NIF_MGR through ONEP_LISP

NIF_MGR
NIM_XXD
NTP
OBJGROUP
OCE
OCE_PUNT_PROCESS
OIR
OLM
ONEP_BASE
ONEP_LISP

NIF_MGR


%NIF_MGR-6-PORT_CONN_READY : [chars] on front side stack link [dec] connection is READY.
Explanation	A port associated with a front side stack link has a ready connection.
Recommended Action	No action is required


%NIF_MGR-6-PORT_CONN_PENDING : [chars] on front side stack link [dec] connection is PENDING.
Explanation	A port associated with a front side stack link has a pending connection.
Recommended Action	No action is required


%NIF_MGR-6-PORT_CONN_ERR : [chars] on front side stack link [dec] connection is in ERR-DISABLE: [chars]
Explanation	A port associated with a front side stack link has reached err-disable state.
Recommended Action	No action is required


%NIF_MGR-6-PORT_CONN_TIMEOUT : [chars] on front side stack link [dec] connection has TIMEOUT: [chars]
Explanation	A port associated with a front side stack link has disconnected connection.
Recommended Action	No action is required


%NIF_MGR-6-PORT_CONN_DISCONNECTED : [chars] on front side stack link [dec] connection has DISCONNECTED: [chars]
Explanation	A port associated with a front side stack link has disconnected connection.
Recommended Action	No action is required


%NIF_MGR-6-PORT_LINK_UP : [chars] on front side stack link [dec] is UP.
Explanation	A port associated with a front side stack link has come up.
Recommended Action	No action is required


%NIF_MGR-6-PORT_LINK_DOWN : [chars] on front side stack link [dec] is DOWN.
Explanation	A port associated with a front side stack link has come up.
Recommended Action	No action is required


%NIF_MGR-6-STACK_LINK_UP : Front side stack link [dec] is UP.
Explanation	A port associated with a front side stack link has come up.
Recommended Action	No action is required


%NIF_MGR-6-STACK_LINK_DOWN : Front side stack link [dec] is DOWN.
Explanation	A port associated with a front side stack link has come up.
Recommended Action	No action is required


%NIF_MGR-6-PORT_CONNECTION_STATUS_CHANGE : PORT:[chars] changed state from [chars] to [chars].
Explanation	FSS Stack Port status change message.
Recommended Action	No action is required


%NIF_MGR-6-DAD_RECOVERY_MODE : Dual Active detected: Switch going into recovery mode. [chars].
Explanation	Dual Active detected print on console.
Recommended Action	This switch need to be reloaded once user finishes debugging


%NIF_MGR-6-DAD : Dual Active detected: [chars]
Explanation	Dual Active detected print on console.
Recommended Action	No action. Action is only after recovery mode


%NIF_MGR-6-DAD_RECOVERY_RELOAD_ALERT : Switch is in recovery mode, needs Reload now. [chars].
Explanation	Switch is in recovery mode, needs Reload now
Recommended Action	This switch need to be reloaded since some correction is noticed


%NIF_MGR-6-DOMAIN_NUMBER_MISMATCH : Stackwise virtual domain number mismatch on stackwise virtual link [dec]
Explanation	A port associated with a stackwise virtual link is connected to a peer with a different domain number than the local switch
Recommended Action	For the switch to form a stack please configure same domain numbers on both the switches

NIM_XXD


%NIM_XXD-3-DISK_REMOVAL : One or more disks in SPA ([chars]) in subslot [dec]/[dec] can not be detected. Please power down this SPA and insert disk(s).
Explanation	Disks have been removed from SPA
Recommended Action	Power down the SPA, insert disks and power up the SPA.


%NIM_XXD-3-DISK_ERROR : Error detected on disk [dec] in module [chars] in subslot [dec]/[dec]. [chars].
Explanation	Disk error detected in the SPA (NIM-SSD/NIM-HDD). Refer to comment for details.
Recommended Action	Back-up any data and replace the disk.


%NIM_XXD-5-DISK_MONITOR : Disk [dec] in module [chars] in subslot [dec]/[dec] is detected but monitoring is not available.
Explanation	Monitoring of disk in SPA (NIM-SSD/NIM-HDD) is unavailable.
Recommended Action	Add a database file with monitoring information for this disk model and manufacturer.

NTP


%NTP-6-RESTART : NTP process starts
Explanation	NTP process has just started or re-started.
Recommended Action	No action is required.


%NTP-6-STOP : NTP process stops
Explanation	NTP is disabled.
Recommended Action	Check if NTP is disabled by administrator purposely.


%NTP-4-UNSYNC : NTP sync is lost
Explanation	NTP synchronization to its peer is lost.
Recommended Action	Check network connection to the peer, if NTP is running on the peer, if the peer itself is synchronized to a stable time source, and if NTP packets from the peer have passed validity tests specified in the RFC1305 etc.


%NTP-4-PEERUNREACH : Peer [IP_address] is unreachable
Explanation	The NTP peer is unreachable.
Recommended Action	Check network connection to the peer and if NTP is running on the peer.


%NTP-6-PEERREACH : Peer [IP_address] is reachable
Explanation	The NTP peer is reachable.
Recommended Action	No action is required.


%NTP-5-PEERSYNC : NTP synced to peer [IP_address]
Explanation	NTP has synchronized the local clock to a new peer.
Recommended Action	No action is required.


%NTP-4-V6DISABLED : IPv6 is not running on interface [chars]. Cannot send NTP message.
Explanation	Some NTP IPv6 specific commands are configures on an interface on which IPv6 is not running
Recommended Action	Enable IPv6 on the interface

OBJGROUP


%OBJGROUP-3-QFAIL : Failed to perform queue operation '[chars]'
Explanation	Operation to perform processing on internal queue 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.


%OBJGROUP-3-CREATEFAIL : Failed to create/initialize internal data structures
Explanation	Operation to create/initialize internal data structures 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.


%OBJGROUP-3-CLASSMAP : Failed to perform classmap filter [chars] operation
Explanation	Operation to modify classmap filter 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.


%OBJGROUP-4-BADREFCNT : Bad reference counter classmap '[chars]' sgtid [int] filter [int]
Explanation	Reference counter value indicates database inconsistency.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OBJGROUP-4-INVALIDFILTER : Invalid filter type [int] for classmap '[chars]'
Explanation	Filter type for match statement was unknown/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.


%OBJGROUP-4-EINVAL : Unexpected input value
Explanation	An unexpected input value to a function was incorrect
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OBJGROUP-4-BADCHILD : Object-group '[chars]' has bad child '[chars]'
Explanation	Object-group has reference to invalid child object-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.


%OBJGROUP-4-BADCLASSMAP : Internal match structure points to invalid class-map '[chars]'
Explanation	Object-group has reference to invalid child object-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.


%OBJGROUP-4-BADMATCH : Invalid internal match structure in class-map '[chars]' type [int]
Explanation	Object-group has reference to invalid match
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OBJGROUP-4-BADOG : Reference to non-existent object-group '[chars]'
Explanation	Internal structure references non-existent object-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.


%OBJGROUP-4-INVALIDCMD : Invalid subcommand [int]
Explanation	Attempt to configure invalid subcommand
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OBJGROUP-4-TOOMANYSGT : Exceeded maximum allowed SGT's ([int]) in a class-map group-object match statement
Explanation	The cumulative number of SGTs in a class-map match statement has exceeded the maximum allowed. The number of SGTs includes those in object-groups as well as child object-groups within the heirarchy.
Recommended Action	Limit the number of SGTs in the object-group heirarchy referenced by the class-map match statement

OCE


%OCE-3-OCE_SET_WRONG_PATH : Attempting to add an oce to the set contributed by path/list [IPV6 address]/[IPV6 address] while set set belongs to [IPV6 address]
Explanation	Failed to enqueue a unlock for an oce, this may lead to a memory leak
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-QUEUE_UNLOCK : Failed to [chars] unlock[chars] for [chars] oce [IPV6 address]
Explanation	Failed to enqueue a unlock for an oce, this may lead to a memory leak
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-OCEDEPDUMP : [chars]
Explanation	An error condition triggered display of oce dependents
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-UNINITIALIZED_VECTOR : Improperly initialized [chars] vector in [chars] OCE bundle [IPV6 address], packet dropped
Explanation	An OCE bundle vector was improperly 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-MISSING_HANDLER_FOR_SW_OBJ : Missing handler for '[chars]' function
Explanation	An internal API request has been ignored because it was unexpected
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-MISSING_HANDLER_FOR_SW_OBJ_TYPE : Missing handler for '[chars]' function for type [chars]
Explanation	An internal API request has been ignored because it was unexpected
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-OCE_CHANGED_BY_APPLY_FUNCTION : Target OCE [IPV6 address] changed to [IPV6 address] by apply function [IPV6 address]
Explanation	An internal API request has been ignored because it was unexpected
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-UNEXPECTED_SW_OBJ_TYPE : SW_OBJ handle/type mismatch; expecting oce type [chars], found [dec]
Explanation	An internal API request has been ignored because it was unexpected
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-OCE_FWD_STATE_HANDLE : Limit of oce forward state handle allocation reached; maximum allowable number is [int]
Explanation	Did not store the reinject forwarding state handle, as the maximum number of handles are already in use
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-OCE_FWD_STATE_HANDLE_INIT : Failed to initialize a stack of reusable forward state handles; at element [int], initial stack size is [int] elements
Explanation	Could not allocate enough forwarding state handles for initial handle reuse
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-UNEXPECTED_DISP_TYPE : Unexpected disposition type is encounted; expecting disposition types are [chars], found [chars]
Explanation	An internal disposition counter measure request has been ignored because it was unexpected
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-DECREASE_ZERO_REFCOUNT : Try to decrease zero refcount for [chars] oce [IPV6 address]
Explanation	Attempt to decrease the refcount of oce when it is already zero
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-INTERRUPT_LEVEL_LAST_LOCK : Try to remove last lock for [chars] oce [IPV6 address] at interrupt
Explanation	Attempt to delete oce while not at process level
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-GENERAL : [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.


%OCE-3-LOOP : A loop in the OCE chain has been detected at: [chars][[IPV6 address]]
Explanation	A loop in the OCE chain has been 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE-3-EXCEED_OCE_COUNTER_LIMIT : Exceeded OCE push counter limit (functs:[IPV6 address] counter:[IPV6 address])
Explanation	At most OCE_MAX_COUNTERS oce counters can be added because of design restrictions.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

OCE_PUNT_PROCESS


%OCE_PUNT_PROCESS-3-NORESOURCE : [chars] [dec]
Explanation	Resource Failure: %s %d
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OCE_PUNT_PROCESS-3-LABEL_CACHE_INVALID : [chars]
Explanation	MPLS label cache was invalid, failed to handle exception
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

OIR


%OIR-6-REMCARD : Card removed from slot [dec], interfaces disabled
Explanation	The OIR facility detected the removal of a processor from the slot number specified in the error message. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action	No action is required.


%OIR-6-INSCARD : Card inserted in slot [dec], interfaces administratively shut down
Explanation	The OIR facility detected a newly inserted processor. The interfaces associated with that processor are operational, but will be shut down until they are configured by the user. If any interfaces of that type were previously configured, they will be restored to their previous state.
Recommended Action	No action is required.


%OIR-3-LONGSTALL : Long bus stall ([int] ms), check for improperly seated cards
Explanation	An online insertion or removal of an interface processor card has stalled the backplane bus for longer duration than expected.
Recommended Action	Make sure all interface processor cards are inserted or removed. LOG_STD_ACTION_ERR


%OIR-4-NOEOIR : [chars] [chars] version [int].[int] not capable of EOIR
Explanation	This message indicates that this card is capable of Online Insertion and Removal (OIR) hot-swapping but is not capable of Extended Online Insertion and Removal (EOIR). Though no damage would occur to the hardware, insertion or removal of the card will cause a CBUS complex restart, which would be disruptive to traffic on other cards in the system.
Recommended Action	Try to restrict insertion or removal of this card to times when a CBUS complex restart will be least disruptive. Or upgrade the card to the latest revision which supports EOIR.


%OIR-3-SEATED : Insert/removal failed for slot [dec], check card seating
Explanation	The OIR facility detected an incorrectly seated card, causing the insertion or removal of this card to fail.
Recommended Action	Reseat the card in the indicated slot.


%OIR-3-CRASH : The module in slot [dec] has crashed
Explanation	The module in the slot indicated has crashed and will be rebooted by the supervisor.
Recommended Action	Collect the crashinfo file from the crashed module and contact support.

OLM


%OLM-3-ILLEVT : State [chars]; Event [chars]
Explanation	An LMP state machine has encountered an event that is not legal or allowed in the current state.
Recommended Action	Write down the state and the event and call your Cisco technical support representative for assistance


%OLM-5-LSUMBADTEL : Invalid TE Link ID [int] in Link Summary message
Explanation	A Link Summary or Link Summary Ack or Link Summary Nack message has been received with bad TE Link ID. The sending node probably doesn't have LMP configured correctly.
Recommended Action	Locate the neighbor from which the LMP message with invalid TE Link ID was received and enter show ip olm command and make sure that the port ID mappings between the two nodes are correct


%OLM-5-LMPNOIPCC : Internal error: Couldn't find IPCC to send LMP msg; msg type : [int]
Explanation	This is generally caused by race conditions wherein an LMP message is received from a neighbor before the first control channel goes UP [locally]. This conditions usually happens when a node reboots.
Recommended Action	If the problem persists even after the node has completed initialization, enter sho ip olm command to find the LMP configuration and use the debug ip lmp packets and debug ip lmp generic command to gather additional context type information and call Cisco technical assistance.


%OLM-3-LMPNONBR : Internal error: Couldn't find neighbor while [chars]
Explanation	An LMP processing that requires to access information about the neighbor has found that no such neighbor exists. This could be due to internal error.
Recommended Action	Turn on generic and packet level debugging using the command, debug ip lmp and gather LMP configuration using the command, show ip olm and gather the displayed information and contact Cisco technical assistance.


%OLM-5-LMPUNKSRC : LMP rcvd msg from unknown src ip 0x[IP_address], link %
Explanation	An LMP message has been received from a neighbor that we don't know about. This could be due to the fact that the neighbor in question has not yet been configured on this node.
Recommended Action	Locate the problem neighbor using the IP address and enter a show ip olm command; gather the displayed info and contact Cisco technical assistance.


%OLM-4-LMPINVTLV : Invalid TLV Length [int] in LMP msg; remaining size [int]
Explanation	An LMP message has been received with invalid TLV length. This suggests that we have a broken LMP implementation on the sending neighbor.
Recommended Action	Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance.


%OLM-3-LMPSNDFAIL : Failed to send LMP msg to [chars]
Explanation	Attempt to send LMP control message has failed; this could be due to an 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.


%OLM-5-LSUMMISMATCH : Link Summary parameter([chars]) mismatch
Explanation	Port ID and other link summary parameters do not match with those on the neighbor in question. The neighbor and/or the local node is not properly configured.
Recommended Action	Enter the show ip olm command on the local as well as the neighbor node and make sure that the port IDs match.


%OLM-4-LMPBADTLV : Bad TLV; type [int]
Explanation	An LMP message has been received with invalid TLV type. This suggests that we have a broken LMP implementation on the sending neighbor
Recommended Action	Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance.


%OLM-4-LMPBADMSG : Bad LMP Msg; type [int]
Explanation	An LMP message has been received with invalid message type. This suggests that we have a broken LMP implementation on the sending neighbor
Recommended Action	Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance.


%OLM-5-LMPNONBR1 : No such neighbor to assign
Explanation	User attempted to assign interface to invalid neighbor
Recommended Action	Use show olm to find the correct neighbor name


%OLM-2-LMPCONSIST : Internal consistency error; [chars]
Explanation	An internal consistency error has been encountered during the said 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.


%OLM-5-LMPMSGSEQ : LMP [chars] msg id [int] not 1+[int]
Explanation	An LMP message has been received with message id that is not sequential within the Control channel or TE Link. This situation is not caused by the known cases that cause message id sequence to be broken, including local node reboot, neighbor node reboot and neighbor retransmission
Recommended Action	Enter the show ip olm stat command when this problem occurs and gather the information displayed and call the Cisco technical assistance.


%OLM-3-LMPSDMISMATCH : Service Discovery: Attribute [chars] incompatible with neighbor [chars]
Explanation	Specified service attribute does not match with neighbor. The neighbor and/or the local node may not be properly configured.
Recommended Action	Use the `show mpls uni lmp neighbor` command on the local as well as the neighbor node (where applicable), to determine the service attributes and modify the configuration, where feasible, to ensure that the attributes match


%OLM-3-LMPSDPORTFAILED : Service Discovery: Attributes for port [chars] incompatible with nbr [chars]
Explanation	Port-level service attribute does not match with those of the neighbor. The neighbor and/or the local node may not be properly configured.
Recommended Action	Use the `show mpls uni lmp neighbor` command on the local as well as the neighbor node (where applicable), to determine the service attributes and modify the configuration, where feasible, to ensure that the port-level service attributes match

ONEP_BASE


%ONEP_BASE-3-VERSION_ERR : [[chars]]: ONE-P version incompatible between client and network element. [chars]
Explanation	The ONE-P client service set version is incompatible with the one installed on the network element
Recommended Action	LOG_STD_SH_CMD_ACTION( Make sure the version running on the client side is compatible with the one installed on the network element )


%ONEP_BASE-3-DISABLED_ERR : [[chars]]: [chars] is disabled.
Explanation	The requested service set is in disabled state. All the service requests for that service set will be rejected.
Recommended Action	LOG_STD_SH_CMD_ACTION( Make sure the service set is enabled. onep service set <name>)


%ONEP_BASE-6-SS_ENABLED : ONEP: [chars]
Explanation	The service set has been set to an enabled state. The features of the service set will be available for use.
Recommended Action	LOG_STD_SH_CMD_ACTION( If the enablement was intentional, no action is required.)


%ONEP_BASE-6-SS_DISABLED : ONEP: [chars]
Explanation	The service set has been set to a disabled state. All service requests for that service set will be rejected.
Recommended Action	LOG_STD_SH_CMD_ACTION( If the disablement was intentional, no action is required. If not, then enable the service set: onep service set <name>)


%ONEP_BASE-3-DUPLICATE_ERR : [[chars]]: Requested entity [chars] already exists.
Explanation	The connection request to the network element already exists
Recommended Action	LOG_STD_SH_CMD_ACTION( Make sure the uniqueness of the application name. One session per application is allowed on a network element.)


%ONEP_BASE-3-AUTHEN_ERR : [[chars]]: Authentication/authorization failed. [chars]
Explanation	The session authentication has failed
Recommended Action	LOG_STD_SH_CMD_ACTION( Check user's credentials are matched against the AAA/local users configured on the Netwk Element.)


%ONEP_BASE-3-BUSY_ERR : [[chars]]: The requested resource is currently busy. [chars].
Explanation	The usage of the resource has exceeded the configured threshold value
Recommended Action	LOG_STD_SH_CMD_ACTION( Check the current resource usage and configured resource threshold. cpu threshold rising <value> falling <value> interval <seconds> Retry the operation if resource usage is below the threshold.)


%ONEP_BASE-3-SESSION_ERR : [[chars]]: ONEP session maximum is exceeded. [chars].
Explanation	The application session has exceeded the configured maximum
Recommended Action	LOG_STD_SH_CMD_ACTION( Check the configured session maximum value, and adjust accordingly. >session max <value> Retry the session establishment or adjust the configured session maximum.)


%ONEP_BASE-3-STARTUP_ERR : [[chars]]: Start up ONEP failed. [chars].
Explanation	Fail to start ONEP due to error
Recommended Action	LOG_STD_SH_CMD_ACTION( Check transport is configured correctly or reboot the device)


%ONEP_BASE-4-CLEAR_TEXT_TRANSPORT_WARN : [[chars]]: Clear text transport being enabled. This is not recommended for production environment. [chars]
Explanation	Clear text transport being enabled. This is not recommended for production environment.
Recommended Action	LOG_STD_SH_CMD_ACTION( Please configure secure transport, such as TLS.)


%ONEP_BASE-6-HISTORY : [chars]
Explanation	This syslog message is used to display onePK history messages when the 'history syslog' onep command is enabled.
Recommended Action	LOG_STD_SH_CMD_ACTION( No action is required. Use 'no history syslog' at the onep configuration prompt to turn off this logging if desired.)


%ONEP_BASE-6-CONNECT : [[chars]]: ONEP session [chars] has connected.
Explanation	A new ONEP session has been established with network element.
Recommended Action	LOG_STD_SH_CMD_ACTION( No action is required if this is an authorized session.)


%ONEP_BASE-6-RECONNECT : [[chars]]: ONEP session [chars] has reconnected.
Explanation	ONEP session has been reconnected after being disconnected temporarly. This disconnect can happen due to intermittent network connectivity issues.
Recommended Action	LOG_STD_SH_CMD_ACTION( No action is required if this is an authorized session.)


%ONEP_BASE-6-DISCONNECT : [[chars]]: ONEP session [chars]
Explanation	ONEP session has been disconnected. A disconnect can happen when application has finished execution or there was a problem during execution including issue with network transport. If reconnect timer is configured, Network Element will wait for application to reconnect within configured time before cleaning up session resources.
Recommended Action	LOG_STD_SH_CMD_ACTION( No action is required if it is a expected disconnected. If reconnect timer is configured, session will wait for application to attempt reconnect request Use show tech-support onep to collect logs from Network Element)

ONEP_LISP


%ONEP_LISP-3-DISABLED_ERR : [[chars]]: [chars] is disabled.
Explanation	The requested service set is in disabled state. All the service requests for that service set will be rejected.
Recommended Action	LOG_STD_SH_CMD_ACTION( Make sure the service set is enabled. onep service set lisp)

OOM through PBUF

OOM
OPENDNS_PROXY
OSC
OTNMGR
PAD
PAM_UPDB
PATHMGR
PA_PKT
PA_PKT_PROXY
PBUF

OOM


%OOM-3-NO_MEMORY_AVAIL : The system is very low on available memory. Operations will begin to fail.
Explanation	The system has exhausted all available memory. It is not possible to continue stable operation.
Recommended Action	The system has exhausted all available memory and stable operation is no longer possible.


%OOM-0-NO_MEMORY_RESET : The system is completely out of available memory. The board will be reset.
Explanation	The system has exhausted all available memory and the hardware component will be reset.
Recommended Action	Review other messages related to low memory states and see if those messages contain any information about an issue that can be addressed. If this problem persists, copy all the output from the console as well as the output of show tech-support, and provide the gathered information to your Cisco technical support representative.

OPENDNS_PROXY


%OPENDNS_PROXY-2-OPENDNS_MSG_PROXYINIT_FAILURE : UMBRELLA - Failed to register IPC message handler, result code [int]
Explanation	QFP Umbrella feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to 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.


%OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_UNKNOWN_IPCMSG : UMBRELLA - Received an unknown type (code [int]), IPC message
Explanation	QFP Umbrella feature received an unknown message from another layer of Umbrella feature's software stack.
Recommended Action	If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_INVALID_MSGLEN : UMBRELLA - Received an invalid length IPC message
Explanation	QFP Umbrella feature received an incorrect length of IPC message from anoter layer of Umbrella feature's software stack, m_enum %d, m_subtype %d, m_len %d, m_flags 0x%x, m_source %d.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_ALLOC_FAILURE : UMBRELLA - Failed to get [int] bytes space for IPC reply message
Explanation	QFP Umbrella feature detected buffer allocation failure while sending reply to a message from another layer of Umbrella feature's software stack.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_OPENREPLY_FAIL : UMBRELLA - Failed to open reply message part of IPC packet
Explanation	QFP Umbrella feature failed to open message part of IPC packet while sending a reply to another layer of Umbrella feature's software stack.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_IPCSEND_FAIL : UMBRELLA - Failed to send IPC message, result code [dec]
Explanation	QFP Umbrella feature failed to send IPC message to another layer of Umbrella feature's software stack.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%OPENDNS_PROXY-3-OPENDNS_MSG_PROXY_DEBUG_REG_FAILED :
Explanation	Umbrella Conditional Debugging 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.

OSC


%OSC-3-DCDI : DATACORRUPTION-DATAINCONSISTENCY: [chars]
Explanation	Software has detected that some internal data structures may be corrupt. This may lead to unpredictable device operation
Recommended Action	Copy the error message exactly as it appears on the console or in the in the system log, and report it your technical support representative.

OTNMGR


%OTNMGR-3-OTN_STATS_CREATE_IF_FAILED_TO_ALLOCATE : stats for interface index [dec] could not be created with status [dec]
Explanation
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%OTNMGR-3-OTN_STATS_CREATE_IF_FAIL : stats for interface index [dec] could not be created with status [dec]
Explanation
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%OTNMGR-3-OTN_STATS_DELETE_IF_FAIL : stats for interface index [dec] could not be deleted with status [dec]
Explanation
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

PAD


%PAD-3-GETLINE : Tty%t, bad return code [dec] from x3_getline()
Explanation	An internal software error occurred.
Recommended Action	If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.


%PAD-2-PUTSETUP : Tty%t, buffer already setup
Explanation	An internal software error occurred.
Recommended Action	If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.


%PAD-2-INTR : [chars] called at interrupt level [hex]
Explanation	An internal software error occurred.
Recommended Action	If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.

PAM_UPDB


%PAM_UPDB-3-NOPROMPT_READ : Error reading [chars] prompt: [chars]
Explanation	The authentication module was unable to read the specified prompt file. The default prompt will be used.
Recommended Action	If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PAM_UPDB-3-NOENVIRONMENT_SET : Error setting user in application environment: [chars]
Explanation	The user has succesfully authenticated, but the user information could not be saved to the application environment. The user session will not proceed.
Recommended Action	If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.

PATHMGR


%PATHMGR-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation	For a request from upper PATHMGR 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


%PATHMGR-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation	For a request from upper PATHMGR 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


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

PA_PKT


%PA_PKT-5-PA_DLIST_ALLOC_FAILED :
Explanation	Could not allocate segmented packet list header.
Recommended Action	LOG_STD_ACTION


%PA_PKT-3-PA_VFR_CALLBACK_ARGS_ERROR : [chars] [hex]
Explanation	PA vFR callback input args error.
Recommended Action	LOG_STD_ACTION


%PA_PKT-3-PA_DLIST_MEM_REQ_FAILED :
Explanation	Failure occurred when attempting to request segmented packet memory.
Recommended Action	LOG_STD_ACTION


%PA_PKT-3-PA_MCST_REPL_DESC_OVERFL : [chars], MSGDEF_LIMIT_MEDIUM
Explanation	PA M-Cast Gather descriptor list exceeded limit of 255 entries.
Recommended Action	LOG_STD_ACTION


%PA_PKT-3-PA_MCST_GPM_ALLOC_FAILURE : [chars], MSGDEF_LIMIT_MEDIUM
Explanation	PA M-Cast replication failed to allocate required GPM.
Recommended Action	LOG_STD_ACTION


%PA_PKT-3-PA_MCST_DUP_FAILURE : [chars], MSGDEF_LIMIT_MEDIUM
Explanation	PA M-Cast replication failed to allocate duplicate the requisite PA structures.
Recommended Action	LOG_STD_ACTION


%PA_PKT-3-PA_PUT_FAILURE : [chars], MSGDEF_LIMIT_MEDIUM
Explanation	The PA API layer failed to complete a requested WRITE into pkt memory.
Recommended Action	LOG_STD_ACTION


%PA_PKT-3-PA_ADJUST_FIRST_FRAG_FAILURE : [chars], MSGDEF_LIMIT_MEDIUM
Explanation	PA unaware feature doing pkt_head_clip more than first pbuf on PA pkt.
Recommended Action	LOG_STD_ACTION

PA_PKT_PROXY


%PA_PKT_PROXY-3-PROXY_IPC_EXTENDED_PKT_MEM_INIT_FAILED : [dec]
Explanation	Initialization of extended packet memory failed.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-3-PROXY_IPC_SEG_DLIST_MEM_INIT_FAILED : [dec]
Explanation	Initialization of segmented packet dlist memory failed.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-3-PROXY_IPC_PBUF_MEM_INIT_FAILED : [dec]
Explanation	Initialization of packet buffer header memory failed.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-3-PROXY_IPC_SEG_DLIST_EXTEND_FAILED : [dec]
Explanation	Extending of segmented packet dlist memory failed.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-3-PROXY_IPC_PBUF_EXTEND_FAILED : [dec]
Explanation	Extending of packet buffer header memory failed.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-3-PROXY_IPC_PKT_DRAM_EXTEND_FAILED : [dec]
Explanation	Extending of extended packet memory failed.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-4-PROXY_IPC_UNKNOWN_SUBTYPE : [dec]
Explanation	Unknown IPC message detected.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-2-PROXY_IPC_INIT_FAILED : [dec]
Explanation	Could not initialize IPC handler.
Recommended Action	LOG_STD_ACTION


%PA_PKT_PROXY-3-PROXY_IPC_INVALID_MSG : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation	Invalid length for IPC message.
Recommended Action	LOG_STD_ACTION

PBUF


%PBUF-3-PBUF_MEM_REQ_FAILED :
Explanation	Failure occurred when attempting to request extended packet memory.
Recommended Action	LOG_STD_ACTION


%PBUF-3-PBUF_MEM_INIT_FAILED : [chars]
Explanation	Failure occurred when attempting to create memory resource
Recommended Action	LOG_STD_ACTION


%PBUF-3-PBUF_PKT_MEM_CORRUPT : [hex] [hex]
Explanation	Memory corruption detected while freeing extended packet memory
Recommended Action	LOG_STD_ACTION


%PBUF-3-PBUF_SH_DRAM_CVT_FAIL : [chars]
Explanation	An attempt to convert a shared DRAM buffer to non-shared failed.
Recommended Action	LOG_STD_ACTION

PCE through PKTLOG

PCE
PCMCIAFS
PCM_TRACER
PERF_MEASURE
PERF_MON
PERF_MON_REACT
PERF_TRAFFIC_INFRA
PERF_TRAFFIC_REACT
PKI
PKTLOG

PCE


%PCE-5-PCE_STATE : Connection to PCE server:[chars] [chars]
Explanation	The connection to PCE server changed state.
Recommended Action	If the state change was unexpected check connectivity and state of the PCE server


%PCE-5-PCE_ERR_RX : PCEP peer [chars] sent PCError message - type: [int], value: [int]
Explanation	PCErr message was received from peer
Recommended Action	Verify PCEP protocol operation

PCMCIAFS


%PCMCIAFS-5-DIBERR : [dec] [chars]
Explanation	The system cannot boot a image from the PCMCIA 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.


%PCMCIAFS-3-RESETERR : PCMCIA disk [dec] [chars]
Explanation	PCMCIA 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.


%PCMCIAFS-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.


%PCMCIAFS-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.

PCM_TRACER


%PCM_TRACER-3-PCMT_NO_DEST : No PCM Tracer capture destination configured.
Explanation	Capture destination is required for starting the PCM Tracer.
Recommended Action	Configure capture destination before starting the PCM Tracer.


%PCM_TRACER-3-PCMT_NO_PROFILE : No PCM Tracer profile configured.
Explanation	Capture profile is required for starting the PCM Tracer.
Recommended Action	Configure capture profile before starting the PCM Tracer.


%PCM_TRACER-3-PCMT_NO_CAPTURE_TDM : No capture-tdm configured under profile [int].
Explanation	Capture-tdm is required for starting the PCM Tracer.
Recommended Action	Configure capture-tdm before starting the PCM Tracer.


%PCM_TRACER-3-PCMT_NO_CAPTURE_DURATION : No capture duration configured.
Explanation	Capture duration is required for starting the PCM Tracer.
Recommended Action	Configure capture duration before starting the PCM Tracer.


%PCM_TRACER-3-PCMT_NO_ACTIVE_CALL : No active calls to trace.
Explanation	PCM Tracer can be applied only on active calls.
Recommended Action	Make sure there is an active call before starting the PCM Tracer.


%PCM_TRACER-3-PCMT_RUNNING : A PCM Tracer session is currently running.
Explanation	Can't execute this command since there is a PCM Tracer running now.
Recommended Action	Make sure there is no PCM Tracer sesssion running before execute this command.


%PCM_TRACER-3-PCMT_NOT_SUPPORTED : PCM Tracer 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 PCM Tracer is supported on.


%PCM_TRACER-3-PCMT_CHANNEL_TYPE_NOT_SUPPORTED : The channel/group type of ds0 [int] is not supported by PCM Tracer.
Explanation	Can't execute this command on the ds0 number specified.
Recommended Action	Refer to the user guide for the channel/group type PCM Tracer supports.


%PCM_TRACER-6-PCMT_START : Starting PCM Trace on channel under profile [dec]
Explanation
Recommended Action


%PCM_TRACER-6-PCMT_STOP : Stopping PCM Trace on channel under profile [dec]
Explanation
Recommended Action


%PCM_TRACER-6-PCMT_STOP_FAIL : Fail to Stop PCM Trace on channel under profile [dec]
Explanation
Recommended Action


%PCM_TRACER-6-PCMT_STOP_RUNNING : Stop PCM capture
Explanation
Recommended Action

PERF_MEASURE


%PERF_MEASURE-2-CRIT_ERR : The Perf Measure protocol has encountered the critical error: [chars].
Explanation	The protocol has run into a critical error. The reason should be given in the brackets.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MEASURE-4-ISSU_INCOMPATIBLE : perf-measure-issu-compat: returned FALSE
Explanation	The compatibility checking has failed
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MEASURE-3-TRANSFORM_FAIL : PERF MEASURE ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation	The PERF MEASURE 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 PERF MEASURE 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>)


%PERF_MEASURE-2-GET_BUFFER : PERF MEASURE ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation	The PERF MEASURE 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)


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


%PERF_MEASURE-2-INIT : PERF MEASURE ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation	The PERF MEASURE 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.


%PERF_MEASURE-2-SEND_NEGO_FAILED : PERF MEASURE ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation	The PERF MEASURE 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)


%PERF_MEASURE-2-SESSION_REGISTRY : PERF MEASURE ISSU client failed to register session information. Error: [dec] ([chars])
Explanation	The PERF MEASURE 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>)


%PERF_MEASURE-3-INVALID_SESSION : PERF MEASURE ISSU client does not have a valid registered session.
Explanation	The PERF MEASURE 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>)


%PERF_MEASURE-3-MSG_SIZE : PERF MEASURE ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation	The PERF MEASURE ISSU client failed to calculate the MTU for the specified message. The PERF MEASURE 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>)


%PERF_MEASURE-2-SESSION_NEGO : PERF MEASURE ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation	An ISSU-compliant client transitions through a series of internal states. The PERF MEASURE 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>)

PERF_MON


%PERF_MON-3-LIST : Failed to [chars] list [chars]
Explanation	A list operation failed. This could be caused by memory 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.


%PERF_MON-3-MEM : Memory [chars] failed - [chars]
Explanation	Memory creation failed during the initialization
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MON-3-PARSER : [chars]
Explanation	Parser failure. This could due to invalid command or corrupted csb
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MON-3-CHUNKCREATE : Failed to chunk create memory for [chars]
Explanation	Unable to chunk create memory chunk
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MON-3-CHUNKDESTROY : Failed to chunk destroy memory for [chars]
Explanation	Unable to chunk destroy memory chunk
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MON-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation	Unable to malloc memory chunk, malloc 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.


%PERF_MON-3-DEFRECCREATE : Creation of default-record [chars] failed - reason [chars]
Explanation	Failed to create system defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MON-3-RECSETPROP : Setting property for [chars] default-record failed - reason [chars]
Explanation	Failed to set properties for system defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MON-3-RECSETKEY : Adding key fields for default-record [chars] failed - reason [chars]
Explanation	Failed to add key fields for defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_MON-3-RECSETNONKEY : Adding non-key fieds for [chars] default-record failed - reason [chars]
Explanation	Failed to add non-key fields for defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PERF_MON_REACT


%PERF_MON_REACT-0-EMERGSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable.
Recommended Action	No action is required.


%PERF_MON_REACT-0-EMERGCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is EMERGENT.
Recommended Action	No action is required.


%PERF_MON_REACT-1-ALERTSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is ALERT.
Recommended Action	No action is required.


%PERF_MON_REACT-1-ALERTCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is ALERT.
Recommended Action	No action is required.


%PERF_MON_REACT-2-CRITSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is CRITICAL.
Recommended Action	No action is required.


%PERF_MON_REACT-2-CRITCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is CRITICAL.
Recommended Action	No action is required.


%PERF_MON_REACT-3-ERRSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is ERROR
Recommended Action	No action is required.


%PERF_MON_REACT-3-ERRCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is ERROR
Recommended Action	No action is required.


%PERF_MON_REACT-2-INFOSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is INFO.
Recommended Action	No action is required.


%PERF_MON_REACT-2-INFOCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is INFO.
Recommended Action	No action is required.

PERF_TRAFFIC_INFRA


%PERF_TRAFFIC_INFRA-3-MMONOBJINV : A mmon_obj does not exist for policy [chars] class [chars]
Explanation	Unable to find an existing mmon obj for event CLASS_REMOVE and CLASS_MODIFY
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-MMONOBJDUP : A mmon_obj already exists for policy [chars] class [chars]
Explanation	A mmon obj already exists in the MMON DB under the same policy and class for CLASS_ADD
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-NOPARENTMMONOBJ : Internal error, target has no parent mmon object
Explanation	None valid pointer to mmon obj found in tgt obj for CLASS_REMOVE
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-INV_REACT : react is not valid - [chars]
Explanation	This is an internal error, the saved react info is corrupted
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-FIELDENA : Enable fnf field [chars] failed - [chars]
Explanation	Failed to enable a field for use with a config
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-FNFPARSERENA : Enable flow monitor parser failed - [chars]
Explanation	Failed to enable performance monitor typed monitor
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-CHUNKCREATE : Failed to chunk create memory for [chars]
Explanation	Unable to chunk create memory chunk
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-CHUNKDESTROY : Failed to chunk destroy memory for [chars]
Explanation	Unable to chunk destroy memory chunk
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation	Unable to malloc memory chunk, malloc 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.


%PERF_TRAFFIC_INFRA-3-INV_TARGET : A target object does not exist - [chars]
Explanation	An internal error occurred. Try to access a null target obj
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-NULLHIST : A history bucket does not exist
Explanation	An internal error occurred. Try to access a null history
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-NULLFLOW : A flow does not exist
Explanation	An internal error occurred. Try to access a null flow
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-INVCMD : Invalid cmd type [dec] to [chars]
Explanation	This is an internal error, the command type 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.


%PERF_TRAFFIC_INFRA-3-INVMODE : Invalid performance-monitor configuration mode
Explanation	This is an internal error, the configuration sub mode 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.


%PERF_TRAFFIC_INFRA-3-INVCRIT : Invalid react criteria [dec] to [chars]
Explanation	This is an internal error, the saved react criteria is corrupted
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-RESETMODE : Failed to reset csb vars
Explanation	Reset of the csb vars failed due to lack 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-DEFRECCREATE : Creation of default-record [chars] failed - reason [chars]
Explanation	Failed to create system defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-RECSETPROP : Setting property for [chars] default-record failed - reason [chars]
Explanation	Failed to set properties for system defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-RECSETKEY : Adding key fields for default-record [chars] failed - reason [chars]
Explanation	Failed to add key fields for defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-RECSETNONKEY : Adding non-key fieds for [chars] default-record failed - reason [chars]
Explanation	Failed to add non-key fields for defined default flow-records
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-MONITOR_CREATE : Failed to create Monitor at Metering layer. Error - [chars]
Explanation	Failed to create monitor at Metering layer for this policy. The error code provides the reason for failure. No statistics will be collected.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-MONITOR_DELETE : Failed to delete Monitor at Metering layer. Error - [chars]
Explanation	Failed to delete monitor at Metering layer for this policy. The error code provides the reason for 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.


%PERF_TRAFFIC_INFRA-3-MONITOR_SYNC : Out of sync - [chars]
Explanation	This is an internal error, the reference count in flow monitor reached negative
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-INVFIELDTYPE : Enable fnf field [dec] failed - invalid field type
Explanation	Failed to enable a field for use with a config
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-INVMONITOR : The flow monitor pointer is invalid
Explanation	An internal error occurred. The performance-monitor monitor pointer saved in the common monitor 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-INV_COMMON_MONITOR : The common monitor ptr is invalid
Explanation	An internal error occurred. The common monitor ptr saved in the performance-monitor monitor 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-INV_MONITOR_TYPE : The monitor type [dec] is invalid
Explanation	An internal error occurred. The monitor type is out of the 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-INV_POLICY_MAP : The retrieved policy map is invalide - [chars]
Explanation	An internal error occurred. The policy map saved in csb 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.


%PERF_TRAFFIC_INFRA-3-INV_ARG : The argument is not valid - [chars]
Explanation	An internal error occurred. The argument for an internal API 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-CONV_FAILURE : Conversion failed - [chars]
Explanation	Conversion from one format to another 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.


%PERF_TRAFFIC_INFRA-3-CHUNK_INIT : Chunk is not initialized - [chars]
Explanation	Chunk memory is not created or failed to 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.


%PERF_TRAFFIC_INFRA-3-PROC_MSG : Failed to process received record - [chars]
Explanation	Failure during the process of handling the received fnf record
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-MEMLEAK : Memory leak detected - [chars]
Explanation	A memory leak is detected during media-mon memory handling
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-FDEF_NOTIFY : Failed to register PD flow definition [chars]
Explanation	The flow def received from ME or PD 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/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-EXP_ATTR : Failed to set flow attribute for exporter - [chars]
Explanation	An error occured when setting flow attribute use to transform match and collect metrics to export 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.


%PERF_TRAFFIC_INFRA-3-FDEF_TEMP : Invalid flow definition template - [chars]
Explanation	The template was not initialized during system initialization
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-FLOW_EXCEED : The number of flows has exceeded 95%% of the configured maximum flow. [chars]
Explanation	This is warning message if the flow size exceeds the maximum value
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-FLOW_NONEXCEED : The number of flows is below 85%% of the configured maximum flow. [chars]
Explanation	This is info message if the flow size falls below the maximum value
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-SIB_LINK : sib member [int] with [int], error [chars]
Explanation	Failed to link two sibling members in the MMON PD
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PERF_TRAFFIC_INFRA-3-SIB_UNLINK : sib member [int] from [int], error [chars]
Explanation	Failed to unlink two sibling members in the MMON PD
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PERF_TRAFFIC_REACT


%PERF_TRAFFIC_REACT-0-EMERGSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable.
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-0-EMERGCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is EMERGENT.
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-1-ALERTSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is ALERT.
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-1-ALERTCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is ALERT.
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-2-CRITSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is CRITICAL.
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-2-CRITCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is CRITICAL.
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-3-ERRSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is ERROR
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-3-ERRCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is ERROR
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-2-INFOSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is raised. The alarm severity is INFO.
Recommended Action	No action is required.


%PERF_TRAFFIC_REACT-2-INFOCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation	A threshold crossing alarm is cleared. The alarm severity is INFO.
Recommended Action	No action is required.

PKI


%PKI-3-KEY_CMP_MISMATCH : Key in the certificate and stored key does not match for Trustpoint-[chars].
Explanation	Public key in the certificate is not the same as the stored key.
Recommended Action	Make sure that the certificate public key and stored public key are the same.


%PKI-3-QUERY_KEY : Querying key pair failed.
Explanation	Querying public key/private key using subject name failed
Recommended Action	Resubmit enrollment request. Check the subject name.


%PKI-3-CERTRETFAIL : Certificate enrollment failed.
Explanation	Certificate enrollment transaction failed due to internal error.
Recommended Action	Contact CE.


%PKI-6-CERT_INSTALL : [chars] Trustpoint : [chars] Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] End-date : [chars]
Explanation	A previous certificate enrollment request was received by the Certificate Authority. It has issued the certificate, and sent back a copy
Recommended Action	Informational message only. No action required.


%PKI-6-CERTPENDING : Enter manual authentication ...
Explanation	CA server want to manually authenticate the router.
Recommended Action	Follow a manual authentication procedure.


%PKI-6-CERTREJECT : [chars]
Explanation	A previous certificate enrollment request was received by the Certificate Authority. It has rejected the enrollment request.
Recommended Action	Contact the Certificate Authority administrator.


%PKI-6-PKCS12_EXPORT_SUCCESS : PKCS #12 Export from trustpoint [chars] was successfully Exported.
Explanation	A PKCS #12 has been generated and successfully exported.
Recommended Action	No action required. Informational message


%PKI-6-PKCS12_IMPORT_SUCCESS : PKCS #12 import in to trustpoint [chars] successfully imported.
Explanation	A PKCS #12 has been successfully imported.
Recommended Action	No action required. Informational message


%PKI-3-POLLCACERT : Polling CA certificate .....
Explanation	Polling ca certificate.
Recommended Action	Check if CA or ldap server is online.


%PKI-3-QUERYCACERT : Failed to query CA certificate.
Explanation	Failed to query ca certificate from ca server.
Recommended Action	Use parser command cr ca auth and try again.


%PKI-3-INVALIDCACERT : Failed to process CA certificate.
Explanation	Failed to process the ca certificate received from ca server.
Recommended Action	Use parser command cr ca auth and try again.


%PKI-3-POLLRACERT : Polling RA certificate .....
Explanation	Polling ra certificate.
Recommended Action	Check if CA or ldap server is online.


%PKI-3-POLLROUTERCERT : Polling Router certificate for [chars] .....
Explanation	Polling router certificate.
Recommended Action	Check if CA or ldap server is online.


%PKI-4-NOAUTOSAVE : Configuration was modified. Issue write memory to save new certificate
Explanation	Auto-Enroll has obtained a new router key pair and certificate. However, the running configuration was previously modified.
Recommended Action	Issue the write memory command to save the new certificate(s) and key(s).


%PKI-6-AUTOSAVE : Running configuration saved to NVRAM
Explanation	Auto-Enroll has obtained a new router key pair and certificate, and has done an automatic write memory to save them.
Recommended Action	No action required. Informational message


%PKI-4-NOSHADOWAUTOSAVE : Configuration was modified. Issue write memory to save new IOS CA certificate
Explanation	IOS CA Rollover has generated a shadow CA key pair and certificate. However, the running configuration was previously modified.
Recommended Action	Issue the write memory command to save the new certificate(s) and key(s).


%PKI-6-CERTRENEWMANUAL : Please renew the router certificate for trustpoint [chars]
Explanation	Trustpoint certificate will expire soon, and should be renewed
Recommended Action	Obtain a new certificate from the Certificate Authority


%PKI-6-CERT_RENEW_AUTO : Auto renewing router certificate of trustpoint [chars]
Explanation	Trustpoint certificate will expire soon, and is being automatically renewed
Recommended Action	No action required. Informational message


%PKI-6-SHADOWAUTOSAVE : Running configuration saved to NVRAM
Explanation	IOS CA Rollover has generated a shadow CA key pair and certificate, and has done an automatic write memory to save them.
Recommended Action	No action required. Informational message


%PKI-4-NOCONFIGAUTOSAVE : Configuration was modified. Issue write memory to save new IOS PKI configuration
Explanation	IOS PKI APIs have generated new PKI configuration. However, the running configuration was previously modified.
Recommended Action	Issue the write memory command to save the new PKI configuration.


%PKI-6-CONFIGAUTOSAVE : Running configuration saved to NVRAM
Explanation	IOS PKI APIs have generated new PKI configuration, and has done an automatic write memory to save them.
Recommended Action	No action required. Informational message


%PKI-6-CERTIFSSEND : Could not send Certificate enrollment request to file system.
Explanation	The certificate enrollment request could not be sent to file system.
Recommended Action	Verify the enrollment URL and that the router is able to write to the file system.


%PKI-6-CERTIFSRECV : Could not receive router's Certificate from file system.
Explanation	The router's certificate could not be received from file system.
Recommended Action	Verify the enrollment URL and that the router is able to read from the file system.


%PKI-2-CERT_ENROLL_FAIL : Certificate enrollment failed for trustpoint [chars]. Reason : [chars]
Explanation	Certificate enroll encounter fatal error
Recommended Action	Contact the CA administrator.


%PKI-2-CERT_RENEW_FAIL : Certificate renewal failed for trustpoint [chars] Reason : [chars]
Explanation	Certificate enroll encounter fatal error
Recommended Action	Contact the CA administrator.


%PKI-4-CERT_ENROLL_CANCEL : Enrollment cancelled for trustpoint : [chars]
Explanation	Certificate enroll cancelled by user
Recommended Action	Contact the CA administrator.


%PKI-3-SOCKETSEND : Failed to send out message to CA server.
Explanation	The failure is caused by http transaction.
Recommended Action	Check http connection to the CA server


%PKI-3-INVALID_INPUT : The input to the parser command is not correct
Explanation	The input to the parser command is not correct
Recommended Action	Repeat the command.


%PKI-3-GETCARACERT : Failed to receive RA/CA certificates.
Explanation	Encountered failure when parsing and processing CA/RA certificates
Recommended Action	Check the status, contact the CA administrator


%PKI-6-CS_DELETE_TP_KEY : Trustpoint and key deleted.
Explanation	Trustpoint and key used by the Certificate Server are deleted.
Recommended Action	No action required. Informational message.


%PKI-6-CS_DELETE : Certificate Server is deleted.
Explanation	Certificate Server is deleted.
Recommended Action	No action required. Informational message.


%PKI-6-CS_GRANT_AUTO_RA : Enrollment requests coming from known RAs will be automatically granted.
Explanation	Enrollment requests coming from known RAs will be automatically granted.
Recommended Action	No action required. Informational message.


%PKI-6-CS_GRANT_AUTO : All enrollment requests will be automatically granted.
Explanation	All enrollment requests will be automatically granted.
Recommended Action	No action required. Informational message.


%PKI-6-CS_GRANT_AUTO_CACERT : All rollover subordinate CA cert requests will be automatically granted.
Explanation	All rollover subordinate CA cert requests will be automatically granted.
Recommended Action	No action required. Informational message.


%PKI-4-CS_GRANT_AUTO_CACERT_FAILURE : A rollover request for a subordinate CA certificate cannot be auto granted.
Explanation	A rollover request for a subordinate CA certificate cannot be authorized and the configured auto grant policy will be ignored. This request will be added to the CS server request queue but will need to be manually granted
Recommended Action	Insure that the peer's current sub CA cert is valid.


%PKI-6-CS_GRANT_AUTO_RACERT : All rollover RA cert requests will be automatically granted.
Explanation	All rollover RA cert requests will be automatically granted.
Recommended Action	No action required. Informational message.


%PKI-6-CS_REJECT_AUTO : All enrollment requests will be automatically rejected.
Explanation	All enrollment requests will be automatically rejected.
Recommended Action	No action required. Informational message.


%PKI-3-CS_CRIT_STORAGE : Critical certificate server storage, [chars], is inaccessible, server disabled.
Explanation	Critical certificate server storage is inaccessible, server disabled.
Recommended Action	Make storage accessible, or re-configure the storage location


%PKI-4-CS_PUBLISH_STORAGE : Publish certificate server storage, [chars], is inaccessible.
Explanation	Publish certificate server storage is inaccessible.
Recommended Action	Make storage accessible, or re-configure the storage location


%PKI-6-AUTOENROLL_KEY_LOCKED : Auto-enroll failed - RSA keypair is locked
Explanation	Auto-enroll attempted to generate a new RSA keypair. However the existing RSA keypair is locked so auto-enroll cannot proceed
Recommended Action	Auto-enroll will retry the enrollment request Make sure the existing RSA keypair is unlocked before the next retry


%PKI-6-CS_ENABLED : Certificate server now enabled.
Explanation	Certificate server now enabled.
Recommended Action	No action required. Informational message.


%PKI-6-CS_DISABLED : Certificate server now disabled. Reason : [chars]
Explanation	Certificate server now disabled.
Recommended Action	No action required. Informational message.


%PKI-3-UNUSABLE_KEY_USAGE : Key-usage type '[chars]' for cert with serial number [chars] is not usable.
Explanation	The given key-usage type is not usable by IOS. If seen during an import operation, this will likely cause the import to fail. Acceptable key-usage types should include Key-encipherment and/or digital-signature. Other key-usage types may be present, but will be ignored.
Recommended Action	Recreate the certificate with Key-encipherment, digital-signature, or both.


%PKI-6-AUTOCERTFAIL : Certificate (re)enrollment failed. Delaying before retry
Explanation	Automatic certificate enrollment or re-enrollment failed The router will retry in 6 hours or less depending on the expiration time of the router's certificate.
Recommended Action	Contact the CA administrator.


%PKI-4-AUTOCERTFAILWARN : Certificate (re)enrollment failed. Delaying before retry
Explanation	Automatic certificate re-enrollment failed. The router will retry in 6 hours or less depending on the expiration time of the router's certificate. Caution - Router's Certificate may expire soon.
Recommended Action	Contact the CA administrator. The router will retry.


%PKI-3-AUTOCERTERR : Auto Certificate (re)enrollment failed. Cannot retry
Explanation	Automatic certificate re-enrollment failed. The router clock my not be set correctly. If the router has a certificate it may be expired.
Recommended Action	Check router clock is set correctly Make sure the router's cert has not expired


%PKI-3-CERTPENDERR : Failed to receive pending certificate during enrollment
Explanation	The router's cert remains in a pending state after the maximum number of retries to enroll.
Recommended Action	Contact the CA administrator. Then retry the enrollment.


%PKI-4-CERTIFICATE_INVALID_SUBJECT : Certificate has a missing or invalid subject name.
Explanation	The certificate subject name attribute must be present and not empty OR The certificate subject alt name extension must be present and include at least one entry.
Recommended Action	Examine the offending certificate and re-issue it with a proper subject name.


%PKI-3-CERTIFICATE_INVALID_EXPIRED : Certificate chain validation has failed. The certificate (SN: [chars]) has expired. Validity period ended on [chars]
Explanation	The certificate validity period indicates that this certificate has expired
Recommended Action	Check the system clock to see if its set correctly


%PKI-3-CERTIFICATE_INVALID_NOT_YET_VALID : Certificate chain validation has failed. The certificate (SN: [chars]) is not yet valid Validity period starts on [chars]
Explanation	The certificate validity period indicates that this certificate is not yet valid
Recommended Action	Check the system clock to see if its set correctly


%PKI-3-CERTIFICATE_INVALID : Certificate chain validation has failed.
Explanation	The certificate is not valid
Recommended Action	Check the system clock to see if its set correctly


%PKI-3-CERTIFICATE_REVOKED : Certificate chain validation has failed. The certificate (SN: [chars]) is revoked
Explanation	The certificate has been revoked by the CA administrator.
Recommended Action	Check the status, contact the CA administrator


%PKI-3-CERTIFICATE_INVALID_UNAUTHORIZED : Certificate chain validation has failed. Unauthorized
Explanation	The certificate is valid but not authorized
Recommended Action	Check the system clock to see if its set correctly


%PKI-4-CRLHTTPFETCHFAIL : CRL Request for trustpoint [chars] returned [dec] [chars]
Explanation	The CRL fetch returned something other than success. If the trustpoint revocation-check includes the keyword 'none', the transaction will succeed. If revocation- checking is not optional, the transaction will fail.
Recommended Action	Verify that the CRL is at the location specified in the Certificate, and that the server is operational. To see interaction between IOS and the CRL-server, please turn on `debug crypto pki transactions`


%PKI-6-CRLHTTPFETCHREDIR : CRL Request for trustpoint [chars] returned [dec] [chars] -> [chars]
Explanation	The CRL fetch returned a redirect directive. This need not be an error, if the file exists at the redirected location.
Recommended Action	If no other errors are seen, then the CRL was fetched from the new location, and no action is necessary. To see interaction between IOS and the CRL-server, please turn on `debug crypto pki transactions`


%PKI-3-CRL_FETCH_FAIL : CRL fetch for trustpoint [chars] failed Reason : [chars]
Explanation	The CRL fetch returned something other than success.
Recommended Action	Check the CRL manually to see it is correct. To see interaction between IOS and the CRL-server, please turn on `debug crypto pki transactions`


%PKI-3-CRL_INSERT_FAIL : CRL download for trustpoint [chars] has been discarded. Reason : [chars] Status : [dec] Status String : [chars]
Explanation	Inserting and/or verifying the CRL failed. If the trustpoint revocation-check includes the keyword 'none', the transaction will succeed. If revocation- checking is not optional, the transaction will fail.
Recommended Action	Check the CRL manually to see it is correct. To see interaction between IOS and the CRL-server, please turn on `debug crypto pki transactions`


%PKI-4-HTTPREDIRECT : Maximum Redirection limit of [dec] exceeded, trying to retrieve URL [chars]
Explanation	While fetching a document via http, there were too many redirections, and the operation has aborted. If the trustpoint revocation-check includes the keyword 'none', the transaction will succeed. If revocation- checking is not optional, the transaction will fail.
Recommended Action	Verify that the CRL is at the location specified in the Certificate, and that the server is operational. To see interaction between IOS and the CRL-server, please turn on `debug crypto pki transactions`


%PKI-4-CRL_LDAP_QUERY : An attempt to retrieve the CRL from [chars] using LDAP has failed
Explanation	An LDAP query was made to acquire the certificate revocation list, but the LDAP server did not respond with the requested information. This is a warning that only applies to the Distribution Point listed. It does not necessarily reflect the overall success or failure of CRL aquistion since a prior or subsequent retrival of the CRL may have succedeed.
Recommended Action	Check that the LDAP server is reachable and online. Verify that the CRL is at the requested location


%PKI-6-TRUSTPOOL_AUTO_UPDATE : Auto-trustpool update in progress from [chars].
Explanation	One of the certificates in the trustpool will expire soon. An attmpt to download a new trustpool bundle is in progress
Recommended Action	Since an url has been configured that identifies the location to aquire the trustpool bundle, then no action is required.


%PKI-4-TRUSTPOOL_AUTO_UPDATE_DISABLED : Auto-trustpool update is disabled.
Explanation	One of the certificates in the trustpool will expire soon. An attmpt to download a new trustpool bundle cannot be attempted since a bundle location is not configured
Recommended Action	Either configure the bundle location in the trustpool policy or manually update the trustpool bundle.


%PKI-4-TRUSTPOOL_EXPIRATION_WARNING : The Trustpool will expire in [chars].
Explanation	One of the certificates in the trustpool will expire soon. If a bundle location is configured an auto aupdate will be attempted at predetermined intervals.
Recommended Action	If a bundle location is configured in the trustpool policy no further action is required. Otherwise manual update of trustpool bundle may be needed.


%PKI-6-ECDSA_CERT_WITH_SHA1 : User has accepted the security implication of using lesser hash strength(SHA1) for the Elliptic Curve Key present in the certificate
Explanation	The SHA1 hash algorithm is not recommended for use with the elliptic curve key in this certificate. It is recommended that SHA2 or stronger hash algorithm be used.
Recommended Action	Informational message only. No action required.


%PKI-6-PKI_CRL_DOWNLOADED : CRL download successful. Trustpoint : [chars] CDP-URL : [chars] Issuer : [chars]
Explanation	CRL is downloaded and successfully inserted in the database. Notification for the same is sent to applications registered.
Recommended Action	Informational message only. No action required.


%PKI-4-CERT_EXPIRY_WARNING : [chars] Certificate belonging to trustpoint [chars] will expire in [int] Days [int] hours [int] mins [int] secs at [chars]. Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] Auto-Renewal : [chars]
Explanation	Warning to indicate that certificate is expiring soon.
Recommended Action	If auto-enrol feature is not configured, re-enrol the certificate manually. Else, check if any issues with auto-enrol.


%PKI-1-CERT_EXPIRY_ALERT : [chars] Certificate belonging to trustpoint [chars] will expire in [int] Days [int] hours [int] mins [int] secs at [chars]. Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] Auto-Renewal : [chars]
Explanation	Alert to indicate that certificate will expire in less than one week.
Recommended Action	If auto-enrol feature is not configured, re-enrol the certificate manually. Else, check if any issues with auto-enrol.


%PKI-4-OCSP_SERVER_NO_RESP : The OCSP Server URL [chars] is not reachable or not responding
Explanation	The OCSP server is not reachable or is not responding to the OCSP request
Recommended Action	Check if the OCSP server is reachable and is receiving the OCSP request


%PKI-4-OCSP_SERVER_RESP_COMP : The OCSP Server [chars]: error:responder certificate is peer certificate
Explanation	The OCSP responder certificate is peer certificate
Recommended Action	Check if the configured OCSP server and responder OCSP server is same or not


%PKI-3-OCSP_RESPONSE_STATUS : OCSP response status failed Reason : [chars]
Explanation	OCSP response status failed
Recommended Action	Check the ocsp request or ocsp server configurations


%PKI-4-OCSP_SERVER_RESP_SIGN : The OCSP Server [chars]: error:responder invalid signature algorithm
Explanation	The OCSP responder has differnt signature algorithm
Recommended Action	Check if the configured and responder OCSP server same signature algorithm or not


%PKI-4-OCSP_SERVER_RESP_DECODE_FAIL : The OCSP Server [chars]: failed to decode OCSP response basic data
Explanation	The OCSP response data decoding is failing
Recommended Action	Check if the configured OCSP server response data


%PKI-4-OCSP_SERVER_CERT_VALIDATE : The OCSP Server [chars]: responder certificate validation failed
Explanation	The OCSP server responder certificate validation failed
Recommended Action	Check if the configured OCSP server responder certificate


%PKI-4-OCSP_SERVER_RESP_VARIFY : The OCSP Server [chars]: failed to verify OCSP response
Explanation	The OCSP response verification failed
Recommended Action	Check if the configured OCSP server response


%PKI-4-OCSP_SERVER_RESP_DECODE : The OCSP Server [chars]: failed to decode OCSP response data
Explanation	The OCSP response data decoding is failing
Recommended Action	Check if the configured OCSP server response data


%PKI-5-CERT_ENROLL_RETRY : Certificate (re)enrollment has failed and retry will happen for [dec] attempts
Explanation	Automatic certificate re-enrollment failed. We are printing a consolidated message for the maximum number of retry attempts. The router will continue to retry depending on the expiration time of the router's certificate. The retry attempts will be either 999 (default) or as specified Caution - Router's Certificate may expire soon.
Recommended Action	Contact the CA administrator. The router will retry.


%PKI-4-CERT_ENROLL_RETRY_FAIL : Certificate (re)enrollment has failed after [dec] attempts
Explanation	Automatic certificate re-enrollment failed. Caution - Router's Certificate may expire soon.
Recommended Action	Contact the CA administrator. Enrollment failed.


%PKI-4-ROUTER_CERT_EXPIRED : Router certificate expired, cannot re-enroll/retry for enrollment/re-enroll
Explanation	Cannot re-enroll/retry for enroll/re-enroll. Caution - Router's Certificate has expired.
Recommended Action	Enroll the router manually.


%PKI-4-TRUSTPOOL_DOWNLOAD_FAIL : Trustpool download requires [int] bytes, available free storage [int] bytes is insufficient
Explanation	Trustpool download failed Free space in nvram is not sufficient to store Trustpool Certificates. Change the Trustpool policy for its storage
Recommended Action	Change the storage policy for Trustpool


%PKI-6-TRUSTPOOL_DOWNLOAD_SUCCESS : Trustpool Download is successful
Explanation	Trustpool Download is successful
Recommended Action	No action required. Informational message


%PKI-4-TRUSTPOOL_DOWNLOAD_FAILURE : Trustpool Download failed
Explanation	Failed to download the trustpool bundle
Recommended Action	Enable debugs and obtain the reason for failure


%PKI-4-TRUSTPOOL_CERTIFICATE_SAVE_CHANGE : Downloaded Trustpool certificates present prior to image upgrade should be re-downloaded. Issue 'crypto pki trustpool import url <url>' to re-download the certificates.
Explanation	Downloaded Trustpool certificates present prior to image upgrade should be re-downlaoded
Recommended Action	Before image upgrade, clean all the downloaded trustpool certificates. Import them again after image upgrade.


%PKI-2-NON_AUTHORITATIVE_CLOCK : PKI functions can not be initialized until an authoritative time source, like NTP, can be obtained.
Explanation	System clock is not valid. Update the system clock to start with PKI timers
Recommended Action	System clock must be configured/Updated.


%PKI-6-AUTHORITATIVE_CLOCK : The system clock has been set.
Explanation	System clock is valid.
Recommended Action	No action. Informational message.


%PKI-6-CSR_FINGERPRINT : CSR Fingerprint MD5 : [chars] CSR Fingerprint SHA1: [chars]
Explanation	Fingerprint display
Recommended Action	Information message


%PKI-6-CERT_ENROLL_AUTO : Auto initial enrollment for trustpoint [chars]
Explanation	Trustpoint enrollment happening automatically.
Recommended Action	No action required. Informational message


%PKI-6-CERT_ENROLL_MANUAL : Manual enrollment for trustpoint [chars]
Explanation	Trustpoint enrollment triggerred manaully
Recommended Action	No action required. Informational message


%PKI-6-CERT_REENROLL : Re-enrollment for trustpoint [chars]
Explanation	Trustpoint re-enrollment triggerred manaully
Recommended Action	No action required. Informational message


%PKI-3-HOSTNAME_RESOLVE_ERR : Failed to resolve HOSTNAME/IPADDRESS : [chars]
Explanation	Unable to resolve hostname/ip-address
Recommended Action	Check network connectivity


%PKI-3-OCSP_CONTENT_MISMATCH : ocsp content mismatch
Explanation	Expected content not matched with formed content
Recommended Action	Check ocsp request


%PKI-2-MEM_ALLOC_FAIL : Memory allocation failure. Number of bytes requested : [dec]
Explanation	Memory allocation failed
Recommended Action	Check memory left on the device


%PKI-3-SOCKET_OPEN : Failed to open socket.
Explanation	The failure is caused by socket open
Recommended Action	Check tcp/socket debugging message


%PKI-3-SET_SOURCE_INTERFACE_FAIL : Failed to set source interface for [chars] ip address
Explanation	Failed to set source interface
Recommended Action	Check configured source interface for trustpoint


%PKI-3-SOCKET_BIND_FAIL_SOURCE_INTERFACE : Failed to bind the socket due to source interface ip : [chars]
Explanation	Failed to bind socket with source interface
Recommended Action	Check configured source interface for trustpoint


%PKI-3-SET_VRF_FAIL : Failed to set VRF : [chars]. VRF not configured
Explanation	Failed to set VRF
Recommended Action	Check configured VRF for trustpoint and set VRF


%PKI-3-SET_SOCK_VRF_INTERFACE_FAIL : Failed to set VRF : [chars] to socket interface
Explanation	Failed to set VRF to socket
Recommended Action	Check configured VRF for trustpoint and set VRF


%PKI-3-SET_SOCKET_OPTION_FAIL : Failed to set socket option. Option : [chars]
Explanation	Failed to set socket option
Recommended Action	Enable socket debugs


%PKI-3-SOCKET_CONNECT_FAIL : Failed to connect to socket
Explanation	Failed to connect socket
Recommended Action	Enable socket debugs


%PKI-2-CA_SERVER_CERT_EXPIRED : [chars] server ceritifcate expired. Cannot enable [chars] server
Explanation	CA server certificate expired.
Recommended Action	Reconfigure CA server


%PKI-2-CA_SERVER_LABEL_TOO_LONG : [chars] server name too long. Reconfigure server with name less than 13 characters.
Explanation	CA server name too long.
Recommended Action	Reconfigure CA server with less than 13 characters


%PKI-2-CA_SERVER_TP_NOT_PRESENT : [chars] server's Trustpoint not available. Check for the trustpoint config.
Explanation	CA server's Trustpoint not available.
Recommended Action	Check for CA server and Trustpoint configuration presence


%PKI-2-SERVER_TP_CREATE_FAIL : Not abel to create [chars] server's Trustpoint.Check for CA server config's.
Explanation	CA server's Trustpoint not created.
Recommended Action	Check for CA server and Trustpoint configuration presence


%PKI-2-SERVER_KEY_NOT_PRESENT : Not able to find CS [chars]'s keypair label [chars]. Check whether keypair [chars] is available on device
Explanation	CA server's key-pair not available.
Recommended Action	Check for key-pair presence


%PKI-2-NON_AUTHORITATIVE_CLOCK_CA : CA server cannot be enabled due to non-authoritative system clock. Configure clock/Sync with NTP server.
Explanation	System clock is not valid. Update the system clock to start CA server
Recommended Action	System clock must be configured/Updated.


%PKI-2-CS_CERT_EXPIRED : Certificate server [chars] CA certificate expired. Regenerate CA certificate manaully.
Explanation	CS certificate expired.
Recommended Action	Regenerate CS certificate.


%PKI-2-CS_CERT_GEN_FAIL : Certificate server [chars] CA certificate generation failed. Regenerate CA certificate manaully.
Explanation	Certificate Server disabled.
Recommended Action	Regenerate CS certificate.


%PKI-2-CS_CERT_INVALID : Certificate server [chars] CA certificate invalid. Regenerate CA certificate manaully.
Explanation	CS certificate invalid.
Recommended Action	Regenerate CS certificate.


%PKI-2-CS_SUBJECT_NAME_FAIL : Extracting subject name from Server certificate failed
Explanation	Extraction of subject failed
Recommended Action	Regenerate CS certificate.


%PKI-2-CS_ISSUER_NAME_INVALID : Invalid issuer_name in CS [chars] configuration
Explanation	Invalid issuer-name in Certificate Server
Recommended Action	Check certificate server configuration and re-configure.


%PKI-2-CS_CERT_NOT_PRESENT : Certificate server [chars]'s certificate not present.
Explanation	Certificate server certificate not present
Recommended Action	Regenerate CS certificate.


%PKI-3-ISSUER_NAME_NOT_BER : Issuer name is not BER
Explanation	Issuer name is not BER. Check issuer-name
Recommended Action	Check issuer-name present/configured


%PKI-3-SUBJECT_NAME_NOT_BER : Subject name is not BER
Explanation	Subject name is not BER. Check subject-name
Recommended Action	Check subject-name present/configured


%PKI-3-CRL_HTTP_FAIL : CRL Request over http for trustpoint [chars] failed. Reason : [chars]
Explanation	Receival of CA certificate failed
Recommended Action	CA cert download failed


%PKI-6-CERT_ROLLOVER_ACTIVE : A rollover ID certificate has been activated under trustpoint [chars] replacing the previous ID certificate. Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] End-date : [chars]
Explanation	Rollover ID certificate active
Recommended Action	No action needed. Informational mesage only


%PKI-2-CERT_SHADOW_INSTALL_FAIL : [chars].
Explanation	Shadow CA/ID certificate installation failed.
Recommended Action	Check for the reason for failure and perform necessary steps


%PKI-6-CERT_SHADOW_INSTALL : [chars] Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] End-date : [chars]
Explanation	Shadow CA/ID certificate has been installed.
Recommended Action	No action needed. Informational mesage only


%PKI-6-CERT_SHADOW_ACTIVE : [chars] Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] End-date : [chars]
Explanation	Shadow CA/ID certificate has been activated.
Recommended Action	No action needed. Informational mesage only


%PKI-3-CERT_ROLLOVER : Renew/Shadow event has failed for trustpoint : [chars] Reason : [chars]
Explanation	Renew/Shadow event failed.
Recommended Action	Perform manual renewal of certificate to avoid certificate expiry.


%PKI-3-CS_ROLLOVER_TRIGGER : CS Rollover event has been triggered for server [chars]
Explanation	Rollover triggerred for certificate server
Recommended Action	Informational message only. No action needed.


%PKI-2-CS_ROLLOVER_FAIL : CS Rollover failed. Reason : [chars]
Explanation	Rollover failed for certificate server
Recommended Action	Critical error on rollover. Certificate Server has to be re-enabled.


%PKI-6-CS_ROLLOVER_AVAILABLE : [Sub/RA]CS Rollover certificate has been generated for [chars], and it will be activated at [chars] Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] End-date : [chars]
Explanation	Rollover certificate generated
Recommended Action	Informational message only. No action needed.


%PKI-6-CS_ROLLOVER_ACTIVE : [chars] Rollover certificate has been activated for [chars], replacing the previous [Sub/RA]CA certificate Issuer-name : [chars] Subject-name : [chars] Serial-number: [chars] End-date : [chars]
Explanation	Rollover certificate activated
Recommended Action	Informational message only. No action needed.


%PKI-3-OCSP_FETCH_FAIL : OCSP fetch failed. Reason : [chars]
Explanation	OCSP Fetch failed
Recommended Action	Enable socket/tcp debugs to check connectivity with ocsp server


%PKI-3-OCSP_RESPONSE_FAIL : OCSP response from [chars] has been discarded. Reason : [chars]
Explanation	OCSP response parse failed
Recommended Action	Check OCSP response


%PKI-6-OCSP_SUCCESS : OCSP response from [chars] has been successfully processed for certificate : [chars] Serial-number: [chars] Result : [chars]
Explanation	OCSP response successfully processed.
Recommended Action	Informational message only. No action needed.


%PKI-2-PKI_EVENT_LOG : PKI Event : [chars]
Explanation	PKI Event for both success/failure.
Recommended Action	Informational message only. No action needed.


%PKI-3-ENROLL_PKCS12 : Trustpoint [chars] configured as pkcs12 enrollment. SCEP enrollment not supported
Explanation	Change the trustpoint configuration to point to enrollment-url
Recommended Action	TP configuraiton need to be verified.


%PKI-3-GET_CERT_INITIAL : Failed with GetCertInitial for trustpoint [chars] Reason : [chars]
Explanation	GetCertInitial encounter fatal error
Recommended Action	Contact the CA administrator.


%PKI-6-SLA_TRUSTPOINT_CHANGE : Attempting to override SLA Trustpoint. The current running SLA trustpoint config will be retained Config-Replace errors corresponding to SLA TrustPoint may be ingored.
Explanation	PKI Event for both success/failure.
Recommended Action	Informational message only. No action needed.

PKTLOG


%PKTLOG-3-PROXY_IPC_SEND_FAILED : [chars] [chars]
Explanation	Transmission of an IPC message by the packet logger proxy failed.
Recommended Action	LOG_STD_ACTION


%PKTLOG-3-PROXY_IPC_ALLOC_FAILED : [chars]
Explanation	Allocation of an IPC packet buffer by the packet logger proxy failed.
Recommended Action	LOG_STD_ACTION


%PKTLOG-3-PROXY_BAD_SUBTYPE : [dec]
Explanation	Invalid subtype was passed to packet logger proxy IPC handler.
Recommended Action	LOG_STD_ACTION


%PKTLOG-2-PROXY_IPC_SET_FAILED : [chars]
Explanation	Packet logger proxy IPC handler could not be initialized.
Recommended Action	LOG_STD_ACTION


%PKTLOG-4-PROXY_DUP_INIT : [chars]
Explanation	Duplicate initialization IPC message received for user %d client id %d.
Recommended Action	LOG_STD_ACTION


%PKTLOG-3-PKTLOG_IPC_SEND_FAILED : [chars] [chars]
Explanation	Transmission of an IPC message by the packet logger failed. ACL and stats lost.
Recommended Action	LOG_STD_ACTION


%PKTLOG-4-PKTLOG_IPC_ALLOC_FAILED : [chars]
Explanation	Allocation of an IPC packet buffer by the packet logger failed.
Recommended Action	LOG_STD_ACTION


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


%PKTLOG-4-PROXY_INVALID_USER_IDX : [int] [int]
Explanation	IPC message contained invalid user index for client id.
Recommended Action	LOG_STD_ACTION


%PKTLOG-1-PROXY_MEM_RET_ERR : [chars] [int] [int] [int]
Explanation	IPC failed and could not return memory
Recommended Action	LOG_STD_ACTION


%PKTLOG-1-PROXY_MEM_APPEND_ERR : [int] [int] [int]
Explanation	Could not add memory to memory pool
Recommended Action	LOG_STD_ACTION

PLATFORM through PLATFORM_TAM

PLATFORM
PLATFORM_ACT2
PLATFORM_BRKOUT
PLATFORM_CAPABILITY
PLATFORM_ENVIRONMENT
PLATFORM_INFRA
PLATFORM_MATM
PLATFORM_POWER
PLATFORM_SCC
PLATFORM_TAM

PLATFORM


%PLATFORM-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation	MAC address allocation failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.
Recommended Action	LOG_STD_ACTION


%PLATFORM-3-NOMAC_INTF : Failed to allocate MAC address for interface [chars]
Explanation	MAC address allocation failed for logical interface specified in the 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.


%PLATFORM-3-GEC_NOMAC : Can't allocate MAC address for port-channel interface [int]
Explanation	MAC address allocation failed for the port-channel interface specified in the message. This may happen if the port-channel interface exceeds the maximum number of supported port-channel interfaces.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-NO_BASEMAC : Can't retrieve base MAC address
Explanation	Base MAC address determination failed at system start.
Recommended Action	LOG_STD_ACTION


%PLATFORM-6-HASTATUS : RP switchover, [chars]
Explanation	RP switchover events received by platform code.
Recommended Action	No action is required.


%PLATFORM-6-HASTATUS_DETAIL : RP switchover, [chars] (count [int])
Explanation	RP switchover events received by platform code.
Recommended Action	No action is required.


%PLATFORM-4-HASTATUS_WARN : RP HA status warning, [chars])
Explanation	Standby RP reports peer not present event. This is indicative of a IPC problem between IOSd and CMRP
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-HAKPA_FAIL : RP HA Keepalive failure, [chars])
Explanation	Standby RP reports missing keepalives from Active. This is indicative of an IPC problem between peer IOSd processes
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-HASTATUS_FAIL : RP switchover, [chars] (count [int])
Explanation	RP switchover failed to reach active state. The RP will be reset. This is indicative of a IPC problem between IOSd and CMRP
Recommended Action	Make sure system achieves full redundant state after the RP reset. If not, reload entire system


%PLATFORM-3-RF_PROG_FAIL : Progression completion notification to chassis management failed, [chars]
Explanation	Could not notify the completion of the RF progression to the chassis management process. The system will potentially not be in a fully redundant state.
Recommended Action	LOG_STD_ACTION


%PLATFORM-6-RF_PROG_SUCCESS : RF state [chars]
Explanation	A marker to illuminate when the standby reaches a terminal state.
Recommended Action	No action is required.


%PLATFORM-4-RELOAD_STANDBY : [chars] reload requested by [chars]. Reason [chars]
Explanation	Unexpected configuration or states mismatch between Active and Standby RPs. Reloading Standby to synchronize the configuration or states.
Recommended Action	None. This is expected behavior.


%PLATFORM-3-RF_RELOAD_PEER : Reload peer notification to chassis management failed, [chars]
Explanation	Could not notify Reload Peer to the chassis management process. The Standby peer could not be reloaded by the Active. The system will potentially not be in a fully redundant state.
Recommended Action	Reload peer instance using the available CLI commands. If system does not achieve full Standby status after that, the system must be reloaded


%PLATFORM-6-EVENT_LOG : [chars]
Explanation	An entry from the internal event log at reload on the standby RP. This is informational.
Recommended Action	No action is required.


%PLATFORM-4-BOOTVAR_NOT_SET : Boot variable is not set. Boot variable either does not exist or buffer is too small. Keeping it blank
Explanation	Boot variable either does not exist or buffer is too small. Not able to set boot variable. Ignoring it.
Recommended Action	No action is required.


%PLATFORM-3-NVRAM_OPEN_FAIL : Failed to open nvram - [chars].
Explanation	The nvram device could not be opened.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-NVRAM_READ_FAIL : Failed to read nvram - [chars].
Explanation	The nvram contents could not be read.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-NVRAM_WRITE_FAIL : Failed to write nvram - [chars].
Explanation	Couldn't write into the nvram device.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-BACKUP_NVRAM_OPEN_FAIL : Failed to open backup nvram - [chars].
Explanation	The backup nvram device could not be opened.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-BACKUP_NVRAM_READ_FAIL : Failed to read backup nvram - [chars].
Explanation	The backup nvram contents could not be read.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-3-BACKUP_NVRAM_WRITE_FAIL : Failed to write backup nvram - [chars].
Explanation	Couldn't write into the backup nvram device.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM-6-SB_INIT_DELAY : RF progression will be suspended due to standby initialization delay configuration setting. Standby initialization will resume after [int] seconds
Explanation	An informational message about the standby initialization delay configuration. RF progression will be delayed for the configured value. Bulk-sync and other progression events will not happen until after the configured delay value
Recommended Action	No action is required.


%PLATFORM-6-SB_INIT_DELAY_END : RF progression delay timer expired. Standby initialization will now continue
Explanation	An informational message about the standby initialization delay configuration. RF progression will now continue since configured delay has expired
Recommended Action	No action is required.


%PLATFORM-4-STATS_COLLECTION : Reducing statistics collection interval for SPA ([chars]) will impact the RP control plane activity
Explanation	MIB statistics for HW counters are sent from CC to RP every 10 seconds by default, changing the timer through CLI to send more often will increase RP CPU utilization and result in sending more IPC messages between CC and RP
Recommended Action	No action is required.


%PLATFORM-1-NOSPACE : [chars] : no space alarm assert
Explanation	bootflash memory exhausted Delete the old file from boot flash to create space
Recommended Action	No action is required.


%PLATFORM-4-LOWSPACE : [chars] : low space alarm assert
Explanation	bootflash memory is very low Delete the old file from boot flash to create space
Recommended Action	No action is required.


%PLATFORM-5-LOWSPACERECOVER : [chars] : low space alarm deassert
Explanation	bootflash memory
Recommended Action	No action is required.


%PLATFORM-4-MEMORYSIZE : Active and Standby memory configuration differ by more than 1 GB. Active = %lldKB, Standby = %lldKB
Explanation	The memory configuration on both the Supervisor is different by more than 1GB. Some of the functionality which is high availability aware and dependent on the memory (like IOX) will be impacted.
Recommended Action	Please upgrade/downgrade memory configuration on both the Supervisor to match the size


%PLATFORM-4-SDM_TEMPLATE : Mismatch in SDM templates configured on Active ([chars]) and Standby ([chars]) supervisors
Explanation	The SDM template configured on the two Supervisors are different. Different SDM template would enable different sets of features on the active and standby supervisors. Table sizes configured for the common features may be different. These features will not function properly on switchover from one supervisor to another.
Recommended Action	Please configure the same SDM template on both Supervisors using 'sdm prefer <template>' configuration command, followed by a reload. Supervisors should be brought to hot-standby state and the SDM template configured such that the template gets applied to both the supervisors. Supervisors can also be brought up as standalone and SDM template configured on them one at a time followed by a reload.


%PLATFORM-3-REDMODE_FAIL : Redundancy mode: [chars] (rc [dec])
Explanation	Redundancy mode change could not be processed. This is indicative of a IPC problem between IOSd and the peer platform process.
Recommended Action	Make sure system achieves full redundant state. If not, reload entire system


%PLATFORM-5-RESETCARD : [chars] reset to acquire provisioned software
Explanation	The linecard specified was not running the currently provisioned software, which it will acquire on restart.
Recommended Action	No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only.

PLATFORM_ACT2


%PLATFORM_ACT2-2-SUDI_VALIDATION_FAILED : Secure UDI validation failed. [chars]
Explanation	Secure UDI validation for the chassis failed. The router failed to authenticate itself
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PLATFORM_BRKOUT


%PLATFORM_BRKOUT-3-BRKOUTCMD_SYNCFAILED : Failed to send Breakout command to hardware.
Explanation	A messages that was sent to the hardware module, was not delivered correctly. The failure most likely occurred because of incorrect switch number or non-existing breakout port number specified, or a software communication 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.

PLATFORM_CAPABILITY


%PLATFORM_CAPABILITY-4-INIT : Fatal Initialization Error - [chars]
Explanation	An internal software error occurred.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM_CAPABILITY-4-CALL : Fatal Initialization Error - [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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.

PLATFORM_ENVIRONMENT


%PLATFORM_ENVIRONMENT-1-NIM_OVER_CURRENT : NIM module in [chars] is in an over current condition [dec] [chars]. System will reset.
Explanation	An over current condition has been detected in the indicated module. Remove the module causing the issue. User has ~30 seconds to remove module before the router will be shut 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.


%PLATFORM_ENVIRONMENT-1-NIM_OVER_CURRENT_GEN : NIM module(s) in an over current condition. System will reset.
Explanation	An over current condition has been detected in the indicated module. Remove the module causing the issue. User has ~30 seconds to remove module before the router will be shut 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.

PLATFORM_INFRA


%PLATFORM_INFRA-5-IOS_INTR_OVER_LIMIT : IOS thread disabled interrupt for [int] msec
Explanation	IOS thread process disabled interrupt 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.


%PLATFORM_INFRA-5-IOS_INTR_LIMIT_NOT_SET : IOS thread interrupt limit not set
Explanation	IOS failed to retrieve interrupt limit
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM_INFRA-5-IOS_INTR_EVENT : IOS thread interrupt event ([dec]).
Explanation	IOS thread process interrupt event
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM_INFRA-5-IOS_INTR_HISTORY : [[dec]\|[dec]] [[dec]:[dec]] [[dec]->[dec]] ra[ l* [hex] l* [hex] ]
Explanation	IOS thread process interrupt history
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PLATFORM_INFRA-5-IOS_INTR_INVALID_LEVEL : IOS thread interrupt level [dec] replaced by [dec]
Explanation	An invalid IOS thread interrupt level was used
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PLATFORM_MATM


%PLATFORM_MATM-3-INVALID_MSG_RECEIVED : MATM received invalid SPI message.
Explanation	A messages that was to be received from the hardware module, was not received correctly. Mac address learning/ageing might be impacted as a result. The failure most likely occurred because of a software communication error.
Recommended Action	LOG_STD_SH_TECH_ACTION


%PLATFORM_MATM-4-QUEUE_OVERLIMIT : MATM dropped [chars] messages as queue limit has reached.
Explanation	Messages received from the hardware module were not processed because an internal queue was full. Mac address learning/aging might be impacted as a result.
Recommended Action	LOG_STD_SH_TECH_ACTION

PLATFORM_POWER


%PLATFORM_POWER-6-MODEMISMATCH : [chars] power not in [chars] mode
Explanation	The mode of indicated power type is not available. This may be due to the fact that only one power supply or module of that type is present or functional in the system
Recommended Action	Please verify the appropriate power supply or module is plugged in the system. 'show power', 'show platform' CLI will provide more information.


%PLATFORM_POWER-6-MODEMATCH : [chars] power is in [chars] mode
Explanation	The mode of indicated power type is available.
Recommended Action	No action is required.


%PLATFORM_POWER-1-UNAVAILABLE : Not enough [chars] power available for the system.
Explanation	Sufficient indicated type of power is not available for the system to function properly. This is a critical issue, and system may need to be reset. Please verify that the power source is fine. Check 'show power', and 'show platform' CLI output for further information. LOG_STD_ACTION
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PLATFORM_SCC


%PLATFORM_SCC-1-AUTHENTICATION_FAIL : Chassis authentication failed
Explanation	This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PLATFORM_TAM


%PLATFORM_TAM-2-SUDI_VALIDATION_FAILED : Secure UDI validation failed. [chars]
Explanation	Secure UDI validation for the module failed. The module failed to authenticate itself
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PLIM_QOS through POS_SPA_SPI4

PLIM_QOS
PM
PMAN
PMDWDM
PMIPV6
POLICY_API
POLICY_MANAGER
PORT_SECURITY
POS_SPA_FRMR
POS_SPA_SPI4

PLIM_QOS


%PLIM_QOS-3-IOSXE_RP_PLIM_QOS_FAIL : A software error while configuring the [chars] on slot [dec]
Explanation	This error happens when IOS fails to send messages to configure the per slot qos parameters in forwarding plane
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PM


%PM-1-INCONSISTENT_PORT_STATE : Inconsistent HW/SW port state for [chars]. Please shut/no shut the interface
Explanation	The hardware and software port state has become inconsistent.
Recommended Action	Enter the <CmdBold>shutdown<CmdBold> command followed by the <CmdBold>no shutdown<CmdBold> command on the interface specified in the message.


%PM-2-NOMEM : Not enough memory available for [chars]
Explanation	The Port Manager subsystem could not obtain the memory it needed.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_COOKIE : [chars] was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_CARD_COOKIE : an invalid card cookie was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_PORT_COOKIE : an invalid port cookie was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_VLAN_COOKIE : an invalid vlan cookie was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_CARD_SLOT : an invalid card slot ([dec]) was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_PORT_NUMBER : an invalid port number ([dec]) was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_VLAN_ID : an invalid vlan id ([dec]) was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_APP_ID : an invalid application id ([dec]) was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_APP_REQ : an invalid [chars] request by the '[chars]' application was detected
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-TOO_MANY_APP : application '[chars]' exceeded registration limit
Explanation	An invalid request was detected by the Port Manager.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-ERR_DISABLE : [chars] error detected on [chars], putting [chars] in err-disable state
Explanation	This is a defensive measure that will put the interface in err-disable state when it detects a mis-configuration or mis-behavior . A recovery will be attempted after the configured retry time (default 5 minutes).
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-ERR_RECOVER : Attempting to recover from [chars] err-disable state on [chars]
Explanation	This is an attempt to bring the interface back after taking it down to err-disable state
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-ERR_DISABLE_VP : [chars] error detected on [chars], vlan [dec]. Putting in err-disable state.
Explanation	This is a defensive measure that will put the virtual port (i.e., the port-vlan pair) in err-disable state when it detects a mis-configuration or mis-behavior. If so configured, a recovery will be attempted after the configured retry time (default 5 minutes).
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-ERR_RECOVER_VP : Attempting to recover from [chars] err-disable state on [chars], vlan [dec].
Explanation	This is an attempt to bring the virtual port back after taking it down to err-disable state
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-UNKNOWN_HOST_ACCESS : Invalid Host access value ([dec]) is received
Explanation	Host access table is being accesses with an invalalid host access value
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-INVALID_HOST_ACCESS_ENTRY : Invalid Host access entry type ([dec]) is received
Explanation	Host access entry should be one of configured/dynamic type
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-BAD_HA_ENTRY_EVENT : Invalid Host access entry event ([dec]) is received
Explanation	Host access table is entry event is not any of add/delete/update event
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-LIMITS : The number of vlan-port instances on [chars] exceeded the recommended limit of [dec]
Explanation	The total number of individual VLAN ports, counted over the module or switch specified in the error message, has exceeded the module or switch limit specified in the error message. VLANs can be counted more than once; if VLAN 1 is carried on 10 interfaces, it will count as 10 VLAN ports. For some platforms, e.g. Catalyst 6000, bundling is also ignored for purposes of this count; if 8 interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it will count as 8 VLAN ports.
Recommended Action	Reduce the number of trunks and VLANs configured in the module or switch specified in the error message. Keep the virtual port, VLAN port, count below the recommended limit specified in the configuration documentation. Enter the `show interface trunk` command to see the total number of trunks and VLANs.


%PM-3-ERR_INCOMP_PORT : [dec]/[dec] is set to inactive because [dec]/[dec] is a [chars] port
Explanation	Private host port can't be configured with trunk, private promiscuous, and span destination port on the same coil.
Recommended Action	Try to configure the incompatible ports on different coils.


%PM-4-EXT_VLAN_NOTAVAIL : VLAN [dec] not available in Port Manager
Explanation	Port Manager failed to allocate the requested VLAN. The VLAN is either used as an internal VLAN by other features or the maximum allowed extended VLANs are already configured.
Recommended Action	Try a different VLAN on the device if the limit on maximum allowed extended VLANs is not yet reached.


%PM-4-INT_VLAN_NOTAVAIL : Failed to allocate internal VLAN in Port Manager
Explanation	Port Manager failed to find any available internal VLAN
Recommended Action	Delete some extened range VLANs created by users or remove some features that require internal VLAN allocation, e.g. routed port


%PM-2-LOW_SP_MEM : Switch process available memory is less than [dec] bytes
Explanation	Switch Processor available memory dropped to a low level. Possibly too many Layer 2 VLANs are configured in the system.
Recommended Action	Removed features from the system to reduce memory usage.


%PM-4-EXT_VLAN_INUSE : VLAN [dec] currently in use by [chars]
Explanation	Port Manager failed to allocate the VLAN for external use as the VLAN is currently occupied by another feature
Recommended Action	Reconfigure the feature, e.g. routed port, to use another interal VLAN; Or request another available VLANs.


%PM-2-VLAN_ADD : Failed to add VLAN [dec] - [chars].
Explanation	Failed in adding VLAN to VTP. The reason is stated in the string.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-6-EXT_VLAN_ADDITION : Extended VLAN is not allowed to be configured in VTP CLIENT mode.
Explanation	This message will only be seen if you try to configure an extended VLAN while the switch is in VTP client mode. The configuration will fail and will not be written to the runnning configuration file, but otherwise switch performance and features will be unaffected.
Recommended Action	This is an informational message only, no further action is required. If you need to configure an extended VLAN, you must configure the switch to leave VTP client mode.


%PM-4-NO_SUBBLOCK : No PM subblock found for [chars]
Explanation	Failed to find PM subblock for this interface.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-INT_FAILUP : [chars] failed to come up. No internal VLAN available
Explanation	Port Manager failed to allocate internal VLAN and thus the interface cannot come up.
Recommended Action	Remove extended range VLAN to free up resouces.


%PM-4-VMPS_CFG : Dynamic access VLAN [dec] same as voice vlan on [chars].
Explanation	Access VLAN on VMPS server is set to same VLAN as voice VLAN on the port.
Recommended Action	Access VLAN assignment on VMPS server should be different from voice VLAN.


%PM-4-INACTIVE : putting [chars] in inactive state because [chars]
Explanation	The Port Manager has been blocked from creating a virtual port for the switch port and VLAN, causing the port to be in an inactive state. The reason for this condition is specified in the error message.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-3-INTERNALERROR : Port Manager Internal Software Error ([chars]: [chars]: [dec]: [chars])
Explanation	There is an internal software error encountered in the IOS Port 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.


%PM-4-PVLAN_TYPE_CFG_ERR : Failed to set VLAN [dec] to a [chars] VLAN
Explanation	Platform failed to set private vlan type.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%PM-4-PORT_BOUNCED : Port [chars] was bounced by [chars].
Explanation	The Port Manager needed to perform a reactivation of a port in the link down state during a switchover. A port is only reactivated when the port data structures lack consistency between the active and standby supervisors. Active ports in the link down state were returned to the link up state by the reactivation event.
Recommended Action	No action is required.


%PM-4-MPLS_MTU_PORT_CFG : MPLS MTU size [dec] is not supported by port [chars].
Explanation	The MPLS MTU size configured on the port is larger than the maximum MTU size that can be supported by this port. As a result, large packets can be dropped.
Recommended Action	Reduce the MPLS MTU size.


%PM-4-MPLS_MTU_EC_CFG : MPLS MTU size [dec] is not supported by one or more ports in channel [chars].
Explanation	The MPLS MTU size configured on the ethernet channel is larger than the maximum MTU size that can be supported by one or more ports in this channel. As a result, large packets can be dropped.
Recommended Action	Reduce the MPLS MTU size, or remove these ports from the channel before increasing the MPLS MTU size.


%PM-4-PORT_INCONSISTENT : Port [chars] is inconsistent: IDB state [chars] (set %TE ago), link: [chars] (%TE ago), admin: [chars] (%TE ago).
Explanation	Port Manager on Standby discovered that the port state has been inconsistent for more that 1 second. Inconsistent ports are reactivated on switchover (you will see PORT_BOUNCED message).
Recommended Action	No action is required.


%PM-4-PORT_CONSISTENT : Port [chars] consistency has been restored, IDB state: [chars].
Explanation	Port Manager on Standby discovered that port state became consistent again.
Recommended Action	No action is required.

PMAN


%PMAN-0-PROCESS_NOTIFICATION : The process lifecycle notification component failed because [chars]
Explanation	The process lifecycle notification component failed, preventing proper detection of a process start and stop. This problem is likely the result of a software defect in the software sub-package.
Recommended Action	Note the time of the message and investigate the kernel error message logs to learn more about the problem and see if it is correctable. If the problem cannot be corrected or the logs are not helpful, copy the error message exactly as it appears on the console along with the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PMAN-3-PROCFAILOPT : An optional process [chars] has failed (rc [dec])
Explanation	A process that does not affect the forwarding of traffic has failed.
Recommended Action	Note the time of the message and investigate the kernel error message logs to learn more about the problem. Although traffic will still be forwarded after receiving this message, certain functions on the router may be disabled as a result of this message and the error should be investigated. If the logs are not helpful or indicate a problem you cannot correct, copy the error message as it appears on the console and the output of show tech-support and provide the information to a Cisco technical support representative.


%PMAN-0-PROCFAILCRIT : A critical process [chars] has failed (rc [dec])
Explanation	A process important to the functioning of the router has failed.
Recommended Action	Note the time of the message and investigate the error message logs to learn more about the problem. If the problem persists, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support with the gathered information.


%PMAN-6-PROCSTART : The process [chars] has started
Explanation	The process has launched and is operating properly.
Recommended Action	No user action is necessary. This message is provided for informational purposes only.


%PMAN-6-PROCSHUT : The process [chars] has shutdown
Explanation	The process has gracefully shutdown.
Recommended Action	No user action is necessary. This message is provided for informational purposes only.


%PMAN-3-PROCHOLDDOWN : The process [chars] has been helddown (rc [dec])
Explanation	The process was restarted too many times with repeated failures and has been placed in the holddown state.
Recommended Action	This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.


%PMAN-3-PROCFAIL : The process [chars] has failed (rc [dec])
Explanation	The process has failed as the result of an error.
Recommended Action	This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.


%PMAN-3-PROCFAIL_IGNORE : [chars] process exits and failures are being ignored due to debug settings. Normal router functionality will be affected. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly.
Explanation	A process exit or failure is being ignored due to the user-configured debug settings.
Recommended Action	If this behavior is desired and the debug settings are set according to the user's preference, no action is needed. If the appearance of this message is viewed as a problem, change the debug settings. The router is not expected to behave normally with this debug setting. Functionality like SSO switchover, router reloads, FRU resets, etc. will be affected. This setting should only be used in a debug scenario. It is not normal to run the router with this setting


%PMAN-3-RELOAD_RP_SB_NOT_READY : Reloading: [chars]
Explanation	The RP is being reloaded since there is no ready standby instance
Recommended Action	Make sure this is not due to an error condition


%PMAN-3-RELOAD_RP : Reloading: [chars]
Explanation	The RP is being reloaded
Recommended Action	Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages


%PMAN-3-RELOAD_SYSTEM : Reloading: [chars]
Explanation	The system is being reloaded
Recommended Action	Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages


%PMAN-3-RPSWITCH : RP switch initiated. Critical process [chars] has failed (rc [dec])
Explanation	A RP switchover has been initiated due to a critical fault
Recommended Action	Make sure this is not due to an error condition. If it is due to an error condition, collect debug information like all console output and log files


%PMAN-3-PROC_BAD_EXECUTABLE : Bad executable or permission problem with process [chars]
Explanation	The executable file used for the process is bad or has permission problem
Recommended Action	Make sure that the named executable is replaced with correct executable


%PMAN-3-PROC_BAD_COMMAND : Non-existent executable or bad library used for process [chars]
Explanation	The executable file used for the process is missing or a dependent library is bad
Recommended Action	Make sure that the named executable is present and dependent libraries are good


%PMAN-3-PROC_EMPTY_EXEC_FILE : Empty executable used for process [chars]
Explanation	The executable file used for the process is empty
Recommended Action	Make sure that the named executable is of non-zero size


%PMAN-5-EXITACTION : Process manager is exiting: [chars]
Explanation	The process manager is exiting
Recommended Action	Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages


%PMAN-6-PROCSTATELESS : The process [chars] is restarting stateless
Explanation	The process has requested a stateless restart.
Recommended Action	No user action is necessary. This message is provided for informational purposes only.


%PMAN-3-RELOAD_FRU_IGNORED : All [chars]/[dec] reloads are being ignored. This is being done for debugging purposes and will be changed at a later time to allow the reload. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly.
Explanation	A supervisor failure is being ignored due to debugging purposes.
Recommended Action	This will be removet at a later point in time


%PMAN-3-PROC_RESTART_CNT_EXCEEDED : The process [chars] restart count ([dec]) has exceeded the configured limit ([dec])
Explanation	The process was restarted many times and has exceeded the configured limit.
Recommended Action	This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.

PMDWDM


%PMDWDM-4-TCA : [chars]: [chars] [chars] [chars] value (%lld) threshold (%lld) [chars]
Explanation	The specified PM FEC TCA has been declared or released
Recommended Action	Recommended action is to repair the source of the alarm.

PMIPV6


%PMIPV6-5-TUNNELDELETE : Deleting the Proxy Mobile IPv6 tunnel [chars]
Explanation	The PMIPv6 tunnel is being deleted.
Recommended Action	If you suspect this condition contact technical support representative with the output of show tech


%PMIPV6-5-TUNNELUP : Bringing up the Proxy Mobile IPv6 tunnel [chars]
Explanation	The PMIPv6 tunnel is being deleted.
Recommended Action	If you suspect this condition contact technical support representative with the output of show tech

POLICY_API


%POLICY_API-4-POLICYOVERIDE : Dynamic policy overriding static on intf:[chars]
Explanation	Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy.
Recommended Action	Remove the static policy config if desired.


%POLICY_API-4-POLICYSTATICCLR : Static policy on intf:[chars] cleared. Dynamic policy in use.
Explanation	A dynamic policy was overriding the static policy. Static policy has been cleared.
Recommended Action	No action required.


%POLICY_API-4-POLICYDYNCLR : Dynamic policy on intf:[chars] cleared. Static policy in use.
Explanation	A dynamic policy was overriding the static policy. The dynamic policy has been cleared, the static policy is now in effect.
Recommended Action	No action required.


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

POLICY_MANAGER


%POLICY_MANAGER-2-INIT_FAILURE : Init failure: [chars]
Explanation	A problem occurred in the Policy Manager during initialization
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%POLICY_MANAGER-3-PRE_INIT_CALL : Policy Manager routine called prior to initialization
Explanation	The Policy Manager component was called prior to initialization. This could result in vital information being lost.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%POLICY_MANAGER-2-NO_FREE_EVENT_BUFFERS : Event pool depleted: [chars]
Explanation	The event pool has been depleted. There are no free buffers to process event
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%POLICY_MANAGER-3-INVALID_SEVERITY : Invalid event severity [hex]
Explanation	The event that was received by the Policy Manager contained an invalid severity and was therefore not processed.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%POLICY_MANAGER-3-NULL_ACTION_ROUTINE : NULL action routine invoked
Explanation	The Policy Manager attempted to invoke an action which was NULL
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%POLICY_MANAGER-3-INVALID_ACTION : Invalid action
Explanation	An invalid Policy Manager action was detected.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%POLICY_MANAGER-3-INVALID_PARAMETERS : A call to Policy Manager is made with invalid parameters
Explanation	A call to Policy Manager was made with one or more invalid parameters
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%POLICY_MANAGER-3-NO_FREE_POLICY_IDS : No more Policy IDs available
Explanation	There are no more Policy IDs that can be allocated. The effect of this is that Policy Manager policies can no longer be created.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

PORT_SECURITY


%PORT_SECURITY-2-PSECURE_VIOLATION : Security violation occurred, caused by MAC address [enet] on port [chars].
Explanation	An unauthorized device attempted to connect on a secure port. The MAC address of the unauthorized device and the secure port are specified in the error message.
Recommended Action	Determine the device that attempted to connect on the secure port. Notify your network system administrator of this condition.


%PORT_SECURITY-2-PSECURE_VIOLATION_VLAN : Security violation on port [chars] due to MAC address [enet] on VLAN [dec]
Explanation	An unauthorized device attempted to connect on a secure trunk port. The MAC address of the unauthorized device and the secure trunk and VLAN are specified in the error message.
Recommended Action	Determine the device that attempted to connect via the secure trunk port. Notify your network system administrator of this condition.


%PORT_SECURITY-6-VLAN_REMOVED : VLAN [int] is no longer allowed on port [chars]. Its port security configuration has been removed.
Explanation	A configured VLAN has been excluded either due to port mode change or allowed VLAN list change and is removed from the configuration.
Recommended Action	No action is required.


%PORT_SECURITY-6-ADDR_REMOVED : Address <[int]:[enet]> exists on port [chars]. It has been removed from port [chars].
Explanation	A routed port has changed to a switched port. An address stored in the previous switched port configuration is now in conflict and has been deleted.
Recommended Action	No action is required.


%PORT_SECURITY-6-VLAN_FULL : Vlan [int] on port [chars] has reached its limit. Address [enet] has been removed.
Explanation	The voice VLAN has become the same as the access VLAN, but the number of addresses allowed on the access VLAN has been reached, so the address has been deleted.
Recommended Action	No action is required.


%PORT_SECURITY-6-ADDRESSES_REMOVED : Maximum system secure address count reached. Some secure addresses configured on port [chars] removed.
Explanation	Some configured and sticky MAC addresses on the specified port were removed from the configuration. The number of secure addresses that the system supports was exceeded. This condition occurs only during hot swapping or port-mode changes (for example, when the port is converted from a L3 to a L2 port).
Recommended Action


%PORT_SECURITY-6-ADDR_ADDFAIL : Address <[int]:[enet]> could not be added to [chars] due to [chars].
Explanation	In some rare cases MAC addresses are learnt before all software modules finished initialization and fully functional. In such cases this address may not be known to all modules in the system.
Recommended Action	No action is required.

POS_SPA_FRMR


%POS_SPA_FRMR-3-RESTART_FAILURE : Framer restart failed for SPA in [int]/[int] with error [dec] during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, framer restart error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-RECONFIG_FAILURE : Framer reconfiguration failed for SPA in [int]/[int], with error [dec] during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the framer reconfig error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-RECONCILE_FAILURE : Framer reconcilation failure for SPA in [int]/[int] during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the framer reconcilation error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-TRANSMIT_DELAY_MISMATCH : The software ([int]) and hardware ([int]) copy of transmit-delay is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the transmit delay parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-CRC_MISMATCH : The software ([dec]) and hardware ([dec]) copy of crc is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the crc parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-MTU_MISMATCH : The software ([dec]) and hardware ([dec]) copy of mtu is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the mtu is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-FRAMING_MISMATCH : The software ([dec]) and hardware ([dec]) copy of framing is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the framing parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-C2_MISMATCH : The software ([int]) and hardware ([int]) copy of sonet c2 is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the sonet C2 parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-S1S0_MISMATCH : The software ([int]) and hardware ([int]) copy of sonet S1S0 is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the sonet S1S0 parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-LOOPBACK_MISMATCH : The software ([dec]) and hardware ([dec]) copy of loopback is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the loopback parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-SCRAMBLE_MISMATCH : The software ([dec]) and hardware ([dec]) copy of scrambling is detected to be different during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the software and hardware copy of the scrambling parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_FRMR-3-NULL_DEV_OBJ :
Explanation	Pointer to framer device object is NULL.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.

POS_SPA_SPI4


%POS_SPA_SPI4-3-RESTART_FAILURE : SPI4 restart failed for SPA in [int]/[int] with error [dec] during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, spi4 restart error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.


%POS_SPA_SPI4-3-RECONFIG_FAILURE : SPI4 reconfiguration failed for SPA in [int]/[int], with error [dec] during Minimal Disruptive Restart.
Explanation	During Minimal Disruptive Restart, the spi4 reconfig error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action	Open a case with Cisco Technical Assistance Center for further assistance.

PRELIB_DL through QOS

PRELIB_DL
PRST_IFS
PSM
PT
PTPD
PUNT_INJECT
PW
QFP_MLP
QLLC
QOS

PRELIB_DL


%PRELIB_DL-3-UNREGISTERED_DLOPEN : Unregistered request to dlopen library [chars]
Explanation	The program is attempting to dynamically open a library that has not been explicitly listed on its list of dynamically opened libraries. This represents a potential security threat as well as creates potential run-time instabilities
Recommended Action	File a DDTS against the listed program to register the library in question. If this was an unexpected call to dlopen then the source of the call should be root-caused and closed

PRST_IFS


%PRST_IFS-3-GENERAL : persistent media IFS general error: [chars]
Explanation	Persistent media module (file system) general 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.


%PRST_IFS-3-FILE : persistent media IFS file error: [chars]
Explanation	Persistent media module (file system) file 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.


%PRST_IFS-3-FILEMEM : No memory to update [chars]. Please free some space
Explanation	There is no filesystem memory for the system to write an updated version of the persistent variable file.
Recommended Action	Please free space on the filesystem shown in the error message as soon as possible. This will involve deleting existing files, and/or squeezing the filesystem if the filesystem requires it (bootflash for example may require it).

PSM


%PSM-3-BADLABELADD : Cannot add label - [chars].
Explanation	Unable to create label due to reason given.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PSM-3-NOOCE : Attempt to get labels from OCE failed - [chars].
Explanation	Calling function has provided insufficient information to get labels.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PSM-3-NONIPINFO : Non-ip info: [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.


%PSM-3-CHUNK : [chars]: [chars] [hex] [hex]
Explanation	Parameterized Chunk Manager error occurred
Recommended Action	Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of `show version`, `show running-config` and `show process memory` and contact your Cisco technical support representative.


%PSM-3-INVALIDPARAM : Invalid parameter - [chars]
Explanation	Calling function has passed an invalid parameter.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PSM-3-NORESOURCE : [chars] [dec]
Explanation	Resource Failure: %s %d
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PSM-3-ISSU_REG : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [chars]
Explanation	ISSU negotiation failed for this XDR client.
Recommended Action	This error indicates a coding problem. It is an error that will occur every time this image is run, and requires a code change to fix it.


%PSM-3-L2_PATH : [chars] - path set [hex]([IPV6 address]), path [chars]
Explanation	Internal error while processing layer 2 path.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PT


%PT-3-BADSCOPERATION : Invalid [chars] of subcommand [dec] on ruleset %S.
Explanation	An internal software error occurred.
Recommended Action	If any of these messages recur, call your technical support representative for assistance.


%PT-3-BADRULEUNLOCK : Invalid unlock on ruleset %S, [chars].
Explanation	An internal software error occurred.
Recommended Action	If any of these messages recur, call your technical support representative for assistance.


%PT-3-BADRULEDELETE : Error deleting ruleset %S, [chars].
Explanation	An internal software error occurred.
Recommended Action	If any of these messages recur, call your technical support representative for assistance.


%PT-3-NOOPERATION : No [chars] operation defined for [chars] parameter [chars].
Explanation	An internal data consistency error has been detected.
Recommended Action	Call your technical support representative for assistance.


%PT-6-INVOPERATION : An invalid [chars] operation defined for [chars] parameter [chars].
Explanation	An internal data consistency error has been detected.
Recommended Action	This is an internal verification message, and doesn't affect operation, but notify your technical support representative that this image has this problem.


%PT-4-RULESETWRITER : PT ruleset %S evaluation skipped; ruleset is being modified.
Explanation	An incoming connection attempt was not evaluated by the identified PT ruleset because that ruleset is in the process of being modified.
Recommended Action	The editing of the ruleset must be completed before it's eligible to process an incoming connection attempt.


%PT-3-PARAMEVALERR : PT ruleset %S parameter error in [chars] line [dec]; [chars] [dec].
Explanation	A parameter evaluation error was detected for the specified ruleset, operation and line.
Recommended Action	Call your technical support representative for assistance.


%PT-3-PARAMRESULTERR : PT ruleset %S protocol [chars] parameter [chars] parse error: [chars].
Explanation	The final value of a ruleset's protocol/parameter string could not be decoded.
Recommended Action	Review the ruleset elements that set the parameter value to determine if they need to be modified to generate a valid result.


%PT-3-PARAMRESULTINVALID : PT ruleset %S protocol [chars] parameter [chars] invalid: [chars].
Explanation	The value of a ruleset's protocol/parameter is not valid.
Recommended Action	Review the ruleset elements that set the parameter value to determine if they need to be modified to generate a valid result.


%PT-4-PARAMCHANGED : PT ruleset %S: [chars] parameter [chars] changed; [chars].
Explanation	A protocol parameter value, generated by a ruleset, was modified to be valid for protocol translation operation.
Recommended Action	Review the ruleset processing for the identified parameter to determine if it needs to be modified to generate a value that is, for example, within the range of values supported for PT.


%PT-6-RULESETLIMIT : Ruleset [chars] refused an incoming connection due to the max-user limit.
Explanation	An incoming connection attempt that would normally be processed by a Protocol Translation ruleset has been refused because of the ruleset's configured max-user limit.
Recommended Action	The network administrator may need to verify that the ruleset max-user limit is appropriate.


%PT-6-RULESETACCESS : Ruleset [chars] refused an incoming connection due to the access-class.
Explanation	An incoming connection attempt that was matched by a Protocol Translation ruleset has been refused because the source address failed the ruleset's configured access-class test.
Recommended Action	The network administrator may need to verify that the ruleset access-class configuration is appropriate.

PTPD


%PTPD-0-CHASFS_OBJECT_CREATE : Failed to create chassis filesystem object [chars] because [chars]
Explanation	The hardware failed to create a chassis filesystem object.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-3-CHASFS_OBJECT_DESTROY : Failed to destroy chassis filesystem object [chars] because [chars]
Explanation	A chassis filesystem object that should have been destroyed was not destroyed.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-CHASFS_PROPERTY_CREATE : Failed to create chassis filesystem object [chars] property [chars] because [chars]
Explanation	A chassis filesystem property was not properly created.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-3-CHASFS_PROPERTY_DESTROY : Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars]
Explanation	A chassis filesystem property that should have been destroyed was not destroyed.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-CHASFS_PROPERTY_GET : Failed to read chassis filesystem object [chars] property [chars] because [chars]
Explanation	A chassis filesystem property was not properly read by the system.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-CHASFS_PROPERTY_SET : Failed to write chassis filesystem object [chars] property [chars] because [chars]
Explanation	A chassis filesystem property failed to write.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-CHASFS_OBJECT_WATCH : Failed to watch chassis filesystem object [chars] because [chars]
Explanation	A chassis filesystem object was not watched because of the reason stated in the error message.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-CHASFS_OBJECT_NOT_PRESENT : Expected chassis filesystem object [chars] not present.
Explanation	A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-CHASFS_PROPERTY_NOT_PRESENT : Expected chassis filesystem object [chars] property [chars] not present.
Explanation	A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-IPC_INITIALIZATION : IPC initialization failed because [chars]
Explanation	IPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-IPC_CONNECT_MASTER : IPC connection to the active RSP failed because [chars]
Explanation	IPC connection to the active RSP failed. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-IPC_CONNECTION_INVALID : An IPC connection has invalid state.
Explanation	An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-MQIPC_INITIALIZATION : MQIPC initialization failed because [chars]
Explanation	MQIPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-MQIPC_ADVANCE : Failed to advance MQIPC queue because [chars]
Explanation	The MQIPC initialization failed.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-MESSAGE_REGISTER : Failed to register with active RSP because [chars]
Explanation	The active RSP failed to register.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-MESSAGE_RESPONSE : An invalid message response was received because [chars]
Explanation	An invalid message response was received. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-MESSAGE_RELAY : Failed to relay a message because [chars]
Explanation	Failed to relay a message. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-RESOURSE : Resource allocation failed in [chars] because [chars]
Explanation	The system is unable to allocate the requested resource.
Recommended Action	In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command.


%PTPD-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation	An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%PTPD-0-PEER_TABLE : A peer table initialization or maintenance function failed because [chars]
Explanation	A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.

PUNT_INJECT


%PUNT_INJECT-2-CAUSE_CFG_ERR : [chars] [chars] initialization failed
Explanation	Initialization of Punt/Inject cause failed due to invalid configuration parameters
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PUNT_INJECT-3-DROP_POLICY_SKIPPED : [chars] cause=[dec] output drop policy skipped
Explanation	Output drop policy unexpected skipped on punt packet
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PUNT_INJECT-5-DROP_PUNT_INTF : punt interface policer drop packet from [chars], MSGDEF_LIMIT_SLOW
Explanation	drop punt packet from source interface
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%PUNT_INJECT-5-DROP_PUNT_CAUSE : punt cause policer drop packet cause [dec], MSGDEF_LIMIT_SLOW
Explanation	drop punt packet by punt cause policer
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

PW


%PW-3-IPC_ALLOC_FAILED : [chars]
Explanation	Allocation of an IPC packet buffer by the pseudo wired feature failed.
Recommended Action	LOG_STD_ACTION


%PW-3-IPC_SEND_FAILED : [chars]
Explanation	Transmission of an IPC message by the pseudo wire feature failed.
Recommended Action	LOG_STD_ACTION

QFP_MLP


%QFP_MLP-2-BQS_SCRATCH_TOOSMALL : QFP BQS Scratch area too small for MLP feature usage (size: [dec], need: [dec]).
Explanation	Cisco internal software error. QFP MLP initialization detected that the BQS scratch memory area is insufficient for MLP usage. The MLP 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.


%QFP_MLP-2-PROXY_IPC_INIT_FAILED : QFP MLP Proxy IPC interface initialization failure (result: [dec]).
Explanation	Cisco internal software error. QFP MLP initialization detected that the Proxy IPC interface initialization failed. The MLP 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.


%QFP_MLP-3-INV_PROXY_MSG : QFP MLP Proxy received invalid Message ID [dec]
Explanation	Cisco internal software error. QFP MLP 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.


%QFP_MLP-3-PROXY_INV_RX_TX_INTF_VALUE : QFP MLP Proxy ([chars] [chars]) invalid Rx/Tx interface value [dec] for interface [dec] (handle)
Explanation	Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid interface Rx/Tx designation in the proxy request. The associated MLP 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.


%QFP_MLP-3-PROXY_NULL_BUNDLE : QFP MLP Proxy ([chars] [chars]) NULL Bundle sub-block for interface [dec] (handle)
Explanation	Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid or uninitialized Bundle sub-block. The associated MLP 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.


%QFP_MLP-3-PROXY_NULL_LINK : QFP MLP Proxy ([chars] [chars]) NULL Member Link sub-block for interface [dec] (handle)
Explanation	Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Member Link state change or configuration update due to an invalid or uninitialized Member Link sub-block. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_BUNDLE_STATE : QFP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Bundle being in an incorrect state to accept the message. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_LINK_STATE : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Link being in an incorrect state to accept the message. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_SUB_DEV_ID : QFP MLP Proxy ([chars] [chars]) invalid Sub-Device ID [dec] for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message Bundle Add could not be processed for the indicated interface due to an invalid Sub-Device ID. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_LINK_ID : QFP MLP Proxy ([chars] [chars]) invalid Link ID [dec] for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message Link Add could not be processed for the indicated interface due to an invalid Link ID. The associated MLP 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.


%QFP_MLP-3-PROXY_DUP_LINK_ID : QFP MLP Proxy ([chars] [chars]) duplicate Link ID [dec] for interface [chars] and [chars]
Explanation	Cisco internal software error. QFP MLP 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 MLP Bundle. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_CLASS_INFO : QFP MLP Proxy ([chars] [chars]) invalid Class Info (Base: [hex], Num: [dec]) for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message contained invalid MLP Class information. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_MRRU : QFP MLP Proxy ([chars] [chars]) invalid MRRU [dec] for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message contained an invalid MLP Bundle MRRU. The associated MLP Bundle interface may not be fully functional as a result of this condition. Possible workaround is to reduce the interface mtu on the Multilink bundle interface on both ends of the connection to 9216 or less and then shut/no shut the Multilink bundle interface to force renegotiation of the MLP MRRU.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QFP_MLP-3-PROXY_INV_LOST_FRAG_TO : QFP MLP Proxy ([chars] [chars]) indicated an invalid lost fragment timeout ([dec]) for interface [chars]
Explanation	Cisco internal software error. QFP MLP was provided a invalid lost fragment timeout value. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_BUFFER_LIMIT : QFP MLP Proxy ([chars] [chars]) indicated an invalid Rx buffer limit ([dec]) for interface [chars]
Explanation	Cisco internal software error. QFP MLP was provided a invalid Rx buffer limit value. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_TX_LINK_WEIGHT : QFP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link weight ([dec]) for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link weight information. The associated MLP 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.


%QFP_MLP-3-PROXY_INV_TX_LINK_FRAG_SIZE : QFP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link optimal fragment size ([dec]) for interface [chars]
Explanation	Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link optimal fragment size information. The associated MLP 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.


%QFP_MLP-3-PROXY_B_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]/[chars]
Explanation	Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Bundle state at the time of the request. The associated MLP 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.


%QFP_MLP-3-PROXY_LAI_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]
Explanation	Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the link to an Idle-Link. The associated MLP 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.


%QFP_MLP-3-PROXY_LIA_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]
Explanation	Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the Idle-Link to an active link. The associated MLP 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.


%QFP_MLP-4-PROXY_SYNC : QFP MLP Proxy ([chars] [chars]) Bundle/Link sync issue with interface [chars]
Explanation	Cisco internal software error. QFP MLP 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.


%QFP_MLP-3-PROXY_IPC_ALLOC_FAIL : QFP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation	Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during response processing. The associated MLP 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.


%QFP_MLP-4-PROXY_IPC_ALLOC_FAIL2 : QFP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation	Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during proxy response processing. The associated MLP 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.


%QFP_MLP-3-PROXY_SID_UPDATE_LOCK_ERROR : QFP MLP Proxy ([chars]) Multiple SID Update Locks to same interface (Interface [chars], SID: [hex])
Explanation	Cisco internal software error. QFP MLP 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.


%QFP_MLP-3-PROXY_SID_UPDATE_COMPLETE_ERROR : QFP MLP Proxy ([chars]) SID Update Complete w/o Preceeding Lock (Interface [chars], SID: [hex])
Explanation	Cisco internal software error. QFP MLP 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.


%QFP_MLP-3-EARLY_RX_INIT : QFP MLP Early Receive initialization error ([chars])
Explanation	Cisco internal software error. Multilink Early Receive initialization could not be performed due to indicated error. This could cause possible lost MLP encapsulated packets during member link/bundle bringup and possibly cause the failure to complete member link/bundle initialization.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QFP_MLP-3-EARLY_RX_CLEANUP : QFP MLP Early Receive cleanup error ([chars])
Explanation	Cisco internal software error. Multilink Early Receive cleanup could not be performed due to indicated error. This could cause possible QFP memory leak.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QFP_MLP-3-MCMP_TX_ENCAP_SEQ_CFG_ERROR : MLP QoS encap-sequence ([dec]) must be less than the number of MCMP suspension classes ([dec]) for output interface [chars], MSGDEF_LIMIT_SLOW
Explanation	User software configuration mismatch with PPP Multilink Multiclass (MCMP). User needs to either reduce the highest encap-sequence in the policy-map to be less than the number of negotiated MCMP suspension classes or increase the number of suspension classes negotiated with the 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.


%QFP_MLP-3-MCMP_INVALID_RX_CLASS : MLP MCMP suspension class ID ([dec]) received from the peer must be less than the number of negotiated classes ([dec]) for interface [chars] (Peer error), MSGDEF_LIMIT_SLOW
Explanation	Possible error on the peer device with PPP Multilink Multiclass (MCMP). Received MLP packet contained a MCMP suspension class ID greater than the number of negotiated suspension classes.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QFP_MLP-4-TX_BUNDLE_FLOWED_OFF : QFP MLP Tx Bundle [chars] flowed OFF for an abnormal duration due to one or more congested member link(s) (Ticks: [dec])
Explanation	Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP 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.


%QFP_MLP-4-TX_BUNDLE_FLOWED_ON : QFP MLP Tx Bundle [chars] flowed ON after being flowed OFF for an abnormal duration (Ticks: [dec])
Explanation	Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP 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.


%QFP_MLP-3-MLP_INVALID_EVSI_INTF_STATE : MLP Link Add/Update receved with invalid EVSI indication for Member Link: [chars], Bundle: [chars]
Explanation	Either the user attempted to mix broadband and non-broadband member links on the same bundle or an internal error has occurred processing a configuration update.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QFP_MLP-4-TX_BUNDLE_LOOP : QFP detected re-entry into MLP Tx Bundle [chars])., MSGDEF_LIMIT_SLOW
Explanation	Possible software configuration error in the network that causes re-entry of packets into the MLP Tx bundle. Packets are being discarded and the bundle will not be fully operational until the loop is terminated
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

QLLC


%QLLC-3-NOMEM : Not enough memory available
Explanation	There is not enough memory in the system to complete this request.
Recommended Action	Add more memory to the router. Otherwise, reduce the configuration or the load on the router.


%QLLC-3-NOLLC2 : Unable to open an llc2 session
Explanation	An LLC2 session could not be established with the destination MAC address.
Recommended Action	Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.


%QLLC-3-NULLPTR : [chars] ptr is null
Explanation	The specified structure was not configured.
Recommended Action	Confirm the configuration commands for the structure.


%QLLC-4-NOQLLC : Unable to open qllc session, current state is [chars]
Explanation	A QLLC session could not be established.
Recommended Action	Verify that the qllc partner and the qllc xid commands are correct.


%QLLC-3-DIFFPRTR : [enet] - Different partner - originally [enet] - now [enet]
Explanation	The partner for this QLLC virtual MAC address does not match the MAC address that was defined with the qllc partner command.
Recommended Action	Verify that the qllc partner statement in the configuration file is correct.


%QLLC-3-NONULLXID : Couldn't make null xid - [enet] -[enet]
Explanation	An attempt to create an IEEE XID failed.
Recommended Action	Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.


%QLLC-3-NOXID2 : Couldn't make xid - [enet] -[enet]
Explanation	The QLLC XID could not be forwarded to the LAN.
Recommended Action	Verify that the qllc partner and the qllc xid commands are correct.


%QLLC-3-BADSTATE : Bad qllc state - [chars] - [enet]
Explanation	An invalid LLC primitive was detected.
Recommended Action	Verify that the Token Ring ports and any participating LAN devices are configured correctly.


%QLLC-3-NOMACADDR : No lnx entry for macaddr [enet]
Explanation	No virtual MAC address was defined for this interface.
Recommended Action	Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command.


%QLLC-3-BADOPCODE : Opcode [chars] is invalid
Explanation	Either remote source-route bridging or local acknowledgment is configured incorrectly.
Recommended Action	Verify that remote source-route bridging and local acknowledgment are configured correctly.


%QLLC-3-IFRAME : [chars]
Explanation	An I-Frame was discarded due to network congestion.
Recommended Action	Verify that the LAN is not beaconing and that it is not in a congested state. Copy the error message exactly as it appears, and report it to your technical support representative.


%QLLC-3-BADSTATEEVENT : Bad qllc state - [chars] event - [chars] macaddr - [enet]
Explanation	The LLC primitive specified placed the router in an invalid state.
Recommended Action	Verify that the Token Ring ports and any participating LAN devices are configured correctly.


%QLLC-3-NOPAKENQ : Pak enqueue failed
Explanation	A packet was not sent to the LAN.
Recommended Action	Verify that the LAN partner is configured correctly, and that the partner is on the desired LAN.


%QLLC-3-BADRSRBOPCODE : Bad opcode [hex] from [enet] to [enet]
Explanation	Either remote source-route bridging is incorrectly configured, or the other RSRB device is down.
Recommended Action	Verify that remote source-route bridging is configured correctly with the right version of the IOS software.


%QLLC-3-LNXNOTFOUND : lnx_remove_macaddr_hash did not find target lnx
Explanation	The qllc srb command was not defined for this interface.
Recommended Action	Add a valid qllc srb statement for this serial interface.


%QLLC-3-BADQLLCSTATE : Bad qllc state - [chars]
Explanation	An invalid QLLC primitive was detected.
Recommended Action	Verify that the partner QLLC device is configured correctly.


%QLLC-3-GENERRMSG : [chars]
Explanation	The text string provided with this error message describes the specific QLLC problem.
Recommended Action	Follow the instructions that appear with the error message. Copy the error message exactly as it appears, and report it to your technical support representative.


%QLLC-3-BAD_XID : Sna configuration error for [enet]: Lan device is PU2.1, X.25 device is PU2.0 (XID Format 1)
Explanation	The IBM Gateway (3172) or front-end processor on the LAN is sending XID Format 3 which is used to communicate with PU2.1 devices. The X.25 device is a PU2.0 (3174) that is configured to send XID Format 1 messages. This is a very rare situation - for example, Revision A5.6 on, and C5.1 on the 3172. A likely cause is that the revision levels on the IBM equipment are incompatible.
Recommended Action	Check the revision levels on the external equipment, and upgrade them if necessary.


%QLLC-3-NO_QLLCBUFFER : M bit Reassembly failed - couldn't allocate a packet
Explanation	The router ran out of memory to allocate buffers.
Recommended Action	Make sure that the router configuration is adequate for the service expected of it. You might want to tune the buffer pools, or upgrade to a larger router. At the very least, you will need more memory.


%QLLC-3-INCALL_CFG : Incoming call: No QLLC Service Access Point Configured for x.25 subaddress [chars]
Explanation	A remote X.25 device is calling the router for QLLC service using a subaddress that was not configured by the X.25 routing facility. The subaddress was not configured for QLLC service.
Recommended Action	Correct the QLLC configuration. Configure only the subaddress on the QLLC service, not the complete X.121 address that the remote X.25 device uses.


%QLLC-3-INCALL_NO_PARTNER : Incoming call: No partner Mac Address configured - X.25 subaddress [chars]
Explanation	There is an incoming call, but a connection cannot be initiated to a partner since no partner is configured in a qllc dlsw command (for QLLC/DLSw+ only).
Recommended Action	Configure a partner for the incoming calling (such as using the qllc dlsw partner command).


%QLLC-3-PARTNER_MISMATCH : Outgoing call: Partner Mac Address [enet] doesn't match configured partner [enet]
Explanation	A device tried to connect to a QLLC VMAC (from Token Ring, for instance), but the MAC address of that device does not match the partner in the qllc dlsw command.
Recommended Action	Correct the QLLC configuration to match the right partner.


%QLLC-3-QLLCMAP_ERR : Incoming call: QLLC map entry not found
Explanation	A software error in the router code occurred.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%QLLC-3-NO_QSR : No QLLC Service Access Points defined
Explanation	No QLLC services have been configured, even though the router will accept incoming calls for QLLC.
Recommended Action	Configure the QLLC service required.


%QLLC-3-NO_RESOURCE : Incoming Call: Insufficient resources available
Explanation	This message is reporting insufficient system memory.
Recommended Action	Upgrade the memory.

QOS


%QOS-3-DETACH : Failed to detach [chars] [chars] service policy
Explanation	The specified type of service policy has failed to detach itself from the attachment point indicated. The service policy will remain attached although repeated attempts to remove such should fail in a similar manner.
Recommended Action	LOG_STD_SH_CMD_ACTION(show policy-map [type] <attachment point>)


%QOS-4-SERV_FRAG_POLICY : service-policy [chars] can't be attached without corresponding service-fragment policy on appropriate target first
Explanation	For a fragment policy that is being installed check if parent targets have relevant service-fragment class installed. If not then we can not allow fragment policy installation.
Recommended Action	Check the parent target to add relevant service-fragment class.


%QOS-6-SUSPEND : Suspending service policy [chars] on [chars] in [chars] direction
Explanation	The interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.
Recommended Action	There is no user action required.


%QOS-3-TARGET_INDEX : [chars] [chars] service policy attachment failed to assign index
Explanation	The configuration of a service policy has resulted in the failure to generate an internal unique identifier which represents the attachment point (target) of the associated policy map. This is an internal 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.


%QOS-3-UNASSIGNED : A [chars] event resulted in an (un)assigned index for [chars] [chars]
Explanation	The configuration of either the addition or removal of the specified entity has resulted in the failure to either assign or remove a previously assigned index from such. This is an internal software error and indicates an out of sync condition if operating in a redundant manner
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-3-ISSU_GTP_CFG_ENHANCE : GTP-AIC configuration has been detected, which is totally different with peer. Delete all GTP-AIC related config to proceed with ISSU/ISSD. After ISSU/ISSD done, config GTP-AIC again.
Explanation	PEER GTP-AIC configuration would be messed up.
Recommended Action	Manually remove all GTP-AIC configuration and reinitiate ISSU/ISSD.


%QOS-6-POLICY_INST_FAILED : Service policy installation failed on [chars]. [chars]. policy:[chars], dir:[chars], ptype:[chars], ctype:[chars]
Explanation	Service policy could not be installed
Recommended Action	This is an informational message only. No action is required.


%QOS-6-POLICY_REM_FAILED : Service policy remove failed on [chars] policy:[chars], dir:[chars], ptype:[chars], ctype:[chars]
Explanation	Service policy could not be removed
Recommended Action	This is an informational message only. No action is required.


%QOS-3-INVALID_PLTYPE : No entry found for pltype : [int] in global service_policy_queue during service-policy deletion.
Explanation	No entry was found for a pltype when un-queue of a service-policy from global service_policy_queue was undergoing. This will result in freeing a service-policy without un-queuing it from global service_policy_queue.
Recommended Action	Need to figure out why there was no entry found for a pltype in the global service_policy_queue when passed with a service-policy while deletion. check the traceback for details


%QOS-3-HA_COLLISION_INVALID : Received collision table of type [int]
Explanation	The specified type of collision is an invalid value which indicates that the message received on the standby RP contains erroneous data. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active 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.


%QOS-3-HA_COLLISION_SIZE : Received [chars] message, total/unit [int]/[int] [chars]
Explanation	The specified type of collision table has been determined to contain a discrepancy between the total message size and the individual table unit that is being decoded on the standby RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active 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.


%QOS-3-HA_COLLISION_STRING : Received [chars] message, length [int] for string [chars]
Explanation	The specified type of collision table contains an individual unit within the message which has an incorrectly encoded string which is used to represent the collision which is being synced from the active RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active 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.


%QOS-3-COLLISION_TYPE : Type [int] is invalid for collision [chars]
Explanation	The specified type of collision is an invalid value which indicates that there is no support for the generation of an internal identifier. This is an internal 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.


%QOS-3-COLLISION_DELETE : [chars] unable to remove index [hex]
Explanation	The specified type of collision is unable to removed the specified index. This is an internal 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.


%QOS-3-COLLISION_COUNT : [chars] mismatch, count [int]
Explanation	The specified type of collision has detected that although there are no collisions present the count of such indicates otherwise. This is an internal 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.


%QOS-6-COLLISION_MAX : Maximum number of collision entries, [int], reached
Explanation	The system limit on the number of collision entries used in assigning unique identifiers for policy and class maps et al. has been reached. This indicates that no further configuration of entities which require additional generation of a unique identifier will be possible.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-3-INDEX_EXISTS : [chars] attempt to add index [hex] [chars]
Explanation	The specified entity is unable to add an entry due to the detection of an existing entry with the same index or name. This is an internal software error.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the `show cce cp id [collisions]` command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-3-INDEX_DELETE : [chars] unable to remove index [hex]
Explanation	The specified entity is unable to removed the specified index. This is an internal 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.


%QOS-3-BLT_INDEX : Failed to assign index for target/policy/class/action [int]/[int]/[int]/[chars]
Explanation	The configuration of queuing has resulted in the failure to generate an internal unique identifier which represents the queue. This is an internal 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.


%QOS-6-RELOAD : [chars], reloading [chars]
Explanation	A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-4-INVALIDBW : interface [chars]: Not enough bandwidth to configure service-policy
Explanation	The issued interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.
Recommended Action	Reconfigure the service policy for the new issued bandwidth on the interface, or increase the issued interface bandwidth to the required value. There is no user action required.


%QOS-6-ACTIVATE : Activating service policy [chars] on [chars] in [chars] direction
Explanation	The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.
Recommended Action	There is no user action required.


%QOS-6-NON_AGG_WRED : ATM SPA doesn't support true non-aggregate WRED. All non-specified dscp/prec values will be aggregated in default WRED profile
Explanation	ATM SPA has limited hardware capability which is not enough to support traditional WRED. ATM SPA would support 'limited' non-aggregate WRED for the specified dscp/prec values (maximum of 6) and the rest non-specified dscp/prec colors will go to default WRED profile.
Recommended Action	There is no user action required.


%QOS-6-ACTIVATE_NOHW : Activating service policy [chars] in [chars] direction
Explanation
Recommended Action


%QOS-3-HA_GET_ARG_NUM : [chars] Failure in getting event identification
Explanation	QoS configuration can't be synced to the standby
Recommended Action	Contact your Cisco technical support representative.


%QOS-3-HA_BULK_SYNC : [chars] Failure in completing bulk sync
Explanation	QoS configuration can't be synced to the standby
Recommended Action	Contact your Cisco technical support representative.


%QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT : [chars] Failure in completing bulk sync before timeout
Explanation	QoS configuration can't be synced to the standby The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.
Recommended Action	Contact your Cisco technical support representative. There is no user action required.


%QOS-3-HA_MISMATCH : Bulk sync failed for [chars] collisions, space available [int], buffer [int]
Explanation	A synchronization attempt between the active and standby RP peers has failed due to the detection of a mismatch in the source and destination sizes of a buffer used in the transport of the collision information to the standby RP. This is an internal 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.


%QOS-3-ISSU_COMP : Failed to exchange capability with peer
Explanation	The attempt to negotiate version capabilities and the exhange of the peer support has failed. This indicates that QoS is unable to support a redundant operation with the standby RP 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.


%QOS-3-MAIN_SUB_POLICY : FR fragmentation is not supported with interface or sub-interface based policies
Explanation	On Cisco 7500 series routers, Frame Relay fragmentation is not supported when service policies are configured on the interface or subinterfaces.
Recommended Action	Remove the service policy configuration under the interface or subinterfaces and reissue either the class command from Frame-Relay DLCI interface configuration mode or the frame-relay fragment command from map-class configuration mode.


%QOS-3-CFGERR : interface [chars]: configuration failed
Explanation	Enough memory is not available to configure feature
Recommended Action	It is not possible to configure issued command (feature) unless required memory is released by some other means


%QOS-3-VTEMP_MLP_ERR : A service policy cannot be attached to a PPP virtual-access interface when ppp multilink is enabled. A service policy can be attached to a ppp multilink bundle interface only.
Explanation	A service policy attached to a virtual-template is usually copied to associated virtual-access interfaces. However, if such a virtual-access interface joins a multilink ppp bundle, the policy is not attached to the virtual-access interface.
Recommended Action	This is informational message. No action is required


%QOS-3-VTEMP_VC_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Explanation	Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action	Remove the policy attached to the vc/pvc before attaching a new policy to a PPP/PPPoE virtual-access interface


%QOS-3-HQF_FEA_API_FAIL : Feature processing API returned NULL pak with INCOMPLETE flag
Explanation	HQF calls feature processing API to get the next packet from the feature, for example Frame-relay fragmentation. The API returns conflicting flags with NULL packet.
Recommended Action	Check if the system resources, e.g. packet buffers, are exhausted. Contact technical support


%QOS-3-VTEMP_SUB_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Explanation	Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action	Remove the policy attached to the subinterface before attaching a new policy to a PPP/PPPoE virtual-access interface


%QOS-3-VTEMP_MAIN_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Explanation	Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action	Remove the policy attached to the main interface before attaching a new policy to a PPP/PPPoE virtual-access interface


%QOS-3-HQFPOOLERR : interface [chars]: failed to allocate hqf particle
Explanation	The HQF particle pool is empty. It cannot process a router generated packet
Recommended Action	Collect show buffer and show policy interface output and send to technical support


%QOS-3-HQFNOPAK : interface [chars]: pak_reparent failed
Explanation	pak_reparent has been invoked and failed.
Recommended Action	Collect show buffer and show policy interface output and send to technical support


%QOS-3-MULTIPLE_INTERFACES : Load-sharing mode has changed. Queuing functionality may not be supported after this.
Explanation	Dynamic interface has changed its route out of different physical interface. It might resolve into multiple interfaces for queuing. HQF functionality will get affected.
Recommended Action	Likely scanario is that CEF is returning multiple paths across different interfaces. For those tunnels which has queuing features need unique out-going interface to resolve queuing hierarchy. Common instance is per-prefix load-balancing to per-destination. Need to remove offending configurations. May also need reload to get the queuing in working state


%QOS-3-ATLEAST_ONE_FAILOVER_ERR : Fail-over of dynamic interface [chars] failed
Explanation	Dynamic interface has changed its route out of different physical interface and queueing can not set-up data-sructures for that new physical interface
Recommended Action	One possibility is that new physical interface already has service-policy or some other dynamic interface already has queueing data-structures associated with that physical interface and conjuction of such service-policies are not allowed. Remove one or the other service-policy in that case. If that is not the case then contact technical support


%QOS-3-HQFPAKREQUEUE : interface [chars]: pak_requeue_head has been invoked
Explanation	pak_requeue_head() function has been invoked on a packet. One or more packets have been dropped. This is not the normal mode of operation
Recommended Action	Collect show buffer and show policy interface output and send to technical support


%QOS-3-INVALID_POLICY : queueing policy at session/tunnel can co-exist only with class-default shaping policy at sub-interface/pvc
Explanation	There already may be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session
Recommended Action	Make sub-interface/pvc based policy just one level policy with only class-default


%QOS-3-COEX_NOT_ALLWD : queueing policy at session cannot co-exist with service policy at sub-interface/pvc
Explanation	There already may be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session
Recommended Action	Remove the policy attached to the sub-interface/pvc before attaching a new policy to a session


%QOS-3-BURST_BC_ERR : Burst Bc increased to [dec] bytes
Explanation	If Burst BC is less than the default burst size then Burst Bc is increased to AF_DEAFULT_BURST
Recommended Action	This is informational message. No action is required


%QOS-3-HQF_QID_ERR : Maximum number of QoS queues ([dec]) reached.
Explanation	The system has run out of QoS queue identifiers and cannot allocate any more until existing queues are freed up.
Recommended Action	Existing QoS configurations will need to be removed to free up more queue identifiers. For example, remove existing QoS service-policy configurations or modify policy-map templates to have fewer queueing actions.


%QOS-4-LC_STATS_MSG_DROPPED : QoS statistics update message dropped due to [chars]
Explanation	Changes to QoS counters are sent periodically from linecards to the route processor. One of these statistics update messages was discarded because it was inconsistent or because the route processor ran out of message buffers. The packet and bytes counters for a single service-policy may be underreported by show commands and SNMP queries.
Recommended Action	This is an informational message only. No action is required.


%QOS-3-XDRLEN : Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[dec]
Explanation	An internal software error occured
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-3-BADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at [hex]
Explanation	An internal software error occured
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-6-NORMAL_BURST_CHANGED_WARN : Illegal normal burst size; it is increased to [int]
Explanation	Configured normal burst size is less than the Rate. It is considered to be illegal and has been reset based on the Rate.
Recommended Action	This is an informational message only. No action is required.


%QOS-6-EXTENDED_BURST_CHANGED_WARN : Illegal extended burst size; it is increased to [int]
Explanation	Configured extended burst size is less than the Rate. It is considered to be illegal and has been reset based on the Rate.
Recommended Action	This is an informational message only. No action is required.


%QOS-4-FO_IN_USE : Releasing feature object with reference count [dec]
Explanation	This is an internal software error. A QoS policy feature object has a stale reference.
Recommended Action	If the message recurs, try to isolate the traffic conditions which trigger the message and contact technical support. Provide the output from the show tech-support and show policy-map interface commands.


%QOS-3-SA_SESSION_FAILOVER_ERR : Fail-over of dynamic SA session to interface [chars] failed
Explanation	Dynamic SA session has changed its route out of different physical interface and queueing can not set-up data-sructures for that new physical interface
Recommended Action	One possibility is that new physical interface already has service-policy with queueing configured Remove the other service-policy in that case. If that is not the case then contact technical support


%QOS-4-DYN_SUSPEND : Queueing hierarchy move failed on [chars], suspending policy.
Explanation	A forwarding path change has moved the given queue to a new port where its QoS queuing policy cannot be satisfied. This is likely due to a conflicting policy or insufficient bandwidth on the new port, or simply that a new port has not yet been calculated. The policy has thus been temporarily suspended.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-6-DYN_INSTALL : Installing suspended policy on [chars].
Explanation	IOS is restoring a previously suspended policy.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%QOS-4-WRED_QLIMIT_OUT_OF_SYNC : On interface [chars] user-defined wred max threshold higher than default queue-limit
Explanation	The user defined random-detect is greater that the default queue-limit for this interface. Some of the random-detect configurations will not function properly due to this anomaly.
Recommended Action	If the random-detect value is configured greater than default queue-limit intentionally then keep it as it is else please investigate and use a random-detect value(s) that will be lower than the default queue-limit.


%QOS-4-HQUEUE_QLIMIT_VALUE_SYNC_ISSUE : The hold-queue value is less than the sum of queue-limit values.
Explanation	The hold-queue value is less than the queue-limit configured. This will lead to no-buffer drops instead of tail drops
Recommended Action	The hold-queue value should be properly adjusted to prevent no-buffer drops.


%QOS-4-QLIMIT_HQUEUE_VALUE_SYNC_ISSUE : The sum of all queue-limit value is greater than the hold-queue value.
Explanation	The hold-queue value is less than the queue-limit configured. This will lead to no-buffer drops instead of tail drops
Recommended Action	The hold-queue value should be properly adjusted to prevent no-buffer drops.


%QOS-6-RADIO_MULTI_REM : Remove [chars] policy before removing policy from ([chars])
Explanation	Prevent the removal of policies from radio layer if child targets have any queuing policies.
Recommended Action	This is an informational message only. No action is required.


%QOS-6-ADAPTIVE_QOS_DISABLED : Adaptive QoS functionality is disabled. Shaper is reset to upper-bound
Explanation	Multiple and consecutive reports from peer are not received. This leads to an assumption that the peer has gone away.
Recommended Action	Removal and re-application of policy may be required to re-enable the adaptive QoS functionality

RAC through RFS

RAC
RADIUS
RADIX
RADPROXY
RCMD
REDUNDANCY
REDUNDANCY_UTILS
REGISTRY
REPLICATE_OCE
RFS

RAC


%RAC-3-RACNOIPL : Can not find lease information for interface [chars]
Explanation	Internal error - DHCP lease information is missing for the interface
Recommended Action	Report the problem and how it can be reproduced to Cisco TAC


%RAC-3-RACNOQ : Can't create RAC work queue
Explanation	Internal error - probable cause is insufficient memory resources
Recommended Action	Check available memory.


%RAC-3-RACIPL : DHCP is already running on interface [chars]
Explanation	The interface already has a DHCP originated address via some other system mechanism
Recommended Action	Verify the system configuration

RADIUS


%RADIUS-3-SERVERTYPEMISMATCH : Servers [chars] and [chars] in server group '[chars]' are of different types.
Explanation	All the servers in a server group should either be of type standard or non-standard.
Recommended Action	Enter `show running-config` command and make sure all the RADIUS servers in the server group printed above are of the same type - either standard or non-standard.


%RADIUS-3-ALLDEADSERVER : Group [chars]: No active radius servers found. Id [dec].
Explanation	This error message occurs when all the servers configured in a server group are found to be unresponsive.
Recommended Action	Check the network connectivity to the RADIUS servers, and check that the servers are running.


%RADIUS-6-RESETDEADSERVER : Group [chars]: Marked alive as Radius server [chars]:[dec],[dec] configured.
Explanation	RADIUS server is now configured in the server group which was previously marked dead.
Recommended Action	No action required. The message is informatory in nature and tells that the dead server is now configured and up.


%RADIUS-6-SERVERALIVE : Group [chars]: Radius server [chars]:[dec],[dec] is responding again (previously dead).
Explanation	A RADIUS server, which previously was dead, has started responding again.
Recommended Action	No action required. This message is informatory in nature and tells that the server has come up and running.


%RADIUS-6-GETROUTES : Retrieving static routes in user [chars]
Explanation	Getting initial static routes from RADIUS, using the given user's profile.
Recommended Action	No action required. The message is informatory in nature and tells that it is getting the static routes based on user's profile.


%RADIUS-6-GETPOOLS : Retrieving IP-Pools via user [chars]
Explanation	Getting initial IP-Pool definitions from RADIUS, using the given user's profile.
Recommended Action	No action required.


%RADIUS-3-NOHOSTNAME : Failed to retrieve my hostname.
Explanation	Could not find the router's hostname. A hostname needs to be defined, since it determines the RADIUS profile we will retrieve.
Recommended Action	Define a hostname on the router's config. Refer to the hostname configuration section of IOS documentation.


%RADIUS-3-FORKFAIL : Failed to fork process for [chars].
Explanation	Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action	If this message recurs, enter `show tech-support` command and call your technical support representative for assistance.


%RADIUS-3-IDENTFAIL : Saving of unique accounting ident aborted. Configuration has been modified.
Explanation	The configuration has been modified. We can not save the unique accounting IDENT to nvram. The message is to inform the user that the saving of unique accounting ident is aborted due to the change in configuration.
Recommended Action	Save the configuration and try again. If the error persists, Enter `show tech-support` contact your Cisco technical support representative, and provide the representative with the gathered information for assistance.


%RADIUS-6-IDENTSAVE : Saving config with new acct ident in nvram.
Explanation	Saving an accounting ident in nvram. The message is informatory.
Recommended Action	No action required.


%RADIUS-3-OVERRUN : Insufficient buffer space [dec] for string value.
Explanation	This error occurs due to the insufficient memory allocated to the buffer. The condition could be caused by a software, less likely by a hardware. The traceback and process information is generated due to this condition.
Recommended Action	If the error re-occurs, check bug toolkit on Cisco web-site to look for a bug that has symptoms similar to the one occured. If there is no entry for the problem you faced, collect the system message text exactly as it appears on the console or in the system log. Enter `show tech-support`, and contact your technical support representative, and provide the representative with all the information gathered.


%RADIUS-3-NOSERVERS : No Radius hosts configured or no valid server present in the server group [chars]
Explanation	RADIUS is attempting to send a request, but there are no hosts configured to which the request is send.
Recommended Action	Configure a host with the 'radius-server' command providing the IP address of the server. Refer to the radius-server host configuration section of IOS documentation.


%RADIUS-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation	The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved.
Recommended Action	Configure a proper secret. Refer to the shared secret configuration section for RADIUS servers in IOS documentation.


%RADIUS-3-FORMATLONG : Format string too long.Maximum allowed length is [dec].
Explanation	The user is attempting to configure a format string with a prefix that is too long.
Recommended Action	Enter a shorter string to configure.


%RADIUS-4-NOSERV : Warning: Server [chars]:[dec],[dec] is not defined.
Explanation	The given server is not globally defined, please define it.
Recommended Action	Please define the server. Refer to the server configuration section of IOS documentation.


%RADIUS-4-NOSERVNAME : Warning: Server [chars] is not defined.
Explanation	The given server name is not globally defined, please define it.
Recommended Action	Please define the server. Refer to the new server name configuration section of IOS documentation.


%RADIUS-4-SERVREF : Warning: Server [chars]:[dec],[dec] is still referenced by server group.
Explanation	The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists.
Recommended Action	Please dereference the server from the server group as soon as possible. Refer to server group configuration section in IOS documentation.


%RADIUS-4-SERVREFNAME : Warning: Server %S is still referenced by server group.
Explanation	The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists.
Recommended Action	Please dereference the server from the server group as soon as possible. Refer to server group configuration section in IOS documentation.


%RADIUS-3-NOATTRLIST : No attribute-list passed through parser.
Explanation	An internal error has occurred. The reason could be hardware or software. The error appears when no attribute list is passed through the parser.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RADIUS-3-INVALIDFORMAT : Invalid Nas Port Format: [chars] %c
Explanation	The user is attempting to configure an incorrect format string.
Recommended Action	Enter a 32 character string using supported characters only.


%RADIUS-4-BADATTRLIST : Unable to process attribute list.
Explanation	The attribute list is syntactically incorrect.
Recommended Action	Please specify the attribute list as a comma- delimited string of integers between 1 and 255.


%RADIUS-4-NOATTRLISTDEF : Warning: Attribute list [chars] is not defined.
Explanation	The given attribute list is not defined.
Recommended Action	Please define the attribute list as soon as possible.


%RADIUS-3-DATAERROR : Warning: [chars]
Explanation	The given data passed into the Radius subsystem is considered invalid and may result in loss of attributes.
Recommended Action	Please collect traceback and contact your technical support representative.


%RADIUS-3-SOURCEPORTALLOCERROR : Warning: Unable to allocate port [dec]
Explanation	Unable to allocate a certain port, will not have the full range of source ports. This is not supposed to happen, contact support.
Recommended Action	Contact support


%RADIUS-3-CORRUPTCONTEXT : Bad Magic pattern in [chars]:[hex], magic:[hex]!
Explanation	The magic pattern imprinted on the internal hash table data structures in RADIUS subsystem is missing and indicates memory corruption. The memory is getting overwritten by a misbehaving process. The traceback and the process information is generated to the result of the error.
Recommended Action	Check bug toolkit on Cisco web-site to look for a bug that has symptoms similar to the one occured. If there is no entry for the problem you faced, collect the system message text exactly as it appears on the console or in the system log. Enter `show tech-support` command, contact your technical support representative and provide the representative with the gathered information.


%RADIUS-3-UNKNOWNAPI : Unknown API type [dec]
Explanation	RADIUS code has been invoked using an unknown API type. This is the result of a bug in the RADIUS subsystem.
Recommended Action	Check bug toolkit on Cisco web-site to look for a bug which has symptoms similar to the one occured. If there is no entry for the problem you faced, Please collect traceback and contact your technical support representative.


%RADIUS-3-ZEROATTRLEN : Radius attr [dec] len 0
Explanation	An internal error 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.


%RADIUS-3-BUFFER_OVERFLOW : Radius I/O buffer has overflowed
Explanation	An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer.The given server is not on the global public servers list. This is an internal consistency error
Recommended Action	This is an internal software error. Collect the trace-back appeared as a part of message and report it to your technical support representative.Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RADIUS-3-NOACCOUNTINGRESPONSE : Accounting message [chars] for session %*s failed to receive Accounting Response.
Explanation	Maximum number of retransmissions is exceeded. The network is not accessible or the RADIUS server is down.
Recommended Action	Check the network connectivity to the RADIUS servers, and check that the servers are running. If not able to debug the issue, enter `show running-config` and contact your technical support representative for assistance.


%RADIUS-3-CANNOT_OPEN_SOCKET : Cannot open UDP socket for service [chars]
Explanation	The router is unable to open a socket for UDP communications by the indicated service. Most of the time another service might be using the same port.
Recommended Action	Check your configuration to make sure that no other services are using the same port. If not able to debug the issue, enter `show running-config` and contact your technical support representative for assistance.


%RADIUS-4-NOPUBLICSERV : Warning: No servers were found in the public server list.
Explanation	The given server is not on the global public servers list. This is an internal consistency 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.


%RADIUS-4-RADIUS_DEAD : RADIUS server [chars]:[int],[int] is not responding.
Explanation	The server might not be available to serve request. server has not responded to repeated requests.
Recommended Action	Check for the connectivity to server. Check if the RADIUS server is still active. If not able to debug the issue, enter `show running-config` and contact your technical support representative for assistance.


%RADIUS-4-RADIUS_ALIVE : RADIUS server [chars]:[int],[int] is being marked alive.
Explanation	A RADIUS server that previously was not responding has responded to a new request or the deadtimer has expired.
Recommended Action	No action is required.


%RADIUS-3-MALLOC_FAILED : Insufficient memory : [chars].
Explanation	Memory allocation failed due to insufficient memory
Recommended Action	No action is required.


%RADIUS-3-IPV4_FIB_SEND_FAILED : Radius ipv4 send failed due to FIB error. Error code: [dec].
Explanation	Radius not able to send udp packets as fib failed
Recommended Action	No action is required.


%RADIUS-3-INVALID_PACKET : Invalid packet posted to RADIUS.
Explanation	Radius not able to process a packet as it in invalid
Recommended Action	No action is required.

RADIX


%RADIX-3-NOMEMORY : No memory available [chars]
Explanation	The system is out of memory.
Recommended Action	Try one of these actions to correct the problem: Reduce the number of routes accepted by this router. Upgrade hardware. Use a smaller subset image on run-from-RAM platforms.


%RADIX-3-DELETE : Error deleting trie entry, [chars]
Explanation	A software programming error occurred.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%RADIX-3-ADDMASK : Error adding mask entry, [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.


%RADIX-3-BADTREE : Invalid pointer to head of tree, [hex]
Explanation	A software programming error occurred.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%RADIX-4-ORPHAN : Orphaned mask [hex], refcount=[dec] at [hex], next=[hex]
Explanation	A software error occurred.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%RADIX-2-INIT : No memory for radix initialization: [chars]
Explanation	The system ran out of memory during initialization. This should only occur if an image is too large for the existing dynamic memory.
Recommended Action	Use a smaller subset image or upgrade hardware.

RADPROXY


%RADPROXY-3-NULL_FSM_CONTEXT : Encountered a NULL RP context in [chars]
Explanation	Encountered a NULL context in 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.


%RADPROXY-3-INVALID_FSM_STATE : Encountered an invalid RP state [dec] in [chars]
Explanation	An internal RP 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.


%RADPROXY-3-INVALID_FSM_EVENT : Received invalid RP event [chars] in state [chars]
Explanation	An internal RP 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.


%RADPROXY-3-INIT : Initialisation failure, [chars]
Explanation	An internal error occurred during RP initialisation.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RADPROXY-3-MEMORY_CORRUPT : RP Memory magic corrupted
Explanation	RP memory magic corrupted
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RADPROXY-3-INVALID_MAC : Received invalid MAC [chars] in [chars] from [IP_address] with NAS-IP [IP_address]
Explanation	Error occurred on receiving a invalid MAC
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RADPROXY-3-MEMORY_LOW : Memory low in RP, terminating session
Explanation	System memory is running low.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RADPROXY-3-PROTOCOL_VIOLATION : RP encountered fatal protocol violation
Explanation	Unrecoverable protocol 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.

RCMD


%RCMD-4-RCPATTEMPTED : Remote copy from [chars] at [chars] denied
Explanation	An attempt was made to connect to a router through RCP, but the router was not configured as an RCP server.
Recommended Action	Configure an RCP server.


%RCMD-4-RSHATTEMPTED : Remote shell from [chars] at [chars] denied
Explanation	An attempt was made to connect to a router through rsh, but the router was not configured as an rsh server.
Recommended Action	Configure an rsh server.


%RCMD-4-RCMDDNSFAIL : DNS hostname/ip address mismatch. [chars] unknown to DNS
Explanation	The IP address for an incoming rcmd request is not registered with DNS.
Recommended Action	Add the IP address to DNS.

REDUNDANCY


%REDUNDANCY-3-IPC : [chars] [chars]
Explanation	An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-MEMORY_DIFF : WARNING, nonsymetrical configuration: Active has [dec]K Standby has [dec]K
Explanation	The redundant RPs have different memory configurations.
Recommended Action	The configuation is allowed but discouraged.


%REDUNDANCY-3-FSM : [chars]
Explanation	A REDUNDANCY Finite State Machine (FSM) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-FSM_ERROR : [chars], Error Code: [dec]
Explanation	A REDUNDANCY Finite State Machine (FSM) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-SWITCHOVER : RP switchover ([chars])
Explanation	A REDUNDANCY switchover has occurred.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-STANDBY_LOST : Standby processor fault ([chars])
Explanation	The standby processor is no longer available.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-PEER_MONITOR : [chars]
Explanation	A REDUNDANCY Peer Monitor error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-5-PEER_MONITOR_EVENT : [chars] ([chars][chars]([dec]))
Explanation	A REDUNDANCY Peer Monitor event occurred and reported. The report should help to find out the reason for a switch-over.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-REDUNDANCY_ALARMS : [chars]
Explanation	A REDUNDANCY Alarm assertions error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-CONFIG_SYNC : [chars]
Explanation	A REDUNDANCY config sync error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-3-GENERAL : [chars]
Explanation	A REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.


%REDUNDANCY-4-RELOADING_STANDBY : Reloading the Standby [chars]
Explanation	The Active has sent a reload IPC request to the Standby peer. If the reload is not successful then the Standby will be power cycled instead.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%REDUNDANCY-4-PEER_DID_NOT_RESPOND : Resetting peer [chars] because it did not respond to verification of HA role.
Explanation	The platform uses the HA hardware lines to perform HA role negotiation at boot time. Whichever controller card becomes the Standby verifies this role via the MBUS with the Active. If the Active does not respond it is reset as it is either hung, or is running an old version of software.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%REDUNDANCY-6-STANDBY_HAS_RELOADED : The Standby [chars] has reloaded; reason: [chars]
Explanation	The Standby peer has reloaded itself to correct a configuration mismatch between the Active and the Standby. The Standby has detected that it is missing configuration for a line card. This has most likely happened because the Standby was reloaded prior to the new card being inserted.
Recommended Action	No action is required.


%REDUNDANCY-6-SWITCHOVERTIME : Time taken to switchover = [dec] milliseconds
Explanation	This is how long the Standby peer took to become Active after a failure of the existing Active.
Recommended Action	No action is required.


%REDUNDANCY-3-EHSAISSU : [chars] failed with error code [ [chars] ]
Explanation	An ISSU related REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action	Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.

REDUNDANCY_UTILS


%REDUNDANCY_UTILS-3-INVALID_UNIT_DESIGNATION : An invalid redundancy designation ([chars]) has been detected.
Explanation	The redundancy utility assigns each system a unit designation of either an Active Unit, Standby Unit, or Other Unit, and this designation was found to be invalid in the run-time module associated with the system traceback message. This condition most likely occurred because of a software error. The message text provides more information on the specific nature of the 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.

REGISTRY


%REGISTRY-3-SEQ_LIST_OVERWRITE : Attempt made to overwrite a set sequence function ([chars])
Explanation	A single function can be set as a callback for a specified sequence number for a sequenced list registry. This message indicates that an attempt to set a new callback has failed because a callback function has already been set for this sequence number.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%REGISTRY-3-STUB_CHK_OVERWRITE : Attempt made to overwrite a set stub function in [chars].
Explanation	A single function can be set as a callback for when a stub w/ check registry is invoked. This message indicates that an attempt to set a new callback has failed because a callback function has already been set.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%REGISTRY-3-FASTCASE_OUT_OF_BOUNDS : Attempt made in [chars] to register with out of bounds key.
Explanation	In FASTCASE registry the key has to be smaller than the size specified when the registry was created. This message indicates that an attempt was made to register with a key out of bounds.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%REGISTRY-3-REG_SUSPEND : Registry of type SUSPEND called when suspends are not allowed.
Explanation	When process blocking has been disabled either using raise_interrupt_level or assign_blocking_disabled, a remote registry of type SUSPEND has been invoked.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%REGISTRY-3-REG_FLAG_ERR : Invalid combination of registry flag and scheduler control : [chars]
Explanation	When process blocking has been disabled either using raise_interrupt_level or assign_blocking_disabled, a remote registry with flags REG_FLAG_DATA_SAFE/REG_FLAG_PEER has been invoked.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%REGISTRY-2-REG_FLAG_DEADLOCK : Registry call to [chars] timed out due to deadlock
Explanation	When a remote registry is not serviced within 25 seconds, the remote process (and presumably the entire system) is deadlocked. This message is printed when the deadlock is broken by a timeout
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%REGISTRY-2-REG_PARSE_ERROR : [chars]: Could not parse notification [chars] : error/no. of items = [dec]
Explanation	Registry library is unable to parse notification received from name server. This could be for several reasons: a) There is a bug in sscanf b) The notification block is corrupted c) The pathname published to the name server is invalid This is a serious issue that affects inter-process communication.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.


%REGISTRY-3-REG_XDR : [chars]
Explanation	There was an error while marshalling a parameter to a remote (inter-process) registry call
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

REPLICATE_OCE


%REPLICATE_OCE-3-NETWORK_GET_FAIL : MPLS Multicast can not get network offset: datagram [hex]; network [hex]
Explanation	MPLS failed to find a suitable packet network offset
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%REPLICATE_OCE-3-NETWORK_SET_FAIL : MPLS Multicast can not set network offset: datagram [hex]; length [dec]; offset [dec]
Explanation	MPLS failed to set offset within packet
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%REPLICATE_OCE-6-PAK_TOO_SHORT : Packet too short, datagram size [dec], tl [dec]
Explanation	An IP packet which is too short was received
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%REPLICATE_OCE-3-REPLICATE_PATH_WALK_FAIL : [chars] [dec]
Explanation	Replicate path walk 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.


%REPLICATE_OCE-3-REPLICATE_INIT_INSUFFICIENT_PARTICLE_SIZE : Platform particle size [dec] may be insufficient for Label Switched multicast; Minimum particle size recommended is [dec]; Replicate packets may not be forwarded
Explanation	LSM Replicated packets may not be forwarded.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

RFS


%RFS-3-CLIENT_REG : RFS Client ([dec]) Registration failed
Explanation	RFS ISSU client registration failed
Recommended Action	Enter the following command:'show issu client' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why no uid with this value found registered in ISSU Database


%RFS-3-ENTITY_REG : RFS Entity ([dec]) Registration failed
Explanation	RFS ISSU entity failed to register with ISSU
Recommended Action	Enter the following command:'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this entity failed to register


%RFS-3-MSGTYPE_REG : RFS Msg Type for Entity ([dec]) Registration failed
Explanation	RFS ISSU Msg Type registration failed
Recommended Action	Enter the following commands: 'show issu entities', 'show issu message types' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this message types failed to register


%RFS-3-MSGGROUP_REG : RFS Msg Group ([dec]) for Entity ([dec]) Registration failed
Explanation	RFS ISSU Msg Group registration failed
Recommended Action	Enter the following commands: 'show issu message groups', and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this message group failed to register


%RFS-3-CAPTYPE_REG : RFS Cap Type for Entity ([dec]) Registration failed
Explanation	RFS ISSU Cap Type registration failed
Recommended Action	Enter the following commands: 'show issu capability types' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this capability type failed to register


%RFS-3-CAPENTRY_REG : RFS Cap Entry ([dec]) for Entity ([dec]) Registration failed
Explanation	RFS ISSU Cap Entry registration failed
Recommended Action	Enter the following commands: show issu capability entries and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this capability entry failed to register


%RFS-3-CAPGROUP_REG : RFS Cap Group ([dec]) for Entity ([dec]) Registration failed
Explanation	RFS ISSU Cap Group registration failed
Recommended Action	Enter the following commands: show issu capability groups and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this capability group failed to register


%RFS-3-CLIENT_SESSION_REG : RFS ISSU client shared msg session for entity ([dec]) registration failed
Explanation	RFS ISSU client shared msg session registration failed
Recommended Action	Enter the following commands: show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this shared message session failed to register


%RFS-3-CLIENT_SESSION_UNREG : RFS session ([dec]) Un-Registration failed
Explanation	RFS ISSU client session un-registration failed
Recommended Action	Enter the following commands: show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client session failed to un-register


%RFS-3-NEGO_SESSION_REG : RFS nego session for Entity ([dec]) Registration failed
Explanation	RFS ISSU shared nego session registration failed
Recommended Action	Enter the following commands: 'show issu sessions', 'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session failed to register


%RFS-3-NEGO_SESSION_UNREG : RFS session ([dec]) Un-Registration failed
Explanation	RFS ISSU shared nego session un-registration failed
Recommended Action	Enter the following commands: 'show issu sessions' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session failed to un-register


%RFS-3-START_NEGO_SESSION : RFS nego ([dec]:[dec]) to [[chars]:[hex]] failed: [[chars]]
Explanation	RFS ISSU start shared nego session failed
Recommended Action	Enter the following commands: 'show issu sessions' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session failed to start


%RFS-3-NEGO_COMP : RFS nego is not compatible ([dec])
Explanation	RFS ISSU start shared nego session failed
Recommended Action	Enter the following commands: 'show issu sessions' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session is not compatible


%RFS-3-SEND_NEGO_MESSAGE : RFS send nego message ([IPV6 address]) failed
Explanation	RFS ISSU send nego message failed
Recommended Action	Enter the following commands: 'show issu session' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation message failed


%RFS-3-RECEIVE_NEGO_FAILED : RFS receive nego message ([IPV6 address]) failed
Explanation	RFS ISSU receive nego message failed
Recommended Action	Enter the following commands: 'show issu session' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation message failed


%RFS-3-RECEIVE_NEGO_NOT_DONE : RFS receive nego message is not done ([dec])
Explanation	RFS ISSU receive nego message is not done
Recommended Action	Enter the following commands: show issu session and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation failed to complete


%RFS-3-IPC_GET_BUFFER : RFS issu ipc get buffer failed
Explanation	RFS ISSU ipc get buffer failed
Recommended Action	Enter the following commands:'show proc mem' or 'show buffs' to check if memory or buffer is full. shutdown unused tasks or reset cards usually can recover those memory leak problem. Copy the error and send it to TAC if those actions do not help.


%RFS-3-REG_PORT : RFS reg port ([dec]) failed
Explanation	RFS ISSU reg port failed
Recommended Action	Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this port failed to register


%RFS-3-LOCATE_PORT : RFS locates port ([chars]) failed
Explanation	RFS ISSU locates port failed
Recommended Action	Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be located


%RFS-3-OPEN_CLIENT_PORT : RFS open client port ([chars]) failed. Reason:[chars]
Explanation	RFS ISSU open client port failed
Recommended Action	Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be opened


%RFS-3-OPEN_SERVER_PORT : RFS open server port ([chars]) failed
Explanation	RFS ISSU open server port failed
Recommended Action	Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be opened


%RFS-3-CREATE_CLIENT_PORT : RFS create client port ([chars]) failed
Explanation	RFS ISSU create client port failed
Recommended Action	Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be created


%RFS-3-CREATE_SERVER_PORT : RFS create server port ([chars]) failed
Explanation	RFS ISSU create server port failed
Recommended Action	Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be created


%RFS-3-RFS_ISSU_START_SESSION : RFS create rfs_issu_start_session watch boolean failed
Explanation	RFS ISSU create rfs_issu_start_session watch boolean failed
Recommended Action	Copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be created


%RFS-3-RFS_ISSU_START_PORT : RFS create rfs_issu_start_port watch boolean failed
Explanation	RFS ISSU create rfs_issu_start_port watch boolean failed
Recommended Action	Enter the following commands:show proc mem and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this watched boolean could not be created


%RFS-3-RFS_ISSU_NEGO_PROCESS : RFS create rfs_issu_start_port watch boolean failed
Explanation	RFS ISSU create nego process failed
Recommended Action	Enter the following commands:show proc mem and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this watched boolean could not be created


%RFS-3-MSG_MTU : RFS Client ([dec]) get msg mtu failed. Error = [dec]
Explanation	RFS ISSU client get msg mtu failed
Recommended Action	Enter the following commands: show issu fsm, show issu ses and copy the error and send it to TAC. TAC team can contact the file-systems team to check why get message mtu failed


%RFS-3-MSG_XMIT : RFS Client ([dec]) on session ([dec]) to seat [[hex]] failed send transformation with error[[chars]]
Explanation	RFS ISSU client send msg failed
Recommended Action	Enter the following commands:show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why send message for this client failed


%RFS-3-MSG_RCV : RFS Client ([dec]) on session ([dec]) to seat [[hex]] failed receive transformation with error[[chars]]
Explanation	RFS ISSU client receive msg failed
Recommended Action	Enter the following commands:show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why receive message for this client failed


%RFS-3-UNREG_ENTITY : RFS ISSU Client unreg entity failed.
Explanation	RFS ISSU client unreg entity failed
Recommended Action	Enter the following command:'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this entity failed to un-register


%RFS-3-RFS_ISSU_CLIENT_OR_ENTITY_ID : RFS ISSU couldnt find client/entity id in peer.
Explanation	RFS ISSU couldnt find client/entity id in peer.
Recommended Action	Enter the following command:'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client/entity id coudlnt find in peer


%RFS-3-MSG_GET_NEGO_VER : RFS Client ([dec]) get msg negotiated version failed. Error = [dec]
Explanation	RFS ISSU client get msg negotiated version failed
Recommended Action	Enter the following commands: show issu fsm, show issu ses and copy the error and send it to TAC. TAC team can contact the file-systems team to check why get message negotiated version failed


%RFS-3-MSG_INCOMP : [chars](): msg_type [[dec]] under session [[dec]] is incompatible
Explanation	The message types are incompatible under ISSU
Recommended Action	Enter the following command: show issu message types 110 and copy the output and send it to TAC. TAC team can contact the file-systems team to check why messages are incompatible


%RFS-3-RFS_RF_PROG_ERR : Failed to send the bulk sync notification done. Error ([dec]).
Explanation	The RFS RF client failed to send the final bulk sync otification.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RFS-3-RFS_RF_PROG_NOT_SENT_ERR : [chars].
Explanation	The RFS RF client has error in sending client progression.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RFS-3-RFS_BOOL_CREATE_ERR : [chars].
Explanation	The RFS RF client has error in creating watched boolean.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

RG_AR through RPL

RG_AR
RG_FAULTS
RG_MEDIA
RG_PROTOCOL
RG_TRANSPORT
RG_VP
RMON
ROLLBACK_ISSU
ROUTEMAP
RPL

RG_AR


%RG_AR-3-NOPROCESS : Unable to create process for [chars].
Explanation	Quite likely, we ran out of memory. Other explanations are possible.;msgdef_recommended_action(If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.
Recommended Action	If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.


%RG_AR-3-NOPEER : Peer does not exist for RG ID = ([dec]) with error code = ([dec])
Explanation	Failures in communication with peer
Recommended Action	Make sure that there are no configuration errors.

RG_FAULTS


%RG_FAULTS-6-PRICHANGE : RG Infra RG[[dec]] Priority update. new priority [[dec]] old priority [[dec]] [chars]
Explanation	The runtime priority of the group was updated
Recommended Action	Look at rg_infra trace for the cause for priority change


%RG_FAULTS-6-PRICONFCHANGE : RG Infra RG[[dec]] Priority configuration changed. New runtime priority:[[dec]]
Explanation	The configured priority changed, runtime priority was affected
Recommended Action	No action need to be taken


%RG_FAULTS-3-NOPROCESS : Unable to create a new process for [chars].
Explanation	Quite likely, we ran out of memory. Other explanations are possible.;msgdef_recommended_action(If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.
Recommended Action	If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.

RG_MEDIA


%RG_MEDIA-3-NOPROCESS : Unable to create process for [chars].
Explanation	Quite likely, we ran out of memory. Other explanations are possible.;msgdef_recommended_action(If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.
Recommended Action	If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.


%RG_MEDIA-3-NOSOCKET : Unable to open socket
Explanation	The system was unable to initialize an IP connection for RG Protocol
Recommended Action	Make sure that there is at least one interface configured to run IP.


%RG_MEDIA-4-BADSEQ : Group [dec]: Sequence number larger than expected - indicates packet loss
Explanation	Sequence number expected from peer is too big, this usually indicates packet loss
Recommended Action	Check for connectivity problems between the 2 peers.


%RG_MEDIA-3-INVALIDPLATFORM : Unsupported Platform
Explanation	The peer platform is unsupported as a RG-pair
Recommended Action	Only like platforms can be configured as a RG pair.


%RG_MEDIA-3-TIMEREXPIRED : RG id [dec] Hello Timer Expired.
Explanation	This router did not receive hello message from the peer within the configured hold time. This may result in a role change.
Recommended Action	Enter `show tech-support`, `show history` commands, collect all the information and error message and report it to your technical support representative.

RG_PROTOCOL


%RG_PROTOCOL-3-NOPROCESS : Unable to create process for [chars].
Explanation	Quite likely, we ran out of memory. Other explanations are possible.;msgdef_recommended_action(If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.
Recommended Action	If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.


%RG_PROTOCOL-5-ROLECHANGE : RG id [dec] role change from [chars] to [chars]
Explanation	RG role (Init/Standby/Active) has been changed
Recommended Action	No action is required.


%RG_PROTOCOL-3-UNEXPECTEDACTIVE : RG id [dec] unexpected Active peer [IP_address]
Explanation	An unexpected Active peer has been detected via control interface; there are 2 Active RGs in the redundancy group
Recommended Action	If this is not a transient state, check for connectivity problems or inconsistency of rg protocol timer configuration between the peers


%RG_PROTOCOL-4-UNEXPECTEDSTANDBY : RG id [dec] unexpected Standby peer [IP_address]
Explanation	An unexpected Standby peer has been detected via control interface; there are 2 Standby RGs in the redundancy group
Recommended Action	If this is not a transient state, check for connectivity problems or inconsistency of rg protocol timer configuration between the peers

RG_TRANSPORT


%RG_TRANSPORT-3-NOPROCESS : Unable to create process for [chars].
Explanation	Quite likely, we ran out of memory. Other explanations are possible.;msgdef_recommended_action(If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.
Recommended Action	If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.


%RG_TRANSPORT-3-TRANSFAIL : Negotiation failure with error code: [dec]
Explanation	The query_status in msg is not RG_TRANS_SUCCESS
Recommended Action	Make sure that there are no configuration errors.

RG_VP


%RG_VP-3-NOPROCESS : Unable to create process for [chars].
Explanation	Quite likely, we ran out of memory. Other explanations are possible.;msgdef_recommended_action(If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.
Recommended Action	If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter `Show tech-support` command, collect all the information and error message and report it to your technical support representative.


%RG_VP-6-STANDBY_READY : RG group [dec] Standby router is in SSO state
Explanation	Indicates standby readiness
Recommended Action	No action is required.


%RG_VP-6-BULK_SYNC_DONE : RG group [dec] BULK SYNC to standby complete.
Explanation	Indicagtes Standby bulk sync complete
Recommended Action	No action is required.

RMON


%RMON-5-RISINGTRAP : Rising threshold has been crossed because the value of [chars] exceeded the rising-threshold value [dec]
Explanation	A Rising Event will be generated.The value of the specified MIB object has exceeded the rising threshold value as configured by the `rmon alarm` command for the specified object
Recommended Action	Take appropriate action on the specified object.


%RMON-5-FALLINGTRAP : Falling threshold has been crossed because the value of [chars] has fallen below the falling-threshold value [dec]
Explanation	A Falling Event will be generated.The value of the specified MIB object has fallen below the falling threshold value as configured by the `rmon alarm` command for the specified object
Recommended Action	Take appropriate action on the specified MIB object.


%RMON-5-HCRISINGTRAP : Rising trap is generated because the value of [chars] exceeded therising-threshold hc value [int]
Explanation	A Rising Trap has been generated.The value of the specified MIB object has exceeded the rising threshold value as configured by the `rmon hc-alarms` command for the specified object
Recommended Action	Take appropriate action on the specified object.


%RMON-5-HCFALLINGTRAP : Falling trap is generated because the value of [chars] has fallen belowthe falling-threshold hc value [int]
Explanation	A Falling Trap has been generated.The value of the specified MIB object has fallen below the falling threshold value as configured by the `rmon hc-alarms` command for the specified object
Recommended Action	Take appropriate action on the specified MIB object.

ROLLBACK_ISSU


%ROLLBACK_ISSU-2-INIT : Rollback ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation	The Rollback 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.


%ROLLBACK_ISSU-3-TRANSFORM_FAIL : Rollback ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation	The Rollback 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 Rollback 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>)


%ROLLBACK_ISSU-3-MSG_NOT_OK : Rollback ISSU client 'Message Type [dec]' is not compatible
Explanation	The Rollback 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>)


%ROLLBACK_ISSU-3-MSG_SIZE : Rollback ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation	The Rollback ISSU client failed to calculate the MTU for the specified message. The Rollback 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>)


%ROLLBACK_ISSU-3-INVALID_SESSION : Rollback ISSU client does not have a valid registered session.
Explanation	The Rollback 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>)


%ROLLBACK_ISSU-2-SESSION_REGISTRY : Rollback ISSU client failed to register session information. Error: [dec] ([chars])
Explanation	The Rollback 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>)


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


%ROLLBACK_ISSU-2-SESSION_NEGO_FAIL_START : Failed to start Rollback ISSU session negotiation. Error: [dec] ([chars])
Explanation	The Rollback ISSU client failed to start session negotition. If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.
Recommended Action	LOG_STD_SH_CMD_ACTION( show issu session <client_id>)


%ROLLBACK_ISSU-2-SEND_NEGO_FAILED : Rollback ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation	The Rollback 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)


%ROLLBACK_ISSU-2-GET_BUFFER : Rollback ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation	The Rollback 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)

ROUTEMAP


%ROUTEMAP-4-BADTRACKOBJECTTYPE : can't track this type of object
Explanation	Route maps only support STATE type track objects. This object is not a STATE object
Recommended Action	Reconfigure the track object to make it a STATE object.

RPL


%RPL-3-CONFIG_ERROR : RPL [chars] configuration failed: [chars] [chars] code [dec]
Explanation	This Error message would be encountered when trying to configure rpl through api.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RPL-3-CHUNK_ERROR : [chars]
Explanation	This Error message would be encountered when trying to 1. access chunk or chunk element when they are not valid. 2. lock failure on chunk element.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%RPL-3-MALFORMEDMSG : Malformed [chars] received from: [IPV6 address]
Explanation	This Error message would be encountered if a malformed RPL Control message is received
Recommended Action	Informational

Was this Document Helpful?

Feedback

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)