System Error Messages Guide For Access and Edge Routers, Cisco IOS XE Gibraltar 16.10.1

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:
July 5, 2019

Chapter: MX through SBC_HA

MX through SBC_HA

MX through NETWORK_CLOCK_SYNCHRONIZATION

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

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


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 through OLM

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

%NIF_MGR-6-PORT_CONN_READY : Port [dec] 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 : Port [dec] 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 : Port [dec] 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 : Port [dec] 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 : Port [dec] 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 : Port [dec] 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 : Port [dec] 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 lpn:[dec] 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.


NMSP_SYSLOG

%NMSP_SYSLOG-5-NMSP_SSL_NOTICE : nmspd TLS notice: [chars]
Explanation This is an informational message.
Recommended Action No action required.


%NMSP_SYSLOG-3-NMSP_SSL_ERROR_DISCONNECT : nmspd TLS disconnection: [chars]
Explanation Remote CMX connection over TLS protocol had been dropped.
Recommended Action Check connectivity with CMX, CMX service status and AAA configuration.


%NMSP_SYSLOG-3-NMSP_SSL_ERROR_INTERNAL : nmspd internal error occured when handling TLS connection: [chars]
Explanation Internal eWLC error prevented successful establishment of CMX connection over TLS protocol
Recommended Action Check availability of the system resources of the eWLC controller: memory, open files, sockets. Contact TAC if issue persists


%NMSP_SYSLOG-3-NMSP_SSL_ERROR_CERT : nmspd TLS certificate error: [chars]
Explanation Error validating TLS certificate for incoming CMX connection
Recommended Action Check that certificates and SHA2 key are properly setup on eWLC. Contact TAC if issue persists.


%NMSP_SYSLOG-5-NMSP_HTTPS_NOTICE : nmspd HTTPS info: [chars]
Explanation This is an informational message.
Recommended Action No action required.


%NMSP_SYSLOG-5-NMSP_HTTPS_INTERFACE_NOTICE : nmspd HTTPS info: [chars]
Explanation Wireless management interface notification.
Recommended Action No action required.


%NMSP_SYSLOG-3-NMSP_HTTPS_ERROR_CRYPTO : nmspd HTTPS error: [chars]
Explanation Peer verification of CMX cloud service failed.
Recommended Action Check that server certificate can be verified by root CA certificates in trustpool of crypto PKI.


%NMSP_SYSLOG-3-NMSP_HTTPS_ERROR_CONFIG : nmspd cloud service config error: [chars]
Explanation Configuration error prevented successful connection to CMX cloud service.
Recommended Action Check configuration of cmx cloud service, e.g. server URL and token.


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 through PA_PKT

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

%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 through PERF_TRAFFIC_REACT

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

%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 through PLATFORM_POWER

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.