-
Cisco IOS XR System Error Message Reference Guide, Release 3.5
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Layer 3 Messages
-
Manageability (MGBL) Messages
-
Media Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
System Database Messages
-
Feedback
Table Of Contents
Packet Infrastructure Messages
C12000_FWD_CLIENT_DLL Messages
PLATFORM_C12000_NETIO_LIB Messages
PLATFORM_HFR_NETIO_LIB Messages
PLATFORM_LPTS_COM_IFIB Messages
PLATFORM_LPTS_COM_NETIO Messages
Packet Infrastructure Messages
This section contains all Packet Infrastructure related System Error Messages, including ifmgr, tunnels, bundlemgr, pakman, and so forth. The following facility codes are represented in this module:
•
C12000_FWD_CLIENT_DLL Messages
•
•
•
•
AIB Messages
Error Message%PKT_INFRA-AIB-1-EVENTBLOCK event_block returned early : [chars] (errno=[dec])
Explanation An unexpected or erroneous return while waiting for events.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-AIB-4-INDEX_REG_FAIL AIB process cannot register with the platform specific DLL (return=[dec])
Explanation The AIB process cannot register with the platform specific adjacency index DLL. The adjacency database will not be created.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-AIB-4-INDEX_VERSION_FAIL AIB process has detected a version mismatch between itself and the platform DLL (DLL version is [dec], AIB expected [dec])
Explanation The AIB process has detected that the platform specific adjacency indexing DLL has reported a version number that does not match the AIB process version number. Due to this inconsistency, the AIB cannot continue and the system will not be able to process any adjacency information.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-AIB-4-LTRACE_ERROR Failed to open trace file: [chars]
Explanation The AIB process was unable to open the trace buffer for automatic tracing (show trace adjacency may not work).
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-AIB-4-RADIXINIT_FAIL AIB failed to initialize the interface db radix tree ([chars])
Explanation Initialization of the radix tree could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-AIB-4-SHM_FAIL AIB Shared memory error: [chars] [chars]
Explanation The AIB process received an error while trying to initialize the shared memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-AIB-4-SYSTEM_FAIL [chars] [chars] (errno=[dec])
Explanation There was a system call failure resulting in a failure to provide a system service as indicated in the message text.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
BFM_API Messages
Error Message%PKT_INFRA-BFM_API-3-FATAL bfm: fatal error encountered, reason=[chars]
Explanation iq manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-FATAL_2 bfm: fatal error encountered, reason=[chars], errno=[dec]
Explanation bfm encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-GEN_INFO bfm: general information, [chars]
Explanation The BFM's informational message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-INFO bfm: service degrading error, reason = [chars]
Explanation The bfm encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-MALLOC_FAILED BFM: fatal memory allocation error for [dec] bytes
Explanation BFM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-BFM_API-3-NOT_YET_IMPLEMENTED bfm: this function [chars] is not yet implemented
Explanation BFM, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-USAGE bfm: invalid option [chars] passed to bfm server
Explanation Startup option supplied to BFM is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-4-PTCL_TYPE_WRONG BFM: ptcl type [chars] is not as expected type is [chars]
Explanation BFM encountered a warning condition
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-7-DEBUG bfm: general debug, [chars]
Explanation The BFM's debug message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
BFM Messages
Error Message%PKT_INFRA-BFM-2-UNKNOWN_PLATFORM an unknown platform type.
Explanation platform_get_type returned an unknown platform type.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-BFM-3-BCAST_FAILED BFM: fatal event msg type [dec] bradcast for client jid [dec] error [chars]
Explanation BFM encountered a fatal message event send error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-DEGRAD_INFO bfm: service degrading error, reason = [chars]
Explanation The bfm encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-EDM BFM: fatal edm error [chars] due to [chars]
Explanation BFM encountered a fatal edm error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-FATAL bfm: fatal error encountered, reason=[chars]
Explanation iq manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-FATAL_2 bfm: fatal error encountered, reason=[chars], errno=[dec]
Explanation bfm encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-FATAL_3 bfm: fatal error encountered, reason=[chars], error=[chars]
Explanation bfm encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-GEN_INFO bfm: general information, [chars]
Explanation The BFM's informational message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-MALLOC_FAILED BFM: fatal memory allocation error for [dec] bytes
Explanation BFM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-BFM-3-MSGRPLY_FAILED BFM: fatal msg reply error for client [dec] msg type [dec]
Explanation BFM encountered a fatal message reply error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-NOT_YET_IMPLEMENTED bfm: this function [chars] is not yet implemented
Explanation BFM, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-POOL_STATUS_UNKNOWN A Pool with ID [dec] in region ID [dec] found to be in *unknown* state
Explanation BFM encountered a fatal pool state error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-USAGE bfm: invalid option [chars] passed to bfm server
Explanation Startup option supplied to BFM is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-WARNING bfm: An error encountered, reason=[chars], error=[chars]
Explanation iq manager encountered an error and is not able recover from the error. A reason text will be supplied call support with this text. Some of the functionality may not work until this error is removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-4-INIT_ERROR bfm: init error encountered, reason=[chars], attempt=[dec], error=[chars]
Explanation bfm encountered a error and is not able to recover from the error trying again. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
C12000_FWD_CLIENT_DLL Messages
Error Message%PKT_INFRA-C12000_FWD_CLIENT_DLL-3-ERR [chars][dec]
Explanation An error occured in the forwarder netio client dll (possible the plim driver)
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DM Messages
Error Message%PKT_INFRA-DM-7-INFO [chars]
Explanation An error occurred during initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ENCAP_RM Messages
Error Message%PKT_INFRA-ENCAP_RM-3-FATAL_ERR Fatal error: [chars]: Err=[dec]
Explanation A fatal error occurred in L2 Encap String RM which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-MSG_SEND_FAILED encap_rm: msg: [dec], retried: [dec] time(s), failed to send, errno: [chars]
Explanation Unable to send a message to the L2 Encap String RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-NONFATAL_ERR Nonfatal error: [chars]: Err=[dec]
Explanation This is a error message in the L2 Encap String RM to indicate anomalies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temporary situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-OOR Failed to insert L2 encapsulation string. Out of resource condition reached.
Explanation A request to insert a L2 encapsulation string into the encapsulation table has failed due to out of resource condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-6-INFO_MSG Info: [chars]
Explanation This is an informational message in the L2 Encap String RM.
Recommended Action No action is required.
ENCAP Messages
Error Message%PKT_INFRA-ENCAP-3-DEBUG_INIT_EVENT_FAILED [chars]: debug_init_event([chars]) failed error [chars]
Explanation Failed to switch ON debug event for encapsulation package.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-DEBUG_REGISTER_FAILED [chars]: debug_register() failed error [chars]
Explanation Failed to register debug events for encapsulation package.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-FAILURE [chars]
Explanation Failure in c12000/aib component.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-SYSDB_BIND_FAILED sysdb_bind failed [hex], [chars]
Explanation Failed to bind to sysdb.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-SYSDB_REGISTER_FAILED Failed to register for notification ,[[hex]] [chars]
Explanation Failed to register with Sydb for item change notification
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
FEA_DLL Messages
Error Message%PKT_INFRA-FEA_DLL-3-MSTATS_ALLOC_ERR MSTATS [chars] region: [chars]
Explanation Feature EA DLL failed to allocate statistics entry for ACL. Number of ACL entries requiring statistics entries has exceeded statistics entries reserved for security ACLs on this line card. As a result, per ACE hardware accouting for the failed ACL entries is not available. There is no impact on ability to apply security ACLs in hardware.
Recommended Action If per ACE hardware accouting is needed for ACL in error message, reduce security ACL configuration on this line card.
Error Message%PKT_INFRA-FEA_DLL-3-MSTATS_ERR MSTATS [chars] error: [chars]
Explanation Feature EA DLL encountered error on initializing interface with hardware statistics API. Process will be restarted automatically. On restart, Feature EA DLL will initialize interface with hardware statistics API and no action needs to be taken.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-REPRGM_ERROR Errored during scrub reprogramming [chars] : [chars]
Explanation TCAM entries are reprogrammed every 24 hours to ensure accuracy of hardware entries programmed earlier on user configuration or system changes. This message lists the ACL for which errors have occured during reprogramming.
Recommended Action Detach ACL in the error message from all interfaces of the line card where issue is seen. Now, re-attach ACL to the interfaces. Note that, there is a security hole during re-attachment operation window for these interfaces.
Error Message%PKT_INFRA-FEA_DLL-3-TCAM_ERR TCAM [chars] error: [chars]
Explanation Feature EA DLL encountered error in completing TCAM operation. This can lead to mismatch between hardware and software configuration.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-TCAM_LIMIT TCAM [chars] limit exceeded
Explanation This message will typically occur when permissible single region size is exceeded or total number of entries allowed in TCAM for a given application is exceeded.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FEA_DLL-3-UIDB_ERR UIDB [chars] error: [chars] : [chars]
Explanation UIDB stores the reference to ACL entries programmed in TCAM for the interface, protocol and direction. This error message is due to one of the following reasons: 1. Initialization failure of Feature EA DLL and UIDB manager interface. 2. Failure to set reference of hardware entries programmed or removed for security ACL in UIDB on configuration or system changes. This failure can lead to mismatch between hardware and software configuration.
Recommended Action If the failure is on initialization, process restart is done automatically. No manual action is required. If the failure is to set configuration bits in hardware on detaching a security ACL from interface, attach and detach security ACL again on the interface. In all other cases, detach ACL in the error message from all interfaces of the line card where issue is seen. Now, re-attach ACL to the interfaces.
FINT_N2N_NETIO Messages
Error Message%PKT_INFRA-FINT_N2N_NETIO-3-SET_MAPPING_FAILED control set mapping for capsulation [chars] protocol [dec] ([chars]) failed: [chars]
Explanation FINT n2n protocol dll could not set certain internal protocol mapping. This should not affect the functionality of any other protocol traffic, but might affect n2n protocol traffic only.
Recommended Action Try restarting the netio process. This could sometimes help fix the problem as the set mapping will be trigged again and we might not hit the failure the 2nd time. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FM Messages
Error Message%PKT_INFRA-FM-2-INFRA_FAIL [chars]: [chars] failed rc=[dec]
Explanation There was a ENA infra call failure resulting in a failure to provide some infrastructure service.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-BACKEND_EDM_DATALIST Failed to call the backend parser to handle all datalist requests : [chars]
Explanation backend_edm_datalist() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-BACKEND_EDM_GET Failed to call the backend parser to handle all get requests : [chars]
Explanation backend_edm_get() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-DATAPATH_CONTROL_FAILED [chars]: im_caps_datapath_control failed err [[chars]]
Explanation im_caps_datapath_control to LPTS netio caps dll failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-EDM_REGISTER_FAILED FM EDM initialization failed: [chars]
Explanation The FM process failed to initialize its edm manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-ERR_BAG [chars]: [chars] failed
Explanation bag_xxxx() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-ERR_INVALID_ARGS [chars]: Invalid Params
Explanation Internal error. Function was passed an Invalid Parameter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-ERR_MALLOC Cannot allocate memory in function [chars]()
Explanation Internal error. System is out of memory - malloc failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-ERR_SYSDB [chars]: [chars] failed
[chars]Explanation Sysdb api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-EVENT_CONN_NOTIFY [chars]: could not set notify handler for connection open/close/error: [chars]
Explanation An internal error was detected when trying to set notify handler for connection opens, closes and errors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-EVENT_CONN_OPEN_ALL [chars]: could not open all event connections attached to an Event Manager: [chars]
Explanation An internal error was detected when trying to open all event connections attached to an Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-IM_API_FAILED [chars]: [chars] failed
Explanation Interface Manager client api call failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-INIT_ERROR Process initialization failed: ([chars]%s)
Explanation The feature manager (feat_mgr) process failed to initialize. This process programs packet classification hardware for features which require an action to be performed based on the packet classification. If the feat_mgr process fails to initialize, the access control list cannot be programmed into the hardware. %s - indicates the reason for the initialization failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process feat_mgr location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart feat_mgr location 0/x/cpu0'. Collect all debug information if the process is continually restarting: 'debug featmgr error location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-6-INFO_GENERAL [chars]: [chars]
Explanation The FM encountered a problem of a generic nature or an informational message.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
FMGR Messages
Error Message%PKT_INFRA-FMGR-3-MATCH_TYPE_IN_ACL_NOT_SUPPORTED [chars]
Explanation The following match criteria specified in an ACL are not supported in a QoS policy: Source Port (ipv4), Packet Length. However, rest of the match criteria in the ACE (ignoring the unsupported types) have been programmed in hardware.
Recommended Action If the partial match criteria is not acceptable, the QoS policy should be removed from the interface and modified to use supported match-types. Use 'no service-policy ' in interface configuration mode to remove the QoS policy.
Error Message%PKT_INFRA-FMGR-3-SUB_ID_MSG_TOO_LARGE [chars]
Explanation A message from Platform Manager containing set/unset notifications for sub-interface VLAN IDs was too large and had to be dropped because enough memory could not be allocated. As a result, for a 'set' notification, QoS was not enabled for the reported VLANs. For an unset notification, QoS was not disabled for the reported VLANs.
Recommended Action Restart feature_mgr process. Example: In exec mode, 'process restart feature_mgr location 0/1/CPU0' This will cause all notifications to be delivered to Feature Manager again. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FMGR-3-TCAM_MGR_ERROR [chars] (error = [chars])
Explanation Request to TCAM Manager for programming QoS match rules into TCAM failed. Feature manager sends this request to TCAM manager when a policy is attached/removed to/from an interface (or fabric), when there is a change in bundle membership or when an ACL which is used in a QoS policy is modified. The most likely cause of this error is not enough space remaining in TCAM.
Recommended Action Try modifying QoS and ACL configuration to reduce TCAM usage. If TCAM space doesn't seem to be the reason, try removing and re-applying the QoS policy. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FMGR-4-UIDB_SET_WARNING Feature Mgr failed to program UIDB for QoS. (reason: [chars])
Explanation Feature Mgr failed to program the correct QoS related information in UIDB (interface data structure in hardware) when enabling/disabling QoS on the interface. The most likely cause of this message is deletion of a vlan sub-interface when there is a qos policy attached on the parent physical interface. In this case, the message is harmless and can be ignored. The reason this happens is because, the feature_mgr process tries to reset QoS related flags in the UIDB, but by that time the UIDB entry has already been deleted. It is possible, though very unlikely, for this message to appear in the following cases: 1) A QoS policy is attached on an interface. 2) QoS policy is removed from an interface. 3) Vlan-id is configured for a sub-interface and a QoS policy exists on the associated physical interface. 4) Vlan-id is un-configured on a sub-interface and a QoS policy exists on the associated physical interface. 5) When all members of a bundle go 'down'. In such cases, the warning message indicates that there could be a problem in enabling/disabling QoS on the interface.
Recommended Action For case 5 mentioned above, message can be ignored. For cases 1, 3 try removing and re-applying the QoS policy. For case 2, try applying the policy and removing it again. For case 4, delete the sub-interface itself and if needed re-create it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FMGR-7-INIT_ERROR [chars] (error: [chars]). Feature Mgr initialization failed!
Explanation Feature Mgr process failed to initialize correctly. In this case process will restart.
Recommended Action No action needed. Process will restart automatically. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD_BASE_NETIO Messages
Error Message%PKT_INFRA-FWD_BASE_NETIO-3-ERR_MEM_ALLOC Unable to get heap memory during upgrade: [chars]
Explanation Fwd basecaps dll was not able to get heap memory.
Recommended Action This message could be seen under low memory conditions and should recover once memory becomes available. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_BASE_NETIO-5-INCORRECT_SAVE_DATA_LEN Unexpected saved data length during upgrade for DLL. Expected len [unsigned int], got [unsigned int]
Explanation FINT DLL saves data across DLL upgrades. It expects the length of saved data to be same before and after upgrade, else it would cause netio to take default action (to restart) for upgrade to take effect.
Recommended Action This message indicates that netio will take default action to restart as fwd netio dll does not support dll upgrade with different saved data length. No further action is needed.
Error Message%PKT_INFRA-FWD_BASE_NETIO-5-UNSUP_MAJOR_VERSION DLL upgrade with change in major version number is not supported. Expected version [dec], got [dec]
Explanation FINT DLL does not support DLL upgrade across major version changes. This will cause netio to take default action to restart for upgrade to take effect.
Recommended Action This message indicates that netio will take default action to restart as fwd netio dll does not support dll upgrade across major version number changes. No action is needed.
FWD_HA Messages
Error Message%PKT_INFRA-FWD_HA-4-PROCESS_RESTART [chars] restart_count = [dec] mode = [dec] ([chars])
Explanation The process is being restarted either because we failed to initialize or we finished resetting shared memory and we are starting fresh.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD_NETIO_DLL Messages
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-ATTACH_FAILED fwd: netio idb attach failed for plim interface: [hex].
Explanation FWD was not able to attach to plim interface .
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BAD_COMMAND_RESULT fwd: received bad command result for buffer request: [hex]
Explanation FWD received a bad command result for BMA free buffer request
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BMA_OUT_OF_SEQUENCE fwd: BMA buffer request/response sequence number mismatch - received [dec], expected [dec]
Explanation FWD received an out of sequence BMA buffer request response
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-EGRESSQ_CREATE_FAILED fwd: egressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the egressq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FABRICQ_CREATE_FAILED fwd: fabricq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the fabricq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL fwd: fatal error encountered, reason=[chars]
Explanation Null Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason=[chars], errno=[dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-GET_CTX_ERR Failed to get idb ctx for port [dec], error - ([dec])
Explanation FWD driver got a packet but couldn't map a port to an idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-GET_CTX_ERR Failed to get idb ctx for port [dec], error - ([dec])
Explanation FWD driver got a packet but couldn't map a port to an idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-HSRMODE [[chars]]: error getting hsrmode , reason=[chars], errno=[dec]
Explanation Error determining if mode is HSR. Caller will error string and errno. Caller can also supply an additional description (like function name) to identify where this error occurred in the code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-IDB_CTX_NULL FWD idb context for port [hex] is NULL!
Explanation While processing an ingress packet, the fwd driver failed to find idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INGRESSQ_CREATE_FAILED fwd: ingressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the ingressq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INFO fwd: service degrading error, reason = [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PORT fwd: invalid plim port for plim interface: [hex]
Explanation FWD was supplied with a plim port or uidb index that exceeds the limit of num ports.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PLIM_PORT fwd: invalid plim port for plim interface: [hex]
Explanation FWD was supplied with a plim port that exceeds the limit of num ports.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MALLOC_FAILED fwd: fatal memory allocation error for bytes
Explanation FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MUTEXOPFAIL [chars]: Mutex [chars] operation failed on [chars]; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NETIO_IDB_UNAVAILABLE netio idb for interface [hex] not found, dropping packet 0x[pointer]
Explanation While processing an ingress packet, the fwd driver failed to find netio idb
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NO_OUTSTANDING_BMA_REQ fwd: received BMA buffer request response with no outstanding request
Explanation FWD received a BMA interrupt indicating a response to a BMA buffer request but there was no request made
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NOT_YET_IMPLEMENTED fwd: this function is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-PAK_PROC_ERR [chars] : [chars], pak = [hex], rc = [hex]
Explanation There was an packet processing error. Possible causes 1) Unable to retrieve fabric dest addr from inside the pkt 2) Error setting/getting input ifh from pkt
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-4-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb. Could be transient.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-6-INFO fwd: [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_EGRESS_Q_LOOKUP_ERR Failed to find netio egress qad queue. dropping packet 0x[pointer]
Explanation While transmitting a packet down to the fabric, couldn't find the egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_Q_PRODUCE_FAILED Failed to populate netio egress queue, error - [chars]
Explanation FWD driver failed to populate qad netio egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_RX_THREAD_ERR Failed to create forwarder qad rx thread, error - [chars]
Explanation FWD driver failed to create qad rx thread
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-SET_INPUT_IF_ERR Failed to set input interface handle [hex] on packet
Explanation While processing an ingress packet, the fwd driver failed to set input interface
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
FWD_TP_NETIO Messages
Error Message%PKT_INFRA-FWD_TP_NETIO-3-DEBUG_FAIL Failed to [chars] [chars] with the debugging subsystem: '[chars]'
Explanation Teleport Netio DLL failed initialization or registration with the debugging subsystem. This resulted in the restart of NetIO process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_TP_NETIO-3-DEBUG_GET_EVM_FAIL Failed to get event manager handle to register with the debugging subsystem: '[chars]'
Explanation Teleport Netio DLL failed to get the event manager handle from netio to register with debug system. This resulted in the restart of NetIO process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_TP_NETIO-5-DEBUG_CLEANUP_FAIL Failed to cleanup registration with debugging subsystem: '[chars]'
Explanation Teleport Netio DLL failed to cleanup the registration with the debugging subsystem. This may result in error when fwd DLL is re-registering with the debug system. If such an error is not noticed, no further action is needed.
Recommended Action If error is observed during reregistration, this error message could be a clue about the reregistration failing. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD Messages
Error Message%PKT_INFRA-FWD-3-CAPS_ADD_FAIL Failed to add encapsulation [dec] protocol [dec] to interfaceCH[hex] ([hex]): [chars]
Explanation Forwarder was not able to add this encapsulation to the forwarder interface. This will effect the traffic of this protocol type going to/from fabric.
Recommended Action Based on the type of error, restart of forwarder or ifmgr process might help in the capsulation addition to the interface. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-CHKPT_SAVE_ERR Error checkpointing data. This will not affect present service but forwarding of CPU bound traffic from this interface may be affected on fwd_driver_partner process restart. Ifh = [hex], port num = [dec], error = [chars]
Explanation FWD encountered an error while checkpointing interface info. While this will not affect present service, it will affect CPU bound fwding if partner process restarts.
Recommended Action If any traffic is affected after partner process restart, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-FATAL fwd: fatal error encountered, reason=[chars], error=[chars]
Explanation FWD Driver partner encountered a fatal error and is not able to recover from the error.
Recommended Action The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed the there is no need to take any action. Otherwise check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-USAGE fwd: invalid option [chars] passed to fwd server
Explanation Startup option supplied to FWD is not valid.
Recommended Action The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed the there is no need to take any action. Otherwise Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-4-NOT_YET_IMPLEMENTED fwd: this function [chars] is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action No action needs to be taken.
Error Message%PKT_INFRA-FWD-6-IFMGR_REPLY_FAIL Response to IM Notfn [chars] failed for interfaceCH[hex] ([hex]), caps [dec], proto [dec] with error [chars]
Explanation Forwarder was not able to reply to IFMGR notification. Based on the type of notification the traffic flowing through forwarder interface might or might not be affected.
Recommended Action If any traffic is affected, restarting forwarder process or ifmgr process might help in fixing the issue. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
HFR_FWD Messages
Error Message%PKT_INFRA-HFR_FWD-3-FATAL hfr_fwd: fatal error encountered, reason=[chars]
Explanation HFR FWD Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-FATAL_2 hfr_fwd: fatal error encountered, reason=[chars], errno=[dec]
Explanation hfr_fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-GEN_INFO hfr_fwd: general information,
Explanation The HFR FWD's informational message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-INFO hfr_fwd: service degrading error, reason = [chars]
Explanation The hfr_fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-MALLOC_FAILED hfr_fwd: fatal memory allocation error for bytes
Explanation HFR FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-HFR_FWD-3-NOT_YET_IMPLEMENTED hfr_fwd: this function is not yet implemented
Explanation HFR FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-USAGE hfr_fwd: invalid option passed to fwd server
Explanation Startup option supplied to HFR FWD is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
HFR_PFI Messages
Error Message%PKT_INFRA-HFR_PFI-3-SET_GLOBALS_FAILED [chars] ([chars])
Explanation Platform PFI was unable to set globals
Recommended Action No action is required.
IFMGR_ENCAP Messages
Error Message%PKT_INFRA-IFMGR_ENCAP-3-BC_ERR Encap change for [chars] [chars] [chars] failed(error [chars])
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync
Recommended Action Repeat failed configuration command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR_ENCAP-3-INIT_ERR Process initialisation failed. [chars] : [chars] ([hex])
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync
Recommended Action Repeat failed configuration command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR_ENCAP-3-SYSDB_ERR Sysdb [chars] for [chars] failed(error [chars])
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync
Recommended Action Repeat failed configuration command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IFMGR Messages
Error Message%PKT_INFRA-IFMGR-1-CORRUPT_CONTROL_TREE Control tree corruption was detected while recovering [chars]. ifh [hex] ([chars]), node [hex] [chars] [hex]
Explanation The ifmgr process cannot recover its data structures due to corrupt recovery information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-BASE_CAPS_NOT_FOUND Interface [chars] base caps not found during [chars]
Explanation The operation has failed because Interface Manager could not find the base caps on an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-ERR_FEATURE_TIMEOUT Feature [chars] timeout for context [chars]
Explanation A feature required by Interface Manager failed to start up or perform a mandatory operation within the timeout period.
Recommended Action The context in the error message gives a good idea as to what process has failed. Find out whether this process exists on the router. If not then install the process on the router and try the operation again. If it does exist then there may be a problem in the code. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-GET_TREE_NODE Cannot find node with handle [hex] in the control tree
Explanation Interface Manager failed to find a node which should exist in its tree. This indicates that the Interface Manager database is incorrect and the system may be in an inconsistent state.
Recommended Action If this message is seen repeatedly then try restarting the ifmgr process, causing it to resync. If this fails to fix the problem, then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-GSP_LOOKUP_FAILED [chars] message lookup failed. Error [hex] [chars]
Explanation GSP has difficulty in looking up the group id. There could be a communication problem.
Recommended Action If there is a problem, it might be cleared by restarting ifmgr and/or gsp. 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 provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-GSP_SEND_FAILED [chars] message send failed. Group ID: [hex], Group Name: [chars], Error: [hex] [chars]
Explanation GSP has difficulty in delivering the message to some nodes. There could be a communication problem.
Recommended Action If there is a problem, it might be cleared by restarting ifmgr. 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 provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-IMDC_BUFFER Buffer error [chars] of size [dec]
Explanation An error occurred while accessing a shared buffer. This may be due to a locking issue or a resource allocation failure.
Recommended Action The ifmgr process will try to recover from this situation, possibly by restarting. If the process does not restart automatically then try restarting it manually. This error may indicate a lack of memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-INIT Process initialisation failed. [chars]: [chars] ([hex])
Explanation There was a software error during process startup.
Recommended Action The process will restart and try to recover. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart, then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If the process does not restart automatically, restart it manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-INTERFACE_NOT_FOUND Interface [chars] not found during [chars]
Explanation The operation has failed because Interface Manager could not find the interface.
Recommended Action If there was a good reason for the interface not to be found (such as because it was being deleted) then this error may be harmless. Otherwise contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-RULE_NOT_FOUND [chars] rule for type [chars] could not be found
Explanation Interface Manager cannot complete the current operation because the relevant rules file cannot be found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-RULES_DUPLICATE_ID Error: Duplicate ID [dec] found in rules file [chars]
Explanation A rule with no static id is found in rules file. Every rule should have exactly one static id assigned to it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-RULES_NO_ID Error: ID not found in the rules file [chars]
Explanation A rule with no static id is found in rules file. Every rule should have a static id assigned to it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-SYSDB_OP_FAILED Couldn't [chars] [chars] for interface [chars] error [chars]
Explanation A sysdb item could not be modified. This may leave the system in an inconsistent state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-UNHANDLED_ERROR An unhandled error occured. (error [hex]) [chars] [chars] [chars]
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync (e.g. ifmgr may not have the same information as improxy, imd_server, pfi_ifh_server, netio concerning interfaces)
Recommended Action Unless there is a noticeable problem with the box then take no action. If there is a problem then it may be cleared by restarting ifmgr, or the processes which own the affected interfaces - thus causing a resync.
Error Message%PKT_INFRA-IFMGR-4-CAPS_NOT_ALLOWED [chars] caps is not allowed on interface [chars]
Explanation The current operation failed because the capsulation is not allowed on this interface.
Recommended Action Configure a valid caps on this interface or choose a different interface on which to configure this capsulation.
Error Message%PKT_INFRA-IFMGR-4-CLEANUP_DOWNLOAD_FAILED An error occured while attempting to undo a failed download ([chars]): [chars]. System may now be in an inconsistent state.
Explanation When certain downloads fail, IM must take corrective action to return the system to a consistent state. This message indicates that this process failed, so the system may now have been left in an inconsistent state.
Recommended Action Try undoing and redoing any operation that was taking place when the message was observed. If this does not help Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-DOWNLOAD_FAILED [chars] download to nodeid [hex] failed: [chars] ([hex])
Explanation An attempt to download information required by a node failed.
Recommended Action Although the process recovers from this error it may lead to problems later. Restarting the ifmgr process on the affected node will cause it to reinitialise and try again. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-INVALID_NODESET Attempting to send a download with an invalid ack nodeset containing [dec] down nodes
Explanation IM's internal record of the nodes to which interfaces or caps have been replicated has become inconsistent due to incorrectly handling a node OIR. This has resulted in IM attempting to send a download to the removed node, causing the download to fail, so the system may now be in an inconsistent state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-REPLICATION_CLEANUP_FAILED An error occured while attempting to clean up replication info for an interface ([hex]): [chars]. System may now be in an inconsistent state.
Explanation When replication operations succeed or fail, IM must to return the system to a consistent state. This message indicates that this process failed, so the system may now have been left in an inconsistent state.
Recommended Action Try undoing and redoing any operation that was taking place when the message was observed. If this does not help Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_BADNUMERIC rule [chars]([dec]): error parsing '[chars]' as numeric (zero used)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_BADRANGE rule [chars]([dec]): invalid range (ignored)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_DUPLICATE rule [chars]([dec]): duplicate [chars] (ignored)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_EXCESS rule [chars]([dec]): excess text on line (discarding past '[chars]')
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_HEX_EXCESS rule [chars]([dec]): hex value exceeds 32 bit (discarding '[chars]')
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_INCOMPLETE An incomplete rule's definition in file:[chars]
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the rules within the given file to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_MISSINGARG rule [chars]([dec]): missing argument(s) to '[chars]' (ignored)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_MISSINGTAG rule [chars]([dec]): tag missing (record discarded)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_TOOLONG rule [chars]([dec]): '[chars]' exceeds max of [dec] chars (truncated)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_UNKNOWNFLAG rule [chars]([dec]): unknown flag '[chars]' (ignored)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-RULES_UNKNOWNKEYWORD rule [chars]([dec]): unknown keyword '[chars]' (ignored)
Explanation An internal syntax error was detected in one of the rules files. This will not affect the ifmgr process although it may cause the given rule to work incorrectly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-SYSDB_BULK_FAILED Attempt to [chars] a SysDB bulk operation returned error [chars]
Explanation There was an error while trying to modify some SysDB items in bulk, which could leave the system in an inconsistent state.
Recommended Action A failure to start a bulk request can be ignored, provided there are no further errors, as the SysDB operations will still be completed individually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. A failure to commit or abort a bulk request implies that some or all of the operations within the request failed to take effect, potentially leaving the system in an inconsistent state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-6-BULK_DOWNLOAD_FAILED Bulk [chars] id:[unsigned int], count:[unsigned int], ifh[0]=[chars] ([hex]), caps:[chars] ([unsigned int]), proto: [chars] ([unsigned int]): [chars]
Explanation A bulk download operation has failed for one or more interfaces or capsulations. The ifmgr process will try to recover from this failure so this message is for information only.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-6-GSP_SEND_RETRY [chars] message send error. Group ID: [hex], Group Name: [chars], Error: [hex] [chars]
Explanation GSP has difficulty in delivering a message to some nodes. There could be a communication problem. This warning is for information only since the message will be resent.
Recommended Action No action is required.
IMAEDM Messages
Error Message%PKT_INFRA-IMAEDM-3-EVENT_CONN_CREATE_FAILED [chars]: could not create connection structure for the connection to [chars]: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-EVENT_CONN_NOTIFY_FAILED [chars]: could not set notify handler for connection opens and errors to [chars] : [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-EVENT_CONN_OPEN_ALL_FAILED [chars]: opening all connections of Event Manager failed: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-INTERNAL_ERR [chars]: Internal error: [chars]: [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, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-3-SYSMGR_PROC_READY_FAILED [chars]: sysmgr_proc_ready failed: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-TIMER_CREATE_FAILED [chars]: Timer creation failed: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-7-BAG_REG_FAILED [chars]: bag register error is detected; [chars].
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the im/imaedm/[chars] event failed: [chars]
Explanation An error was returned when the IM Attribute EDM server called the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-7-DEBUG_REGISTER [chars]: Debug registration for IM Attribute EDM server failed: [chars]
Explanation An error was returned when the IM Attribute EDM server called the debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-7-EDM_INIT_FAILED [chars]: Failed to open EDM connections (retries [unsigned int][chars]). Turn on debug imaedm errors to diagnose failure.
Explanation The opening of EDM connections has failed repeatedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-7-EVM_CREATE_FAILED [chars]: event_manager_create failed; [chars]
Explanation The event_manager_create function reported an error trying to initialize the event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IMATTR Messages
Error Message%PKT_INFRA-IMATTR-3-DUPLICATE Received duplicate successful replies for interface [hex], attribute type [chars]
Explanation The attribute client has received duplicate successful responses for this attribute on this interface. This would suggest that multiple attribute owners have been configured for this (interface, attribute) pair.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMATTR-3-NOTIFY_FAILED A bulked notification message failed to be sent: [chars]
Explanation The attribute owner library has failed to send a bulk notification message to the attribute clients. However, the attribute owner that produced these notifications is not aware that they failed to be sent. This could result in the attribute clients being out of sync with this owner.
Recommended Action If the system appears to be in a low-memory condition (check the output of 'show mem summary') then this is most likely the cause of the problem. Please try to fix the low-memory condition. If this is not the case, then contact technical support.
Error Message%PKT_INFRA-IMATTR-3-SET_REPLY_FAILED At least 1 item in a bulk set/clear operation succeeded, but the client cannot be informed due to an error: [chars]
Explanation The attribute owner library has failed to reply to the client to inform it that a set or clear operation has succeeded. This could result in the client being out of sync with the owner.
Recommended Action If the system appears to be in a low-memory condition (check the output of 'show mem summary') then this is most likely the cause of the problem. Please try to fix the low-memory condition. If this is not the case, then contact technical support.
IMD Messages
Error Message%PKT_INFRA-IMD-3-CLIENT [chars]. Error [[hex]] [[chars]]
Explanation An error has occurred in IMD's client database.
Recommended Action IMD will try to recover from this failure. If problems are still seen then try restarting the imd_server process. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMD-3-COMM Communication error: [chars]. Error [[chars]]
Explanation The IMD process failed to send a message to another process.
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 provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMD-3-ENQUEUE Failed to add [chars] to the [chars] queue
Explanation IMD failed to add an element to an internal queue structure.
Recommended Action This error indicates a problem in the code and cannot be easily recovered from. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMD-3-IFBASE [chars]. Error [[chars]]. Node [[hex], [unsigned int], [unsigned int]]
Explanation There was a failure with IMD's IFBASE component.
Recommended Action This error indicates a problem with the code. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMD-3-INIT Init error: [chars]: [chars] ([dec])
Explanation An error occurred while the process was starting up.
Recommended Action The process will restart and try to recover. If the proecess does not restart automatically then try restarting the imd_server process manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMD-3-RESYNC Failure to resync IMD database for node [hex]: [chars]. Error [[chars]]
Explanation The IMD process failed to resync its database for the specified node. This may not cause any problems but it is possible that it could lead to an inconsistant view of interfaces.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMD-4-INIT_NO_RESTART Init error: [chars]: [chars] ([dec]).
Explanation An error occurred while the process was starting up.
Recommended Action This message is a warning only and the process will recover gracefully. However this unexpected event might indicate that there is a more serious problem elsewhere. If other problems are seen then include this message in the report.
Error Message%PKT_INFRA-IMD-4-UNKNOWN_CASE [chars]. Value [unsigned int]
Explanation IMD has reached an unexpected case.
Recommended Action IMD does not know how to handle this situation so it will take the default action. This message may be harmless but it may indicate a more serious problem such as a version mismatch. If other problems are also noted then include this error message when reporting them.
IMPROXY Messages
Error Message%PKT_INFRA-IMPROXY-3-EA_ID_OVERUSE caps/intf ID overuse by EA [chars], id=[dec], maximum allowed=[dec]
Explanation Specified feature Execution Agent (EA) has used more capsulation/interface IDs than the maximum allowed by the infrastructure. EA process restart may not work as a result of this.
Recommended Action Restarting IMProxy may solve any problems that may be seen as a result of this message. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMPROXY-3-GSP_SEND_FAILED GSP message send failed: ([hex]) [chars]
Explanation GSP has difficulty in delivering the mesage to some nodes. There could be a communication problem.
Recommended Action Restarting IMProxy may solve any problems that may be seen as a result of this message. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMPROXY-3-IIR_CONNECT_FAILED Failed to connect to IIR: [chars] ([hex])
Explanation Improxy failed to open it connection to the IIR service.
Recommended Action Restarting IMProxy may solve any problems that may be seen as a result of this message. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMPROXY-3-INIT Process initialisation failed: [chars]: [chars] ([hex])
Explanation An error occurred while the process was starting up.
Recommended Action The process will restart and try to recover. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart, then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If the process does not restart automatically, restart it manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMPROXY-3-INITIAL_DOWNLOAD_FAILED Initial Download Timer Expired: [chars] (pending nodes=[dec])
Explanation The initial download to netio could not be sent, or failed to complete within the timeout period. This may prevent software forwarding on the interfaces on this node.
Recommended Action Restarting IMProxy will cause the download to be retried and may fix this problem. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMPROXY-7-EA_TIMEOUT [chars] EA did not respond to improxy in [unsigned int] seconds, operation [chars] failed.
Explanation A feature Execution Agent (EA) required by IMProxy failed to respond within the timeout period. This does not cause a problem in itself, but may indicate a problem with the EA process or elsewhere in the system.
Recommended Action Follow the advice given for other error messages, if any, occuring at the same time.
INTERFACE_CONFIG Messages
Error Message%PKT_INFRA-INTERFACE_CONFIG-3-SET_DEFAULT_ERR Couldn't reset MAC address value for interface [chars] (error: [chars])
Explanation An error occurred while resetting the MAC address for the specified interface to the default. The interface may still have the wrong MAC address, and different parts of the system may be using different values for the interface's MAC address.
Recommended Action If the message appeared as a result of applying configuration, try removing and re-applying the configuration concerned. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-3-SET_ERR Could not set MAC address for interface [chars] (error: [chars])
Explanation An error occurred while setting the MAC address for the specified interface to the configured value. The interface may still have the wrong MAC address, and different parts of the system may be using different values for the interface's MAC address.
Recommended Action If the message appeared as a result of applying configuration, try removing and re-applying the configuration concerned. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-4-EVENT_BLOCK_ERROR An error occurred while waiting for an event (error: [chars])
Explanation The Interface Configuration process encountered an error while waiting for an event. The process will automatically restart and retry.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-4-INIT_FAILURE Initialisation failure during [chars]: error [chars]
Explanation The Interface Configuration process encountered an error while initialising. It will not be possible to configure interface MAC addresses until the process starts successfully. The process will automatically restart and retry.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LINEPROTO Messages
Error Message%PKT_INFRA-LINEPROTO-5-UPDOWN Line protocol on Interface [chars], changed state to [chars]
Explanation The data link level line protocol changed state.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface and line protocol.
LINK Messages
Error Message%PKT_INFRA-LINK-3-UPDOWN Interface [chars], changed state to [chars]
Explanation The interface hardware went either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
Error Message%PKT_INFRA-LINK-5-CHANGED Interface [chars], changed state to [chars]
Explanation The interface has changed state.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
LPTS_LIB Messages
Error Message%PKT_INFRA-LPTS_LIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_LIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_LIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_MRT Messages
Error Message%PKT_INFRA-LPTS_MRT-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_MRT-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_MRT-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PA_FF_CL Messages
Error Message%PKT_INFRA-LPTS_PA_FF_CL-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF_CL-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PA_FF Messages
Error Message%PKT_INFRA-LPTS_PA_FF-3-CLIENT_NOT_FOUND [chars]: The client structure associated with this client was not found
Explanation An internal error was detected when trying find the internal client structure for a given operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-EVENT_BLOCK [chars]: failed to block waiting for Event Manager events: [chars]
Explanation An internal error was detected when block waiting for Event Manager events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-EVENT_INIT_EVENT [chars]: could not initialize event structure: [chars]
Explanation An internal error was detected when initializing a sigevent structure using event_init_event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-EVM_ASYNC_ATTACH [chars]: could not attach handler for Event Manager asynchronous event: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager asynchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-EVM_CREATE [chars]: could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-GET_NODEID [chars]: Can't get my own nodeid: [chars]
Explanation A call to platform_get_my_nodeid faild.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-INIT [chars]: initialization for PA Flow Forwarder I/O thread failed: [chars]
Explanation An internal error was detected when initializing PA Flow Forwarder I/O thread.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-LRD_FAIL [chars]: error from lrd function [chars]: [chars]
Explanation An internal error was detected when using a logical router daemon api
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-MALLOC [chars]: malloc [dec] bytes failed: [chars]
Explanation An attempt to allocate meory failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-MSG_ATTACH_SYNC [chars]: failed to attach handler for Event Manager synchronous event: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager synchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-MSG_CLINFO_GET_DATUM [chars]: msg_clinfo_get_datum failed: [chars]
Explanation An internal error was detected when accessing a client info structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-MSG_SEND_EVENT [chars]: msg_send_event failed: [chars]
Explanation An internal error was detected when sending an Event Manager synchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-TIMER_CREATE [chars]: could create the timer: [chars]
Explanation An internal error was detected when creating a timer using timer_create.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PA_FF-3-TIMER_SETTIME [chars]: could arm the timer: [chars]
Explanation An internal error was detected when arming a timer using timer_settime.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PA_FGID_DB Messages
Error Message%PKT_INFRA-LPTS_PA_FGID_DB-3-INFRA_ERR Unrecoverable error in FGID resource managing infrastructure : [chars]
Explanation A severe internal error was detected while using Fabric Multicast Group Indentifier(FGID) resource managing infrastructure APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PIFIB Messages
Error Message%PKT_INFRA-LPTS_PIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PREIFIB Messages
Error Message%PKT_INFRA-LPTS_PREIFIB-3-BACKEND_EDM [chars]: EDM backend function [chars] failed: [chars]
Explanation An internal EDM backend function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-BAG [chars]: Bag function [chars] failed: [chars]
Explanation An internal bag function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-BATCHING [chars]: Error [chars] during batching '[chars]' from hardware pre-ifib
Explanation Hardware pre-ifib returned an error during a batching operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-BLC_UPDATE [chars]: BLC '[chars]' failed for interface handle: [hex]
Explanation Bundle (vlan) interface update to local bundle (vlan) database failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-DATAPATH_CMD [chars]: Pre-IFIB datapath control command [chars] failed: [chars]
Explanation The given Pre-IFIB datapath control command returns error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EDM_UNREG [chars]: failed to unregister EDM: [chars]
Explanation An internal error was detected when trying to unregister EDM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-ENTRY_UPDATE [chars]: Error [chars] while updating entry with '[chars]' [hex]
Explanation Error during entry delete or update.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EVENT_BLOCK [chars]: failed to block waiting for Event Manager events: [chars]
Explanation An internal error was detected when block waiting for Event Manager events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EVENT_CONN_NOTIFY [chars]: could not set notify handler for connection open/close/error: [chars]
Explanation An internal error was detected when trying to set notify handler for connection opens, closes and errors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EVENT_CONN_OPEN_ALL [chars]: could not open all event connections of this event manager: [chars]
Explanation An internal error was detected when trying to open all event connections of one event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EVM_CREATE [chars]: could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EVM_TM_ATTACH [chars]: could not set up a managed timer identifier: [chars]
Explanation An internal error was detected when trying to allocate a managed timer identifier and assign to it an event handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-EVM_TM_LEAF_NEW [chars]: could not create a managed timer tree leaf: [chars]
Explanation An internal error was detected when trying to create a managed timer tree leaf for the event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-HW_RETRY [chars]: Error [chars] during hardware retry to update entry in TCAM
Explanation Hardware pre-ifib returned an error during a update retry operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-IIR_QUERY [chars]: Error [chars] during POS bundle member query from IIR for ifhandle [hex]
Explanation Hardware pre-ifib returned an error during a batching operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-IM_CAPS_DATAPATH_CONTROL [chars]: the datapath control function for the capsulation failed: [chars]
Explanation An internal error was detected when calling datapath control function for the capsulation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-INVALID_ARGS [chars]: Invalid arguments: [chars]
Explanation The given argument is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-LRD_FAIL [chars]: error from lrd function [chars]: [chars]
Explanation An internal error was detected when using a logical router daemon api
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-LTRACE_INIT [chars]: Initialization of lightweight tracing buffer '[chars]' failed: [chars]
Explanation Lightweight tracing initialization failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-MSG_CHAN_GLOBAL [chars]: failed to publish global directory channel: [chars]
Explanation An internal error was detected when publishing a global directory channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-NOMEM [chars]: Not enough memory
Explanation Memory low condition is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-PA_FF_OPEN [chars]: failed to connect to the Port Arbitrator as a Flow Forwarder: [chars]
Explanation An internal error was detected when trying to connect to the Port Arbitrator as a Flow Forwarder.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-PA_FF_RESET [chars]: Reset of BCDL group in LPTS PA/FF library failed: [chars]
Explanation An internal error was detected when trying to reset the BCDL group for the LPTS Port Arbitrator/Flow Forwarder.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-PA_UPDATE [chars]: Error [chars] during '[chars]' from PA
Explanation Update from PA failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-PARSE_INFLOW_CONFIG [chars]: could not read input flow config file: [chars]
Explanation An internal error was detected when trying to parse the input flow configuration file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-PFI_IFH_BIND [chars]: Failed to connect to PFI Interface Handle Server: [chars]
Explanation Failed to connect to PFI Interface Handle Server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-PIFIBM_INIT [chars]: failed to initialize Pre-IFIB Mgr: [chars]
Explanation An internal error was detected when trying to initialize the Pre-IFIB Mgr.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-REASS_LIST [chars]: Corrupted reassembly server list received: num_nodes [dec]
Explanation The list of reassembly servers is incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-SYSDB [chars]: Sysdb function [chars] failed: [chars]
Explanation An internal sysdb function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-SYSMGR_PROC_READY [chars]: failed to notify sysmgr that we are ready: [chars]
Explanation An internal error was detected when trying to notify sysmgr that we are ready.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-VRF_UPDATE [chars]: VRF '[chars]' failed for VRF id: [hex]
Explanation VRF update to attached VRFs database on LC failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-6-NETIO_DOWN Pre-IFIB can't establish connection to NetIO in [dec]:[dec]
Explanation Pre-IFIB process can't establish connection to NetIO.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-6-NETIO_UP Pre-IFIB establish connection to NetIO after [dec]:[dec]
Explanation Pre-IFIB process established connection to NetIO.
Recommended Action No action is required.
Error Message%PKT_INFRA-LPTS_PREIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS Messages
Error Message%PKT_INFRA-LPTS-3-ERR_BAD_LISTENER_TAG bad listner tag detected on the packet, dropping packet
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_BAG_ENCODE [chars]: SysDB Bag encoding failed: [chars]
Explanation An internal error was detected when trying to encode a SysDB Bag.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_BAG_REG [chars]: SysDB Bag registration failed: [chars]
Explanation An internal error was detected when trying to register a SysDB Bag definition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_DATAPATH_INPUT_LEN datapath control input buffer len error: length = ([dec])
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_DEBUG_REG [chars]: debug register failed: [chars]
Explanation An internal error was detected when trying to register for changes to debug tuples.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_ECM_CREATE [chars]: couldn't create event connection manager: [chars]
Explanation An internal error was detected when trying to create event connection manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_ECM_OPEN [chars]: couldn't open event connection: [chars]
Explanation An internal error was detected when trying to open event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_EDM_DATALIST_ADD [chars]: adding datalist as a SysDB EDM failed: [chars]
Explanation An internal error was detected when trying to add an item to SysDB data list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_EDM_DATALIST_CREATE [chars]: adding datalist as a SysDB EDM failed: [chars]
Explanation An internal error was detected when trying to create a SysDB data list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_EDM_REG [chars]: registering as a SysDB EDM failed: [chars]
Explanation An internal error was detected when trying to register as a SysDB EDM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_EVM_CREATE [chars]: couldn't create event manager: [chars]
Explanation An internal error was detected when trying to create event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_FINT_MEDIA_REG Couldn't set control mapping for lpts media on fint
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_HSSD [chars]: [chars] failed
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_HSSD_GET_DATA [chars]: retrieving data from HSSD failed: [chars]
Explanation An internal error was detected when trying to read data from the packet HSSD area.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_IFIB [chars]: [chars] failed
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_IFIB_RES_ALLOC Couldn't allocate platform-specific IFIB result structure: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_IFIB_RES_SET failed to set platform-specific IFIB result fields: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_IFIB_SET_KEY [chars]: lpts_netio_ifib_set_key() failed
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_INFO_GENERAL [chars]: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_INVALID_ARGS [chars]: invalid args
Explanation Detected invalid arguments.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_MALLOC [chars]: malloc failure
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_NETIO_DEBUG_INIT lpts netio debugging failed to initialize
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_NETWORK_START_FAIL Unable to get packet network start. Dropping packet
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_NULL_FINT_IDB NULL fint idb.. dropping packet
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_NULL_TRANSPORT_CALLBACK [chars]: Null transport callback
Explanation Detected a NULL transport callback function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PA_CLOSE [chars]: couldn't close the client connection with PA: [chars]
Explanation An internal error was detected when trying to close the client connection with PA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PA_CONN [chars]: couldn't establish connection with PA: [chars]
Explanation An internal error was detected when trying to connection to PA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PAK_DUP couldn't duplicate packet (deliver failed), error = [dec]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PAK_NETIO_MUTEX_LOCK [chars]: pak_netio_mutex_lock() failed: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PAK_NETIO_MUTEX_UNLOCK [chars]: pak_netio_mutex_unlock() failed: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PAK_NETIO_RETURN_BUFFER [chars]: pak_netio_return_buffer() failed: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PAK_NETIO_UINT8_GET [chars]: pak_netio_uint8_get() failed: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PLATFORM_GET_MY_NODEID [chars]: couldn't get my node ID: [chars]
Explanation An internal error was detected when trying to get the node ID for the node on which the caller is running.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PREPARE_EGRESS_BUFFHDR [chars]: failed to process egress buffer header of packet [hex]: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PROCESS_INGRESS_BUFFHDR [chars]: failed to process ingress buffer header of packet [hex]: [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_PUNT_FAIL punt to [chars] failed, dropping packet: [chars]
Explanation One of the possible cause for this message could be denial-of-service attack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_SYSDB_CONN_TO_COID [chars]: converting SysDB connection ID to file descriptor failed: [chars]
Explanation An internal error was detected when trying to convert a SysDB connection ID to a file descriptor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-3-ERR_SYSDB_NS_NODE_TO_STR [chars]: converting node ID to SysDB string failed: [chars]
Explanation An internal error was detected when trying to convert a node ID to a string format that SysDB expects.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS-6-INFO_INTERNAL_TABLE LPTS tables changed in middle of walk. Show command incomplete.
Explanation During processing of a show command, the internal LPTS data structures changed in such a way as to make completion of the show command impossible.
Recommended Action Retry the command.
netio_debug Messages
Error Message%PKT_INFRA-netio_debug-3-INIT_FAILED NetIO debugging partner initialization failed: [chars] (Err=[chars])
Explanation The NetIO debugging partner process initialization failed. This could happen due to errors in various server processes. The error code and its text in the message will reveal the source of the error.
Recommended Action If the process restarts and this message is not repeating, no actions are needed. If this message recurs, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-netio_debug-4-ASYNC_HANDLER Couldn't install the default handler for async messages, err: [chars]
Explanation The NetIO debugging partner process couldn't install the default event handler for async messages.
Recommended Action No action is required.
NETIO Messages
Error Message%PKT_INFRA-NETIO-3-ERR_ARP [chars], [chars], [dec]
Explanation ARP netio error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_INIT [chars] : Failed to initialize ipv4 proto for [chars] with error ([chars])
Explanation netio initialization error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_MEDIA_REGISTER [chars] : Failed for ipv4 proto to [chars] ([chars])
Explanation netio media register or callback error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_PACKET_INPUT Failed to input the packet for [chars] ([chars])
Explanation Failed to input the packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-LTRACE_INIT ltrace_init failed for '[chars]': [chars]
Explanation Netio ltrace facility failed to initlize one of the trace buffers. The Netio trace information will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-PAK_NETIO_MUTEX_LOCK [chars] : Failed to acquire pak netio mutex lock ([chars])
Explanation ARP netio error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-SCRIPT_ERR_MEM_ALLOC Cannot allocate memory in [chars]
Explanation Internal error. System is out of memory - malloc failed.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-3-SCRIPT_FAIL netio script failed: [chars]
Explanation An error occurred during netio script processing. Please check the error message for more details.
Recommended Action Check if the script file exists and is in correct format. If the message recurs, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-SELFMANAGE_FAILURE [chars] failed during self managed upgrade of DLL/SMU, Error: [chars]
Explanation NetIO was attempting a hitless upgrade of a DLL that was part of a SMU/PIE. A step during this operation encountered this error. Netio may or may not be able to perform the DLL upgrade successfully when this error is encountered.
Recommended Action If the DLL upgrade is successful, no further action is needed. Otherwise it is recommended that netio is restarted, to recover from an inconsistent DLL upgrade state in NetIO. Restart of netio should lead to the new DLL take effect and bring back things to normal.
Error Message%PKT_INFRA-NETIO-4-BAD_PACKET NetIO received a packet with no data particle in it, packet: 0x[pointer], packet PID: [dec]
Explanation NetIO received a bad packet from the driver (or from an application) that had no particle data in it. NetIO drops these packets. If too many such packets belonging to a routing protocol are received and dropped, we have a potential possibility of an adjancency flap.
Recommended Action If no side effects are observed nothing needs to be done and NetIO would just drop these packets and continue with its normal operation. If this message is seen many number of times, it indicates some sort of issue in the driver sending packets to NetIO and the driver needs to be analysed further, in that case Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-4-SCRIPT_WARNING script [chars]([dec]): [chars]
Explanation An internal syntax error was detected in the script file. The current line was skipped and the execution of the script continued.
Recommended Action Check the script for the skipped or ignored line. Make syntax changes as needed.
Error Message%PKT_INFRA-NETIO-5-SELFMANAGE_UPGRADE_NOTICE NetIO DLL is being upgraded. NetIO will be restarted
Explanation NetIO gets restarted whenever we upgrade a DLL that does not support NetIO DLL upgrade. This should not cause any problems to the router and NetIO should come back up fine after restart.
Recommended Action This should not cause any problems in the router, NetIO should restart and come back up fine & resume its normal functionality. If it causes any routing issues such as adjacency going down or some other problem, one potential cause is that NetIO took longer to restart. NetIO restart time is a function of number of interfaces configured in NetIO on this node. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-6-ERR_THREAD_MUTEX packet mutex [chars] failed : [chars]
Explanation NetIO was unable lock/unlock the packet mutex. This could lead to certain cases when the same packet is used
Recommended Action --
Error Message%PKT_INFRA-NETIO-6-SELFMANAGE_INFO NetIO is upgrading([chars]) the dll [chars]
Explanation Netio is upgrading this dll. This is here only for informational purpose only. No further action is recommended/needed.
Recommended Action 'No action is required.'
Error Message%PKT_INFRA-NETIO-7-ERR_CREATE_IDB create idb error: interface ifhandle [hex] already in datastore with name [chars], new name [chars]
Explanation Netio already has this IDB in its datastore. It is getting a request for create for the same interface handle but with a different name. This could possibly cause issues with this interface in NetIO.
Recommended Action After the information is gathered, restart of netio/improxy should possibly bring netio in sync with ifmgr leading to the delete of this idb from Netio. If the create operation is retried it might succeed. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-7-ERR_DELETE_IDB_SUBBLOCK delete idb:interface (ifhandle = [hex], name [chars]) having subblocks (name [chars], refcount [dec]) cannot be deleted. Error: [chars]
Explanation NetIO cannot delete an interface which still has subblocks associated with it. This error could potentially cause issues with recreate of any interface, if the same interface handle is reused.
Recommended Action After the information is gathered, restart of netio/improxy should possibly will bring them in sync with ifmgr & delete the protocol chains and hence the subblocks. If restart doesnot help. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-7-ERR_DELETE_IDB_SUBINTF delete idb: interface (ifhandle = [hex], name [chars]) having subinterfaces (demux index: [dec], ifh [hex], name [chars]) cannot be deleted. Error: [chars]
Explanation NetIO cannot delete a interface which still have subinterfaces under it. This could potentially cause issues with recreate of any interface, if the same interface handle is reused.
Recommended Action After the information is gathered, restart of netio/improxy should possibly bring them in sync with ifmgr & delete the main and subinterfaces. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-7-ERROR_INIT [chars] Failed, Error: [chars]
Explanation NetIO process has problem initializing its database and attempts to restart in an attempt to recover from the error.
Recommended Action The process attempts to restart on detecting this failure, in an effort to recover from the failure. If after restart things recover, then nothing more needs to be done. If the error is seen when the system is low on system resources, once the system resource like memory, cpu go back to normal state, the process should succeed in coming back up. If the process fails to recover and repeatedly exits then the ios message will have the details of what part of initialization failed and the reason for it, for further action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
PA Messages
Error Message%PKT_INFRA-PA-2-CTX_CREATE [chars]: Can't create VRF context structures. VRF '[chars]' ([hex]) error [chars] ([unsigned int])
Explanation PA Can't create VFR context structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-2-INFRA_FAIL [chars]: [chars] failed rc=[dec]
Explanation There was a ENA infra call failure resulting in a failure to provide some infrastructure service.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-PA-2-RSI_ERROR RSI [chars] failed error [chars] ([unsigned int])
Explanation RSI error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-2-RSI_UNKNOWN_EVENT Unknown event from RSI event [unsigned int]
Explanation RSI sent unknown event
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ECM_SETRETRY_FAIL Error setting linear connection retry mechanism : [chars]
Explanation Failed to set linear connection retry mechanism in Port Arbitrator Client
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_ADD_SLICE [chars]: Assign of slice [chars] to node [hex] failed. ([chars])
Explanation The PA failed to assign an IFIB slice.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_BACKEND [chars]: [chars] failed
Explanation Sysdb backend api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_BAG [chars]: [chars] failed: [chars]
Explanation Bag api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_FM_MSG_TIMEOUT [chars]: [chars] update of slice [chars] to node [hex] timed out.
Explanation The PA failed to receive a response to an IFIB table update or an IFIB slice assignment update message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_LOCK [chars] line [dec]: error: [chars]
Explanation An attempt to lock a mutex failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_PIFIB_MSG_TIMEOUT [chars]: Pre-IFIB update for slice [chars] timed out.
Explanation The PA failed to receive a response to a critical Pre-IFIB update.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_SYSDB [chars]: [chars] failed
[chars]Explanation Sysdb api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_UNLOCK [chars] line [dec]: error: [chars]
Explanation An attempt to lock a mutex failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-EVENT_REGISTRATION_FAILED PA failed to connect to the event manager: [chars]
Explanation The PA process failed while attempting to connect to an event manager channel for the indicated subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-6-INFO_GENERAL [chars]: [chars]
Explanation The PA encountered some problem in genric nature or plain information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
PAK Messages
Error Message%PKT_INFRA-PAK-3-DEBUGINITFAIL [chars]
Explanation An error occurred during packet debug events initilization. Refer to the error message for the particular cause.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-7-EXCEPTION_LITE packet exception, reason: [chars]
Explanation An software exception had occurred in the packet manager library. The client process terminated with exit code -1. The reason is that the client passed an invalid packet to packet manager library and led to the exception.
Recommended Action Normally the client process will restart and re-connect to packet manager. If any of these messages recur, call your technical support representative for assistance.
PAK_CAPTURE Messages
Error Message%PKT_INFRA-PAK_CAPTURE-4-ECC_ERROR packet dropped in hw due to programming error: pkt type [hex] pkt: [chars]
Explanation A packet was dropped in hardware due to bad programming or a hardware error. This is a raw dump of the packet to aid in debugging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information
PAKPLATFORM Messages
Error Message%PKT_INFRA-PAKPLATFORM-3-CONNECTFAIL Connect to the packet server failed. Reason : [chars]
Explanation The platform driver was not able to connect to the packet server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKPLATFORM-6-SENDFAIL Send data to the packet server failed. Reason : [chars]
Explanation The platform driver was not able to send data to the packet manager. This could happen when the platform driver is trying to send the initilization information to the packet manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PAKSRV Messages
Error Message%PKT_INFRA-PAKSRV-2-ERR_MUTEX_REVIVAL Failed to revive the packet mutex, reason: [chars]
Explanation The packet subsystem failed to revive the packet mutex.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-MEMUTILMAPFAIL Memory mapping for [chars] failed, reason: [chars]
Explanation Memory maping for the specified area failed and packet server will restart.
Recommended Action If the error is not rectified after two or more restarts, please call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-3-BADPAK Corruption detected in the [chars] at [pointer] owned by packet [pointer] belonging to process [dec]
Explanation Consistency check detected corruption in the specified area of the specified packet. This will cause packet manager to restart. Please report the message and value to your technical support representative.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-3-DIAGFAIL Packet server: line [dec], fatal misalignment.
Explanation Packet server internal structures are misaligned. This is a fatal programming error. The value is a marker for tracking down the misalignment. Please report the message and value to your technical support representative.
Recommended Action Call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-3-ERR_MEM_ALLOC Memory allocation failed in process [dec] at [chars]
Explanation Packet server failed to allocate more memory.
Recommended Action It may be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-BADPTCL_DUMP [chars]: [chars]
Explanation Particle body corruption is detected. This message follows a BADPAK message and dumps the first few bytes of the particle body and the last few bytes of the one before.
Recommended Action None. This is message is only for debugging purpose.
Error Message%PKT_INFRA-PAKSRV-7-BCASTFAIL Failed to send broadcast message [dec] to client [dec], error: [chars]
Explanation Packet server failed to send a broadcast message to the client. This will result in the client being unaware of an event that occurred in the packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-CHANCREATEFAIL Failed to create a channel and event manager, error: [chars]
Explanation Packet server failed to create an event manager and channel. Clients will be unable to connect to packet server, and packet server will be unable to send and receive messages.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-CHUNKCREATEFAIL Chunk creation for packet headers failed
Explanation Could not allocate a chunk of memory for the packet headers.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-CONDWAITFAIL Conditional wait operation on [chars] in [chars] failed; reason [chars]
Explanation The packet subsystem failed to perform a conditional wait. This usually indicates a programming error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKSRV-7-DEBUGINITFAIL Packet server debug initialization: [chars] failed, error [chars]
Explanation The debug support initalization failed in the packet server. It will be restarted by sysmgr and should recover.
Recommended Action If packet manager is unable to start up after several restarts by sysmgr, please collect the 'sh log' output and contact your customer support representative.
Error Message%PKT_INFRA-PAKSRV-7-DEQUEUEFAIL Failed to remove client [dec] from clients list at [chars]
Explanation Packet server failed to remove the specified client from the client list queue. This may cause the client fail to reconnect to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ENQUEUEFAIL Fail to insert client [dec] into the list of clients at [chars]
Explanation Packet Server failed to insert a client into client list queue. This will prevent the client from connecting to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_CHKPT_OP [chars]: [chars] check point operation failed, reason : [chars]
Explanation A check point operation failed in packet manager.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_EVM_ATTACH Failed to attach event handler.
Explanation The packet subsystem encountered an error when attaching a handler for synchronous or asynchronous events.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_MUTEX_INIT Failed to initialize packet mutex, reason: [chars]
Explanation The packet subsystem failed to initialize the packet mutex.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_MUTEX_MONREG Packet server registration for mutex monitoring (revival) failed, error [chars]
Explanation Packet server failed to register for the mutex revival and will exit. It will be restarted by sysmgr.
Recommended Action If packet manager is unable to start up after several restarts by sysmgr, please collect the 'sh log' output and contact your customer support representative.
Error Message%PKT_INFRA-PAKSRV-7-ERR_MUTEX_OP Mutex [chars] operation on [chars] in [chars] failed; reason [chars]
Explanation The packet subsystem failed to perform the specified operation on the specified mutex. This usually indicates a programming error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKSRV-7-ERR_THREAD_ATTR_SET [chars]: Failed to set thread attributes
Explanation Packet server unable to set the thread's attributes.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_THREAD_CREATE Failed to create the [chars] thread
Explanation Packet server was unable to create the specified thread.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_THREAD_DETACH [chars]: Failed to detach from a new thread
Explanation Packet server was unable to detach from a new thread.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-FSVFAIL [chars]: fsv_register for name=[chars] failed, error : [dec]
Explanation An automatic register for one of the FSVs failed.
Recommended Action If any of these messages occur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-GET_RENDEZVOUS msg_chan_get_rendezvous failure: [chars].
Explanation msg_chan_get_rendezvous failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-GETNODENAMEFAIL failed to get node name in pakman server init
Explanation packet manager server unable to retrieve the hostname for node/linecard.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-GETPIDFAIL Failed to get client's pid at [chars]
Explanation Packet Server failed to get the client's pid. This will prevent the client from connecting to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-HSSDFAIL [chars]: hssd_register for name=[chars],size=[dec] failed, error : [dec]
Explanation An automatic register for one of the HSSDs failed.
Recommended Action If any of these messages occur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-INITFAIL Packet server initialization failed. Reason : [chars]
Explanation The packet subsystem was not able to initialize properly. It will be restarted by sysmgr and should recover.
Recommended Action If packet manager is unable to start up after several restarts by sysmgr, please collect the 'sh log' output and contact your customer support representative.
Error Message%PKT_INFRA-PAKSRV-7-MSGREPLYFAIL Failed to reply to client [dec] message [dec] at [chars]
Explanation Packet server failed to reply to a client's request. This will result in the client getting blocked on packet server.
Recommended Action Restart the specified client. If the problem is not rectified, contact customer support.
Error Message%PKT_INFRA-PAKSRV-7-PAKBCASTFAIL Broadcast to clients from packet server failed
Explanation Packet server failed to broadcast to message to its clients that it is about to restart.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-PARTICLEINITFAIL Particle initialization failed.
Explanation Packet server was not able to initialize the particles correctly and will restart.
Recommended Action If the error is not rectified after two or more restarts, please call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-QSM_ADD_SERVICE qsm_add_service failure: [chars].
Explanation qsm_add_service failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-SIGALRM Received SIGALRM unexpectedly, ignored.
Explanation An unexpected signal SIGALRM was received.
Recommended Action If any of these messages occur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-SIGNAL signal: [chars].
Explanation The packet subsystem encountered an error while performing a signal operation.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-SYSMGR_GET_NODE_STATE Failed to get node state from Sysmgr: [chars].
Explanation Packet server failed to get node state from sysmgr.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-TIMER [chars]: timer: [chars].
Explanation The packet subsystem encountered an error while operating/handling a timer.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
PAKWATCH Messages
Error Message%PKT_INFRA-PAKWATCH-6-INFO Depletion level [dec] percent for resource [chars]:
Explanation The info about the current depletion level of the specified resource.
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-INFO_BODY [chars] [dec] [dec]
Explanation The resource depletion information in the following format: PROCESS_NAME PID COUNT
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-INFO_HEAD [chars] [chars] [chars]
Explanation The header for resource depletion information that follows this message. It is of the format: PROCESS_NAME PID COUNT
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-TRACEBACK [chars]
Explanation The traceback info about caller
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-USER_INFO Top [dec] users of [chars]:
Explanation The info about the top users of the specified resource.
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-USER_INFO2 Only [dec] users found using [chars].
Explanation The info about the total number of users of the specified resource.
Recommended Action It is an informational message.
PFI_IFH Messages
Error Message%PKT_INFRA-PFI_IFH-4-FAIL [chars]: [chars] ([hex])
Explanation An error occured in the ifh process. This may lead to problems elsewhere in the system.
Recommended Action If no further problems are seen, this warning may probably safely be ignored. If the message recurs, or problems are seen elsewhere in the system, take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PFI Messages
Error Message%PKT_INFRA-PFI-3-ASSERT Fatal error - assert condition [chars] failed - [chars] thread [dec]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
PLATFORM_C12000_NETIO_LIB Messages
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-GET_PPINDEX_INFO_FAIL Lookup for ppindex([dec]), pp_proto([dec]), failed due to [chars]
Explanation Unable to get the adjacency and next hop information from given ppindex.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked.
PLATFORM_HFR_NETIO_LIB Messages
Error Message%PKT_INFRA-PLATFORM_HFR_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_HFR_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
PLATFORM_LPTS_COM_IFIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in IFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG [chars]: Missing configuration for IFIB flow handling
Explanation No configuration for IFIB flow handling was found. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG_MEMORY [chars]: Insufficient memory for IFIB flow handling configuration
Explanation Insufficient memory was available for storing the IFIB flow handling configuration. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work. Debug message only. No action is required.
PLATFORM_LPTS_COM_NETIO Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_LPTS_LIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
PLATFORM_LPTS_PIFIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-BACKEND_EDM [chars]: EDM backend function [chars] failed: [chars]
Explanation An internal EDM backend function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-BAG [chars]: Bag function [chars] failed: [chars]
Explanation An internal bag function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CHKPT_INIT [chars]: Checkpoint Initialization function [chars] failed: [chars]
Explanation An internal Checkpoint function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_FLOW_MEMORY [chars]: Insufficient memory for flow configuration
Explanation There is insufficient memory for the flow configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in PIFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_MEMORY [chars]: Insufficient memory for policer configuration
Explanation There is insufficient memory for the policer configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_INVALID [chars]: Invalid parameter '[chars]' after '[chars]' in policer '[dec]' definition
Explanation There is an invalid parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_MISSING [chars]: Missing parameter after '[chars]' in policer '[dec]' definition
Explanation There is a missing required parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in policer '[dec]' definition
Explanation There is an unknown keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_UNDEFINED_POLICER [chars]: flow '[chars]' references undefined policer '[dec]'
Explanation An input flow definition references an undefined policer. The flow will be configured to use policer 0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_OPEN [chars]: could not open event connection: [chars]
Explanation An internal error was detected when trying to open event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_ADD_FEAT2GRP [chars]: fm add feat to group failed for ISIS [chars]
Explanation An internal fm add feature to group function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_ADD_IFH2GRP [chars]: fm add ifh to group failed for ISIS [chars]
Explanation An internal fm add ifh to group function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_CREATE_GROUP [chars]: fm create group failed: [chars]
Explanation An internal fm create group function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_FEAT_PROCESSING [chars]: fm feature registration failed: [chars]
Explanation An internal fm feature registration function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_REGISTER [chars]: fm_register failed: [chars]
Explanation An internal fm_register function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-HFA_REGISTER [chars]: hfa_register failed: [chars]
Explanation An internal hfa_register function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-LTRACE_INIT [chars]: ltrace_init2 failed: [chars]
Explanation An internal ltrace_init2 function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSG_ATTACH [chars]: Event Mgr function [chars] failed: [chars]
Explanation An internal Event Manager function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-NO_CONFIG [chars]: Missing configuration for PIFIB flow handling
Explanation No configuration for PIFIB flow handling was found. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_CLOSE [chars]: Cleanup for EDM failed: [chars]
Explanation Cleanup for EDM failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_INIT [chars]: Initialization for show EDM failed: [chars]
Explanation Initialization for show EDM failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SYSDB [chars]: Sysdb function [chars] failed: [chars]
Explanation An internal sysdb function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_FMT_TO_HFA_MAP [chars]: vmr_builder_program_tcam_fmt_from_hfa_map failed: [chars]
Explanation An tcam format to hfa mapping function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_IFH_UIDB_INDEX Failed to find uidb index for interface handle [hex]
Explanation Failed to find uidb index for an given interface handle. It is likely to be caused by a programming bug or a programming problem happened in the past.
Recommended Action Run the command 'show uidb index' to verify whether the uidb index is created for the interface. 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 provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action When this issue happens, it will trigger an automatic restart. This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_NOTIF_Q_FULL The queue for notifications from [chars] is full
Explanation Too many notifications have been sent to the component. The queue to hold the notification has overflowed.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_MSTATS_ALLOC Failed to allocate HW counters.
Explanation It failed to allocate HW counters. It may be because of running out of HW counters or encountering internal error.
Recommended Action Disable the numbers of non crucial services which use HW counters.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_INVALID_REG_NAME Found the Pre-IFIB region with unrecognized name: [chars]
Explanation A Pre-IFIB region with unrecognized name is found in the TCAM. It is likely caused by a programming bug or a programming problem happened in the past.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_OVERFLOW Does not have enough space for the Pre-IFIB entry in TCAM region [chars]
Explanation TCAM space is not enough for all Pre-IFIB entries in the particular TCAM region. All control packets which do not have matching Pre-IFIB entries in TCAM will use SW path to forward to destinations.
Recommended Action Disable the numbers of services configured for the system.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_PREFIX_COMPRESS Failed to have IPv6 prefix compressed
Explanation IPv6 prefix compression failed because the line card has run out of internal resources for compressing a preifx. It shouldn't have any major impact on the system service. The in-bound (destined to the system) packets can still reach destinations through SW path.
Recommended Action Try either change the prefix length or change the prefix value of IPv6 addressses used in the system if possible.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT Failed to connect to [chars]: [chars]
Explanation An internal error was detected when trying to connect to the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of the respective component because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT [chars]: [chars]
Explanation An internal error was detected when trying to set up event connection.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_ATTACH Could not set up a timer object: [chars]
Explanation An internal error was detected when trying to allocate a timer object.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_LEAF_NEW Could not create a timer tree leaf objct: [chars]
Explanation An internal error was detected when trying to create a timer tree leaf object.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_INIT_POLICERS Failed to initialize the flow policer [dec]: [chars]
Explanation It failed to program a flow policer during initialization.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_LTRACE_INIT Failed to initialize the ltrace buffer
Explanation An internal error was detected when trying to initalize a ltrace buffer.
Recommended Action When this issue happens, it will not able to use ltrace buffer for debugging. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_INIT Failed to initialize with Metro IPC Server: [chars]
Explanation An internal error was detected when trying to initialize with Metro IPC server.
Recommended Action Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_NOTIF_ACK Failed to acknowledge a MIPC notification: [chars]
Explanation It is an internal error which the system failed to acknowledge a MIPC Server notification.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_MSTATS_INIT Failed to initialize stats table: [chars]
Explanation An internal error was detected when trying to initialize a statistic counter table.
Recommended Action Check the status of Metro Stats Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_NOTIF_HANDLE Failed to handle [chars] notification: [chars]
Explanation An internal error was detected when trying to handle a notification from the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_PROGRAM_ERRORED_POLICER Failed to reprogram the flow policer [dec]: [chars]
Explanation An internal error was detected when trying to program the flow policer.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_REPROGRAM_POLICERS Failed to program the flow policer [dec]: [chars]
Explanation It failed to reprogram a flow policer when it had received a request to reprogram all flow policers to HW.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_SYSDB_DATALIST_CREATE Sysdb datalist function failed to create an object handle: [chars]
Explanation An internal sysdb function failed.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_TCAM_INIT Failed to initialize TCAM regions: [chars]
Explanation An internal error was detected when trying to initialize TCAM regions.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_PFI Messages
Error Message%PKT_INFRA-PLATFORM_PFI-4-IFHANDLE_DECODE Could not map handle [hex] to slot
Explanation The interface handle cannot be mapped to a slot on the card.
Recommended Action Debug message only. *DEBUG*
Error Message%PKT_INFRA-PLATFORM_PFI-4-INIT Failed to initialise [chars]
Explanation An error occured when a module was going to be initialised. This may cause the process to terminate.
Recommended Action Restarting the process might help.
PROTECT_NOTIFY Messages
Error Message%PKT_INFRA-PROTECT_NOTIFY-3-DRIVER_CONFIG Config of i/f driver to generate fast notifictaions failed: [chars] - [chars]
Explanation Configuration of interface driver to generate traffic protection fast notifications failed. Fast (e.g. sub 50ms) protection is not available for interfaces on the affected linecard. Note that while the traffic fast protection is affected in terms of speed, in the absence of additional errors the corresponding protection method (e.g. MPLS TE FRR) should still protect, but at much slower (over 50ms) speeds.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PROTECT_NOTIFY-3-TRIGGER Fast protection trigger failed: [chars] - [chars]
Explanation Fast protection trigger failed for reasons as specified. Note that while the traffic fast protection is affected in terms of speed, in the absence of additional errors the corresponding protection method (e.g. MPLS TE FRR) should still protect, but at much slower (over 50ms) speeds.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PROTECT_NOTIFY-6-CLIENT_INIT Init of notifications client failed: [chars] - [chars]
Explanation Initialization of traffic protection fast notifications client failed. This can happen during normal operation due to a non-optimal initialization order. As client re-tries the initialization this message can be ignored. However if this message repeats for prolonged period of time or if more severe messages are observed the fast (e.g. sub 50ms) protection may become not available for interfaces protected by this client. Note that even if fast protection becomes not available, the corresponding protection method (e.g. MPLS TE FRR) should still protect, but at much slower (over 50ms) speeds.
Recommended Action Monitor for repetition of this message or presence of more severe errors.
Error Message%PKT_INFRA-PROTECT_NOTIFY-7-SERVER_INIT Init of notifications server failed: [chars] - [chars]
Explanation Initialization of traffic protection fast notifications server failed. Fast (e.g. sub 50ms) protection is not available for interfaces on the affected linecard. Note that while the traffic fast protection is affected in terms of speed, in the absence of additional errors the corresponding protection method (e.g. MPLS TE FRR) should still protect, but at much slower (over 50ms) speeds.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SVII_ADJ_LIB Messages
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-ADJ_DATA_CORRUPT The SVI Adjacency Manager was provided with corrupt adjacency data for [chars] SSC belonging to service [chars] on location [chars]
Explanation Either the active or standby Service State Controller for the location given in the message provided the Adjacency Manager with corrupt data. This most likely indicates a bug in the Service State Controller logic. No adjacencies will be installed for the named service, so no traffic will be forwarded to or from it.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-FOLLOW_STANDBY_MISMATCH The SVI Adjacency Manager was provided with conflicting settings for installing adjacencies for interface [hex]
Explanation Conflicting 'follow standby' instructions were supplied to the Adjacency Manager for an interface. 'Follow standby' is specified for an interface by a Service State Controller if it believes that traffic should be directed towards the standby, rather than active, service instance. This message indicates that the active and standby Service State Controllers gave conflicting information about where traffic to be directed to. This indicates an inconsistency between the system state as viewed by the Service State Controllers that are responsible for the service to which the interface belongs. Restarting those processes may help, after allowing any other problems that could lead to inconsistencies being resolved. No adjacencies will be installed for the interface, and all traffic to it will be dropped.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars]
Explanation The SVI Adjacency Manager Library's initialization has failed. The process will exit and automatically restart.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-SERVICE_FAILED An error occurred while setting up adjacencies for service '[chars]': [chars]
Explanation The SVII Adjacency Manager encountered an error while preparing to set up adjacencies for the specified service. It is likely that packets will not be forwarded to interfaces for that service. This may be caused by a lack of resources or other system problems. Restarting the 'svi_adj_mgr' process on the affected node (after any other problems have been cleared up) will restore adjacencies for the affected service.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-INTF_DB_INCONSISTENT An inconsistency has been found in the interface database (interface handle [hex])
Explanation An inconsistency has been found in the adjacency manager interface database. The adjacency manager will automatically recover from this; nevertheless it may indicate a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-REFRESH_FAILED An error occurred while requesting adjacency refresh for service '[chars]': [chars]
Explanation The SVII Adjacency Manager encountered an error while resynchronising its adjacencies. The adjacencies for the specified service may not be correctly set up on the specified card, meaning that traffic for that service arriving at that card may not be forwarded correctly.
Recommended Action Restarting the 'svi_adj_mgr' process on the affected node (after any other problems - such as lack of memory - have been cleared up) will restore adjacencies for the affected service. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-RESTART_FAILED An error occurred while trying to restart cleanly: [chars]
Explanation The SVII Adjacency Manager encountered an error while preparing to restart itself. It will restart itself anyway, but there may be other errors.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-SDIR_INVALID The Service Director library passed invalid parameters to the SVII Adjacency Manager process.
Explanation The Service Director process/library sent an invalid message to the SVII Adjacency Manager. This indicates a problem with the Service Director. It is likely that packets will not be correctly forwarded to some Service Virtual Interfaces.
Recommended Action It may help to restart the SVII Adjacency Manager and/or the Service Director processes. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-SRV_CLEANUP_FAILED The SVI Adjacency Manager 'publish' library encountered an error when trying to clean up after a service unregistered. Error [chars]
Explanation A Service owner tried to revoke a request for adjacencies to be managed by the SVI Adjacency Manager. It is likely that the originally published request has not been cleaned up correctly. This should not have any adverse effects, other than the use of some additional resouces, but probably indicates some kind of programming error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SVII_ADJ_MGR Messages
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-ADJ_FAILED An error occurred while trying to program an adjacency: [chars] (interface handle=[hex])
Explanation The SVII Adjacency Manager encountered an error while programming an adjacency. Packets may not be forwarded to the affected service interface. The name of the interface can be retrieved with 'show im chains ifhandle 0xabc', where '0xabc' is the interface handle shown in the message.
Recommended Action This error should only arise due to resource constraints (eg memory). Determine which resources are short, and make more available; then restart the 'svi_adj_mgr' process on the affected node.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-ECM_ERROR_FAILED An error occurred while trying to recover from a previous failure: [chars]
Explanation The SVII Adjacency Manager encountered an error while calling AIB. Normally, it would recover from this error. However, a secondary failure has occurred while invoking the recovery mechanism. After this error, packets may not be forwarded correctly for some service virtual interfaces.
Recommended Action The system can be recovered by restarting the 'svi_adj_mgr' process on the affected node. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars]
Explanation The SVI Adjacency Manager's initialization has failed. The process will exit and automatically restart.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-LOOP_FAILED Event Loop failed, error: [chars]
Explanation The SVII Adjacency Manager encountered an error while waiting for an event. This should not ordinarily happen, but may indicate a temporary glitch that will automatically recover. If it occurs very frequently it may be necessary to restart the SVII Adjacency Manager process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-RECEIVE_MESSAGE An error occurred whilst processing a '[chars]' message from a client, during operation [chars]: [chars]
Explanation The process encountered an error while trying to handle a message from a Service on a line card. If this happens frequently, then restarting the process that caused the error may fix the problem. It may indicate that the card is low on memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-SYSMGR Failure communicating readiness to System Manager. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-4-RESTART A failure occured while re-syncing state with AIB after a restart: [chars]
Explanation After a restart, the adjacency manager attempts to re-sync its state with AIB. A failure occurred during this process. This could result in adjacencies being erroneously deleted in AIB, and hence forwarding could be interrupted.
Recommended Action Wait five minutes, then restart the adjacency manager again by entering the command: 'process restart svii_adj_mgr location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-6-CERRNO_FAILED Error registration failed ([chars]) - some messages may not be displayed correctly
Explanation The SVI Adjacency Manager encountered an error while registering its error messages. Some error messages may be displayed numerically rather than with full messages. No other problems will be caused by this failure.
Recommended Action No action need be taken.
TCAM_MGR_LIB Messages
Error Message%PKT_INFRA-TCAM_MGR_LIB-3-INTERNAL_ERR Internal error: [chars]
Explanation An internal error occurred in TCAM Manager which involves exiting the process. After the TCAM Manager process restarts, the error should have been cleared. *DDTS*
Recommended Action Collect the configuration, syslog and coredump file. Attach them to the ddts. After the process restarts automatically, the error should have been cleared and no user action is needed.
Error Message%PKT_INFRA-TCAM_MGR_LIB-3-V6_CMPR_FAILED v6 source prefix compression failed: [chars]
Explanation V6 source prefix compression failed due to lack of extended path. This failure indicates that a particular v6 prefix indicated in the message will not be compressed. There are 3 workarounds of this problem. 1) do not use this entry. 2) change the prefix length. 3) change the prefix value. For example if an entry failed during an ACL programming then try removing that ACE indicated in the message and apply the configuration again. *DDTS*
Recommended Action Ouput generated by this message and related config, for example v6 ACL failed in case of ACL configuration. Attach them to the ddts. This failure indicates that a particular v6 prefix indicated in the message will not be compressed. There are 3 workarounds of this problem. 1) do not use this entry. 2) change the prefix length. 3) change the prefix value. For example if an entry failed during an ACL programming then try removing that ACE indicated in the message and apply the configuration again.
TNODE Messages
Error Message%PKT_INFRA-TNODE-3-CAPS_LOOKUP Capsulation lookup failed : [chars]
Explanation im_caps_lookup() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-CHAN_CREATE Failed to create channel : [chars]
Explanation Failed to create a channel using event_manager_create.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-EVENT_INIT IM to initialize linecard dpf notification event : [chars]
Explanation event_init_event() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-GET_RP_SLOT Failed to get RP slot number : [chars]
Explanation primary_rp_slot_number() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IF_FIND Failed to obtain interface handle ([chars]) : [chars]
Explanation im_interface_find() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IM_CTRLSVR_BIND Failed to bind to IM control server : [chars]
Explanation im_control_server_bind() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IM_DATAPATH_CTRL IM datapath control failed : [chars]
Explanation im_caps_datapath_control() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IM_DATASVR_BIND Failed to bind to IM data server : [chars]
Explanation im_data_server_bind() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-LC_CONN_CREATE Failed to create transit-node lc connection : [chars]
Explanation event_conn_create() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-LC_CONN_OPEN Failed to open transit-node lc connection : [chars]
Explanation event_conn_open() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-PROC_RDY Failed to notify System Manager (Ready) : [chars]
Explanation sysmgr_proc_ready() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-SYSDB_BIND Failed to bind to SysDB : [chars]
Explanation sysdb_bind() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-SYSDB_COID Failed to obtain the file descriptor from SysDB connection : [chars]
Explanation sysdb_conn_to_coid() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-SYSDB_REG Failed to register for notification for dpf events : [chars]
Explanation sysdb_register_notification() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
TUNNEL Messages
Error Message%PKT_INFRA-TUNNEL-1-RESOURCES Could not program hardware resources for interface [chars]
Explanation Some hardware resource could not be programmed. The reason details which resource failed
Recommended Action Ensure that enough resources are available. The user may have to unconfigure some resources, and then will have to reapply the xconnect configuration.
Error Message%PKT_INFRA-TUNNEL-3-API_ERR The [chars] API function to [chars] returned the following error: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-API_ERROR [chars]: [chars] - error ([hex]): [chars]
Explanation The specified API returned the specified error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-API_ERROR_2 [chars]: [chars] - error: [chars]
Explanation The specified API returned the specified error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-BAD_CHAIN Invalid chain type ([dec])
Explanation An invalid chain type was received by the chain builder. This is an internal error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-BAD_CHECKSUM Bad checksum - computed = [hex], received = [hex]
Explanation Mismatch in received/computed checksum was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-BAD_KEY Incorrect key - received: [dec], expected: [dec]
Explanation A packet was received with a bad key.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-CONFIG_SCAN_FAILED [chars]: item [chars]: [chars]
Explanation An unexpected error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-CURRENT_MAXIMUM_HIGH Current maximum [dec] exceeds absolute maximum [dec]
Explanation New current maximum is larger than the absolute max.
Recommended Action Use a current maximum value which is lower than the abosulte max value.
Error Message%PKT_INFRA-TUNNEL-3-CURRENT_MAXIMUM_LOW New current max [dec] is lower than the number of tunnels currently configured [dec].
Explanation New current max is lower than the current tunnel count.
Recommended Action Use a current maximum value which is lower than the current tunnel count.
Error Message%PKT_INFRA-TUNNEL-3-CURRENT_MAXIMUM_REACHED tunnel-[chars]: Current Maximum # of configured tunnels reached [dec]
Explanation Tunnel Count has reached the current maximum limit.
Recommended Action Use the 'maximum tunnel-te ' config CLI to increase the current maximum value.
Error Message%PKT_INFRA-TUNNEL-3-GENERIC [chars]
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-IM_ERR The interface manager API function to [chars] returned the following error: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-IMP_ERROR Unknown condition code received from imp: ([dec])
Explanation The specified condition code was received from imp.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-INIT_FAIL Tunnel process initialization failed while [chars] with error: [chars]
Explanation The tunnel process responsible for the creation of tunnel interfaces failed during initialization. The process will exit and as a result, no tunnel interfaces can be configured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-INVALID_IDB datapath_control information for unknown IDB
Explanation A datapath_control message was received for an unknown interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-LOOPING Encapsulation looping detected: inner: [chars], outer: [chars]
Explanation An encapsulation loop was detected.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-NEGATIVE_CURRENT_COUNT tunnel-[chars]: current tunnel count became negative, restarting
Explanation Tunnel count has been decremented till it became negative. process tunnel_infra will restart to recover from the situation.
Recommended Action Ideally this should never happen and points to a serious bug in pfi/tunnel/infra File a tracking DDTS if it happens.
Error Message%PKT_INFRA-TUNNEL-3-NO_IDB IDB not available in context
Explanation Could not find the tunnel IDB in the context structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-NO_INTERFACE Interface [chars] does not exist to delete
Explanation A request to delete a non-existent interface has been received. This is relatively a harmless error, unless it is too frequent, in which case the reason for the error must be investigated, starting with the name of the interface printed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-NULL_DPC NULL DPC received
Explanation The EA received a datapath control with NULL input data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-NULL_NEXT ip_fib_soutput returned NULL en_next: fail code: [dec]
Explanation The decapsulated packet could not be forwarded. This is an internal error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-ROUTING GRE tunnel packet received with source routing
Explanation A GRE tunnel packet with the source routing option was received.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-SEQUENCE GRE tunnel packet received with sequence option
Explanation A GRE packet was received with the sequence option.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-SOCKET Socket op [chars] failed: [chars]
Explanation The specified socket operation failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_GRE_TUNNEL Packet received for unknown tunnel or bad key. Source: [chars], Destination: [chars], Key: [dec]
Explanation A GRE tunnel packet was received for a tunnel that is not configured in this router or there was a key mis-match.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_HANDLE IDB for interface [hex] not found
Explanation The EA received a datapath control indication for an unknown interface handle
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_IPIP_TUNNEL Packet received for unknown tunnel. Source: [chars], Destination: [chars]
Explanation An IPinIP tunnel packet was received for a tunnel that is not configured in this router.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_MSG Received unexpected message opcode [dec] in Interface Manager handler
Explanation An unexpected message was received by this process. This is relatively a harmless error and should not have any immediate impact on the operation of tunnel interfaces. It must still be reported and looked into.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_PROTOCOL Unknown protocol [dec] received by the gre socket handler
Explanation A packet with an unknown protocol type was passed to the GRE socket handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNSUPPORTED_CODE_RCVD Unsupported code received ([dec])
Explanation An unexpected error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNSUPPORTED_PROTOCOL An unsupported protocol type [dec] received in GRE tunnel
Explanation An GRE tunnel packet was received with an unsupported protocol type as the payload.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-VERSION GRE tunnel packet received with bad version number ([dec])
Explanation A GRE tunnel packet was received with a bad version number.
Recommended Action NONE*
Error Message%PKT_INFRA-TUNNEL-3-ZERO_HEADER Encapsulation IP header length is zero
Explanation The length of the tunnel encapsulating header is zero.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-6-DEBUG_ERROR Invalid value [dec] for debug
Explanation An invalid value was received for the debug flag.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-7-IFACE_NOT_UP Packet received on tunnel whose interface is not up
Explanation A packet was received on a tunnel whose interface status is not up.
Recommended Action No action is required.
VI_REPL Messages
Error Message%PKT_INFRA-VI_REPL-3-NAMESTRING Failure during initialization of virtual interface namestring [chars] for replication. [chars]. Error: [chars].
Explanation A failure occurred during the registration of a virtual interface namestring for replication.
Recommended Action The process will attempt to recover from this error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-VI_REPL-3-REPLICATE Virtual Interface config replication failed. [chars]. Error: [chars].
Explanation A failure occurred during the replication of an item of virtual interface configuration to one or more of the backup RPs.
Recommended Action The process will restart and attempt to recover from this error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-VI_REPL-7-EVENT Unrecoverable error in event loop. Error: [chars]
Explanation An unhandled error occured while waiting for an event.
Recommended Action The process will restart and attempt to recover from this problem. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-VI_REPL-7-INIT Failed to intialize config replicator. [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the Virtual Interface Config Replicator process.
Recommended Action The vi_config_replicator process will restart and attempt to recover from this error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.