-
Cisco IOS XR System Error Reference Guide for Platform Independent Messages, Release 3.3
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Default Messages
-
Diagnostic Messages
-
Forwarding Information Base Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 (L1) Messages
-
Layer 2 (L2) Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QOS) Messages
-
Routing Messages
-
Security Messages
-
Service Messages
-
Simple Network Management Protocol (SNMP ) Messages
-
System Database Messages
-
Feedback
Table Of Contents
Packet Infrastructure 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:
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,
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 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 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 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,
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,
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 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 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 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.
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.
FIB_IPV4 Messages
Error Message%PKT-INFRA-FIB_IPV4-3-GEN_ERR FIB IPV4 internal error: [chars]
Explanation An internal software error occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FIB_IPV4-5-RECURSIVE_LOOP FIB IPv4 Recursive loop: [chars]
Explanation Recursive loop was detected. The route update will be dropped
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FIB_IPV6 Messages
Error Message%PKT_INFRA-FIB_IPV6-3-GEN_ERR FIB IPV6 internal error: [chars]
Explanation An internal software error occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FIB_IPV6-5-RECURSIVE_LOOP FIB IPv6 Recursive loop: [chars]
Explanation Recursive loop was detected. The route update will be dropped
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-2-SYSTEM_FAIL [chars]: [chars] errno=[dec] [chars]
Explanation There was a system/os call failure resulting in a failure to provide some system 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-EVENT_REGISTRATION_FAILED FM failed to connect to the event manager: [chars]
Explanation The FM 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-FM-3-FGID_BITMASK_READ [chars]: failed to translate FGID to GSR bitmask: [chars]
Explanation Failed to translate FGID to GSR bitmask.
Recommended Action Copy the error message exactly as it appears on the 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-HSSD_REGISTER_FAILED Failed to register for packet HSSD [chars]
Explanation Fatal failure to register for the packet HSSD
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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-PLATFORM_IFIB_RES_GET [chars]: failed to get platform-specific IFIB result field [chars]
Explanation Failed to get platform-specific IFIB result field.
Recommended Action Copy the error message exactly as it appears on the 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-PLATFORM_IFIB_RES_PRINT [chars]: failed to print platform-specific IFIB result field [chars]
Explanation Failed to print platform-specific IFIB result field.
Recommended Action Copy the error message exactly as it appears on the 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-SYSDB_BIND_FAILED Failed to connect to SysDB in [chars] ([chars])
Explanation Failed to connect to SysDB while starting 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-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.
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_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 interface ([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 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 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 interface ([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.
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-DOWNLOAD_FAILED Initial [chars] download to nodeid [hex] [chars] failed over [chars]: [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-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.' 'Copy the error message exactly as it appears on the 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-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-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.
Error Message%PKT_INFRA-IMAEDM-7-SYSDB_EDM_REGISTER_FAILED [chars]: Can't register EDM to SysDB at [chars]: [chars]
Explanation The sysdb_register_edm function reported an 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.
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] (count=[dec] members=[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-1-BIND_FAILURE Failed to bind to SysDB. Error: [chars]
Explanation Process failed to bind to SysDB during initialization.
Recommended Action Restart 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-INTERFACE_CONFIG-1-EVENT_BLOCK_ERROR An error occurred whilst awaiting another event. Error: [chars]
Explanation Process received an error during the event loop.
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-1-EVM_CREATE_FAILURE Failed to create event manager; error: [chars]
Explanation Process failed to create an event manager during initialization.
Recommended Action Restart 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-INTERFACE_CONFIG-1-PROC_READY_FAILURE Failed to signal process ready to sysmgr; error: [chars]
Explanation Process failed to signal that it had completed initialization to the system manager.
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-3-BADINTFNAME Unknown interface name
Explanation An internal error was detected within the interface config process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show running-config 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 running-config output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-3-INIT_FAILURE Initialisation failure during [chars]: error [chars]
Explanation Process failed during initialisation
Recommended Action No action is required.
Error Message%PKT_INFRA-INTERFACE_CONFIG-3-SET_DEFAULT_ERR Couldn't reset MAC address value. Error [chars]
Explanation Could not reset MAC address value to default.
Recommended Action An error has occured while setting the default value. Copy the error message exactly as it appears on the console or in the system log. Issue the show running-config 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 running-config output, 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. Error [chars]
Explanation Could not set MAC address value.
Recommended Action An error has occured while setting the default value. Copy the error message exactly as it appears on the console or in the system log. Issue the show running-config 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 running-config output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-3-VERIFICATION_FAILURE Could not install verifier for [chars] error [chars]
Explanation Process couldn't register for verification
Recommended Action No action is required.
Error Message%PKT_INFRA-INTERFACE_CONFIG-6-EXITTING Process has encountered an error and is exitting.
Explanation The process encountered an error of some kind, and as a result cannot continue. Process will exit.
Recommended Action The process should automatically 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.
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.
Error Message%PKT_INFRA-LPTS_LIB-7-NO_MEM [chars]: not enough memory: [chars]
Explanation Allocating memory failed due to a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
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-3-GROUP_CREATE [chars]: failed to create a group: [chars]
Explanation An internal error was detected when creating group.
Recommended Action Copy the error message exactly as it appears on the 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-3-GROUP_LEAVE [chars]: failed to leave a group: [chars]
Explanation An internal error was detected when leaving group.
Recommended Action Copy the error message exactly as it appears on the 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-3-GROUP_SEND [chars]: failed to send message to group: [chars]
Explanation An internal error was detected when trying to send a message to group.
Recommended Action Copy the error message exactly as it appears on the 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-3-NO_MEM [chars]: not enough memory: [chars]
Explanation Failed to allocate memory.
Recommended Action Copy the error message exactly as it appears on the 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_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-PIFIB_LIST_ADD [chars]: failed to add an entry into Pre-IFIB entry list: [chars]
Explanation An internal error was detected when trying to add an entry into the Pre-IFIB entry 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_PA_FF-3-PIFIB_LIST_DELETE [chars]: failed to delete an entry from Pre-IFIB entry list: [chars]
Explanation An internal error was detected when trying to delete an entry from the Pre-IFIB entry 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_PA_FF-3-PIFIB_UPD_OPCODE [chars]: invalid Pre-IFIB update opcode: [dec]
Explanation The Pre-IFIB update request has an invalid Pre-IFIB update opcode.
Recommended Action Copy the error message exactly as it appears on the 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-SYSMGR_GET_JOB_ID [chars]: failed to get my own job id: [chars]
Explanation An internal error was detected when trying to get the process's own job id.
Recommended Action Copy the error message exactly as it appears on the 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_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_REG [chars]: failed to register EDM: [chars]
Explanation An internal error was detected when trying to register 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-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 [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-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_DETACH [chars]: could not set up a managed timer identifier: [chars]
Explanation An internal error was detected when trying to remove a managed timer registration from 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-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-IF_RESOLVE [chars]: Error '[chars]' while trying to resolve interface handle: [hex]
Explanation Couldn't resolve 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-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-IM_CAPS_LOOKUP [chars]: failed to find the capsulation number from the given name: [chars]
Explanation An internal error was detected when trying to find the capsulation number from the given name.
Recommended Action Copy the error message exactly as it appears on the 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_CONTROL_SERVER_BIND [chars]: failed to connect to Interface Manager control server: [chars]
Explanation An internal error was detected when trying to establish the connection with the Interface Manager control 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-IM_DATA_SERVER_BIND [chars]: failed to connect to Interface Manager data server: [chars]
Explanation An internal error was detected when trying to establish the connection with the Interface Manager data 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-IM_DATA_SERVER_UNBIND [chars]: failed to disconnect from Interface Manager data server: [chars]
Explanation An internal error was detected when trying to tear down the connection with the Interface Manager data 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-IM_PROTOCOL_LOOKUP [chars]: failed to find the protocol number from the given name: [chars]
Explanation An internal error was detected when trying to find the protocol number from the given name.
Recommended Action Copy the error message exactly as it appears on the 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_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_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-NULL_FINT_IDB [chars]: failed to get forwarder interface IDB
Explanation An internal error was detected when trying to get forwarder interface IDB.
Recommended Action Copy the error message exactly as it appears on the 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_CLOSE [chars]: failed to disconnect from the Port Arbitrator as a Flow Forwarder: [chars]
Explanation An internal error was detected when trying to disconnect from 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_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-PLATFORM_IFIB_RES_GET [chars]: failed to get platform-specific IFIB result: [chars]
Explanation An internal error was detected when trying to get platform-specific IFIB result.
Recommended Action Copy the error message exactly as it appears on the 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-PLATFORM_IFIB_RES_PRINT [chars]: failed to print platform-specific IFIB result: [chars]
Explanation An internal error was detected when trying to print platform-specific IFIB result.
Recommended Action Copy the error message exactly as it appears on the 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-2-ERR_BIND_IFFILTER [chars]: binding of interface filter failed. result = [chars]
Explanation An internal error was detected when trying to bind interface filter 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_BAD_CLIENT_ID [chars]: invalid client id [dec]
Explanation Detected an invalid LPTS client ID.
Recommended Action Copy the error message exactly as it appears on the 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_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_BIND_PAKFILTER [chars]: binding of packet type filter failed. result = [chars]
Explanation An internal error was detected when trying to bind packet type filter 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_BIND_SPOLICY [chars]: binding spolicy failed. result = [chars]
Explanation An internal error was detected when trying to bind static policy 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_CB_NULL_PA_HANDLE [chars]: PA callback invoked with a Null handle
Explanation Detected a NULL PA handle in PA 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_CB_THREAD_INIT [chars]: couldn't create thread for PA event handling: [chars]
Explanation An internal error was detected when trying to create thread for PA event handling.
Recommended Action Copy the error message exactly as it appears on the 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_FGID_BITMASK_READ Failed to translate FGID to bitmask
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_FINT_IDB Driver not bound to 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_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_FM_LOOKUP flow manager lookup failed, 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_FRAG_RCVD punt back of fragment detected
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_GET_IP_ADDR couldn't get the IP addresses off the 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_GET_IP_EMBEDDED_HDR couldn't get the information in embedded transport header of the 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_GET_IP_PORT couldn't get the L4 ports or ICMP/IGMP type off the 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_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_HSSD_REG [chars]: registering HSSD failed: [chars]
Explanation An internal error was detected when trying to register an HSSD.
Recommended Action Copy the error message exactly as it appears on the 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_IF_FILTER [chars]: Null interface filter
Explanation Detected a NULL interface filter.
Recommended Action Copy the error message exactly as it appears on the 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_IF_HANDLE [chars]: couldn't get input interface handle: [chars]
Explanation An internal error was detected when trying to get input interface handle of a 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-LPTS-3-ERR_IFFILTER_ADD [chars]: couldn't add interface filter binding to PA: [chars]
Explanation An internal error was detected when trying to add interface filters 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_IFFILTER_DELETE [chars]: couldn't delete interface filter from PA: [chars]
Explanation An internal error was detected when trying to delete interface filters from 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_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_DEB_INIT lpts netio ifib 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_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_GET failed to get [chars] from IFIB result
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_INVALID_PROTO_FAM [chars]: invalid protocol family number [dec]
Explanation Detected an invalid protocol family number.
Recommended Action Copy the error message exactly as it appears on the 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_MEM_ALLOC [chars]: couldn't allocate memory for [chars]
Explanation An internal error was detected when trying to allocate memory.
Recommended Action Copy the error message exactly as it appears on the 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_PAK [chars]: Null pak
Explanation Detected a NULL packet pointer.
Recommended Action Copy the error message exactly as it appears on the 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_PCB [chars]: Null PCB
Explanation Detected a NULL PCB.
Recommended Action Copy the error message exactly as it appears on the 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_PTR [chars]: the pointer to [chars] is NULL
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_SOCKET [chars]: Null socket
Explanation Detected a NULL socket.
Recommended Action Copy the error message exactly as it appears on the 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_ADD_BINDING [chars]: couldn't add binding to PA: [chars]
Explanation An internal error was detected when trying to add bindings 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_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_PA_DELETE_BINDING [chars]: couldn't delete binding from PA: [chars]
Explanation An internal error was detected when trying to delete bindings from 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_REPLAY_BINDINGS [chars]: Replay of bindings failed: [chars]
Explanation An internal error was detected when trying to replay bindings 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_PA_UPDATE_IFFILTER [chars]: couldn't update interface filter binding to PA: [chars]
Explanation An internal error was detected when trying to update interface filter binding 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_PA_UPDATE_PAKFILTER [chars]: couldn't update packet type filter binding to PA: [chars]
Explanation An internal error was detected when trying to update packet type filter binding 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_PA_UPDATE_SPOLICY [chars]: couldn't update static policy binding to PA: [chars]
Explanation An internal error was detected when trying to update static policy binding 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 [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_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_PAKFILTER_ADD [chars]: couldn't add packet type filter binding to PA: [chars]
Explanation An internal error was detected when trying to add packet type filters 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_PAKFILTER_DELETE [chars]: couldn't delete packet type filter from PA: [chars]
Explanation An internal error was detected when trying to delete packet type filters from 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_PCB_CREATE_IFFILTER [chars]: couldn't create PCB interface filter list: [chars]
Explanation An internal error was detected when trying to create PCB interface filter 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_PCB_CREATE_PAKFILTER [chars]: couldn't create PCB packet type filter list: [chars]
Explanation An internal error was detected when trying to create PCB packet type filter 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_PCB_CREATE_SPOLICY [chars]: couldn't create PCB static policy list: [chars]
Explanation An internal error was detected when trying to create PCB static policy 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_PCB_UPDATE_IFFILTER [chars]: couldn't update PCB interface filter list: [chars]
Explanation An internal error was detected when trying to update PCB interface filter 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_PCB_UPDATE_PAKFILTER [chars]: couldn't update PCB packet type filter list: [chars]
Explanation An internal error was detected when trying to update PCB packet type filter 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_PCB_UPDATE_SPOLICY [chars]: couldn't update PCB static policy list: [chars]
Explanation An internal error was detected when trying to update PCB static policy 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_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_SET_LOCAL_FLAG failed to check if local flag of IFIB result need to be set for the 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_SOLOCK [chars]: failed to lock socket mutex: [chars]
Explanation An internal error was detected when trying to lock socket 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-LPTS-3-ERR_SOUNLOCK [chars]: failed to unlock socket mutex: [chars]
Explanation An internal error was detected when trying to unlock socket 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-LPTS-3-ERR_SPOLICY_ADD [chars]: couldn't add static policy binding to PA: [chars]
Explanation An internal error was detected when trying to add static policy 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_SPOLICY_DELETE [chars]: couldn't delete static policy from PA: [chars]
Explanation An internal error was detected when trying to delete static policy from 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_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-3-ERR_SYSDB_UNBIND [chars]: disconnecting from SysDB failed: [chars]
Explanation An internal error was detected when trying to unbind from 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-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
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:
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]
Explanation NetIO received a bad packet from the driver 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-2-SYSTEM_FAIL [chars]: [chars] errno=[dec] [chars]
Explanation There was a system/os call failure resulting in a failure to provide some system service.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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_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-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_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-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-3-HSSD_REGISTER_FAILED Failed to register for packet HSSD [chars]
Explanation Fatal failure to register for the packet HSSD
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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.
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.'
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_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-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-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_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-3-TX_ADJ_FAILED An error occurred while trying to program a transmit 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-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_MGR-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_MGR-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.
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.
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 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 Failure during replicate [chars] operation on item [chars]. Error: [chars].
Explanation A failure occurred during the replication of an item of virtual interface configuration to the standby RP.
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-VI_REPL-3-RETRY_SETUP Failure during setup of replicate retry ([chars]) Error: [chars].
Explanation A failure occurred during the setup of data structures for doing retries of previous failed configuration replication events to the standby RP.
Recommended Action The process will restart and try to resync the configuration of virtual interfaces from the active to the standby card. 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-4-LOST Lost retry of [chars] ([chars]) ([unsigned int] ops)
Explanation A failure occurred during configuration replication to the standby RP. The replication event was queued for retry, but there has been some event such as a failover which means the queued events have now been lost.
Recommended Action Check the configuration via show running configuration and reapply any configuration that is missing. Note: The missing configuration will only be for Virtual Interfaces. 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-6-RETRY Failure during replication ([chars]) Error: [chars]. The event will be queued for retry in [unsigned int] seconds
Explanation A failure occurred during configuration replication to the standby RP. The replication will be tried again after the specified time.
Recommended Action The process will try to resync the configuration of virtual interfaces from the active to the standby card. 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 error (other than EINTR) occured in the event loop. The process must exit.
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-VI_REPL-7-INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the Virtual Interface Config Replicator 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-VI_REPL-7-SYSDB_INIT Failure during intialization of SysDB connection. [chars]. Error: [chars].
Explanation A failure occurred during the initialization of the Virtual Interface Config Replicator connection to SysDB.
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-VI_REPL-7-SYSMGR Failure communicating readiness to SysMgr. 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.
