-
Cisco IOS XR System Error Message Reference Guide, Release 3.2
-
Preface
-
Cisco IOS XR System Error Messages Overview
-
Access Control List (ACL) Error Messages for Cisco IOS XR
-
Fabric (FABRIC) Error Messages for Cisco IOS XR
-
Hardware Accessibility (HA) Messages for Cisco IOS XR
-
Installation (INSTALL) Messages for Cisco IOS XR
-
Internet Protocol (IP) Messages for Cisco IOS XR
-
Layer 2 (L2) Messages for Cisco IOS XR
-
Media (MEDIA) Messages on Cisco IOS XR
-
Manageability (MGBL) Messages for Cisco IOS XR
-
Operating System (OS) Messages for Cisco IOS XR
-
Packet Infrastructure (PKT_INFRA) Messages for Cisco IOS XR
-
Platform (PLATFORM) Messages for Cisco IOS XR
-
Quality of Service (QOS) Messages for Cisco IOS XR
-
Routing (ROUTING) Messages for Cisco IOS XR
-
Security (SECURITY) Messages for Cisco IOS XR
-
Simple Network Management Protocol (SNMP) Messages for Cisco IOS XR
-
System Database (SYSDB) Messages for Cisco IOS XR
-
Feedback
Table Of Contents
Packet Infrastructure Messages
C12000_FWD_CLIENT_DLL Messages
PLATFORM_C12000_NETIO_LIB Messages
PLATFORM_HFR_NETIO_LIB Messages
PLATFORM_LPTS_COM_IFIB Messages
PLATFORM_LPTS_COM_NETIO Messages
Packet Infrastructure Messages
This section contains all Packet Infrastructure related System Error Messages, including ifmgr, tunnels, bundlemgr, pakman, and so forth. The following facility codes are represented in this module:
•
C12000_FWD_CLIENT_DLL Messages
•
•
•
•
AIB Messages
Error Message%PKT_INFRA-AIB-2-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 Be sure you have installed all of the proper software for your platform. If the problem persists, report it to your technical support representative.
Error Message%PKT_INFRA-AIB-2-INDEX_TIMEOUT AIB process timed out on platform adjacency index for for address=[hex], interface=[chars] flags=[hex] index=[hex]
Explanation The AIB process timed out on platform adjacency index indication.
Recommended Action If adjacencies are being updated properly then this is probably nothing to worry about. However, if adjacencies are not being updated then copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-AIB-2-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 Check that the platform DLLs and the base operation system versions are compatible. If not, install the correct software. If everything seems correct, contact your service representative.
Error Message%PKT_INFRA-AIB-2-PFI_IFH_ERROR A pfi_ifh failure. [chars]. (error=[chars].)
Explanation An important pfi_ifh api failed.
Recommended Action AIB automatically restarts and retries upon this failure. If it starts up automatically after a couple of retries, this error can be ignored. Otherwise, the card needs a reload.
Error Message%PKT_INFRA-AIB-2-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-2-SHM_FAILURE AIB Shared memory error: [chars] [chars]
Explanation The AIB process received an error while trying to initialize the shared 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-AIB-2-SYSTEM_FAIL [chars] [chars] (errno=[dec])
Explanation There was a critical system call failure resulting in a failure to provide some system service as indicated in the message text.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-AIB-4-LTRACE_ERROR Failed to open LTrace file: [chars]
Explanation The AIB process was unable to open the LTrace buffer for automatic tracing (show ltrace adjacency may not work).
Recommended Action Copy the error message exactly as it appears on the 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-NO_WAIT_INDEX AIB process received unexpected index for address=[hex], interface=[chars] flags=[hex] index=[hex]
Explanation The AIB process received an unexpected platform adjacency index.
Recommended Action If adjacencies are being updated properly then this is probably nothing to worry about. However, if adjacencies are not being updated then copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-AIB-4-PFI_IFH_SETRETRY_ERR Error setting the PFI IFH linear retry period: [hex] '[chars]'
Explanation AIB failed to set the linear retry period for connecting to the PFI IFH. This implies that PFI IFH lookups may fail.
Recommended Action Copy the error message exactly as it appears on the 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-UNEXP_RETURN AIB process received unexpected return value [chars] (errno=[dec])
Explanation The AIB process received an unexpected return value while waiting for service requests or replies.
Recommended Action If adjacencies are being updated properly then this is probably nothing to worry about. However, if adjacencies are not being updated then copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-AIB-6-LOCAL_ADDRESS AIB denied addition of adjacency to local address [chars] from client [chars]
Explanation The indicated AIB client has requested the addition of an adjacency associated with a local address. Such adjacencies are not allowed.
Recommended Action Copy the error message exactly as 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.
C12000_FWD_CLIENT_DLL Messages
Error Message%PKT_INFRA-C12000_FWD_CLIENT_DLL-3-ERR [chars][dec]
Explanation An error occured in the forwarder netio client dll (possible the plim driver)
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
C12000_PAK Messages
Error Message%PKT_INFRA-C12000_PAK-2-NETIO_CONN [chars]
Explanation Unexpected Error in netio 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-C12000_PAK-3-API_INVALID_INPUT Packet API call failed due to invalid input, API: [chars].
Explanation The packet supplied to the API is corrupted or has invalid fields.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-C12000_PAK-3-INSUF_SPACE_IN_HW_BUFF pak_netio_add_head_NEW: failed to add ([dec]) bytes in head due to hw limitations, use pak_netio_dup.
Explanation Unable to add nbytes to the head of 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.
DM Messages
Error Message%PKT_INFRA-DM-3-DUPLICATE_RULE DM Rules dll: duplicate promid: [chars] in file: [chars]
Explanation Duplicate promid found in one of the rules 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-DM-3-INVALID_FILENAME DM Rules dll: unable to open the rule file: [chars]
Explanation Unable to open 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-DM-3-PROC_AND_TUPLE DM Rules dll: found process and tuple rule in file
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-DM-3-RULES_PATH_NOTSET DM Rules dll: rules path env/sys variable not set
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-DM-4-ANOMALY [chars]
Explanation A SW exception occurred in DM Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DPM Messages
Error Message%PKT_INFRA-DPM-4-ANOMALY [chars]
Explanation A SW exception occurred in DPM Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ENCAP_RM Messages
Error Message%PKT_INFRA-ENCAP_RM-3-FATAL_ERR Fatal error: [chars]: Err=[dec]
Explanation A fatal error occurred in L2 Encap String RM which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-MSG_SEND_FAILED encap_rm: msg: [dec], retried: [dec] time(s), failed to send, errno: [chars]
Explanation Unable to send a message to the L2 Encap String RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-NONFATAL_ERR Nonfatal error: [chars]: Err=[dec]
Explanation This is a error message in the L2 Encap String RM to indicate anomalies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temporary situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-6-INFO_MSG Info: [chars]
Explanation This is an informational message in the L2 Encap String RM.
Recommended Action No action is required.
ENCAP Messages
Error Message%PKT_INFRA-ENCAP-3-DEBUG_INIT_EVENT_FAILED [chars]: debug_init_event([chars]) failed error [chars]
Explanation Failed to switch ON debug event for encapsulation package.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-DEBUG_REGISTER_FAILED [chars]: debug_register() failed error [chars]
Explanation Failed to register debug events for encapsulation package.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-DROP_PKT [chars]: [chars]
Explanation Dropping packets. Bad.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-FAILURE [chars]
Explanation Failure in c12000/aib component.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-INVALID_CHAIN_BUILD Erroneous call to build chain type [dec]
Explanation Tried to build invalid chain type
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-SYSDB_BIND_FAILED sysdb_bind failed [hex], [chars]
Explanation Failed to bind to sysdb.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-SYSDB_REGISTER_FAILED Failed to register for notification ,[[hex]] [chars]
Explanation Failed to register with Sydb for item change notification
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-TX_PKT [chars]: [chars] (size=[dec])
Explanation sending packets
Recommended Action none
Error Message%PKT_INFRA-ENCAP-3-UNEXPECTED_NODE_CALL [chars] Node erroneously called
Explanation Capsulation Node function is erroneously called
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-ENCAP-3-UNRECOGNIZED_CONTROL_CMD Unrecognized command [dec] received by Fabric dll
Explanation Fabric Control function received unrecognized control command
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
ETHER_SHIM_PARTNER Messages
Error Message%PKT_INFRA-ETHER_SHIM_PARTNER-3-FATAL_ERR Fatal error: [chars]: Err=[dec]
Explanation A fatal error occurred in ether_shim_partner which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FEA_DLL Messages
Error Message%PKT_INFRA-FEA_DLL-3-MSTATS_ALLOC_ERR MSTATS [chars] region: [chars]
Explanation Feature EA DLL encountered error in completing MSTATS operation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-MSTATS_ERR MSTATS [chars] error: [chars]: Err=[dec]
Explanation Feature EA DLL encountered error in completing MSTATS operation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-REPRGM_ERROR Errored during scrub reprogramming [chars] region: [chars]
Explanation Errors occured during reprogramming
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-TCAM_ERR TCAM [chars] error: [chars]: Err=[dec]
Explanation Feature EA DLL encountered error in completing TCAM operation. This can lead to inconsistency between HW view of configuration and SW view of configuration.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-TCAM_LIMIT TCAM [chars] limit exceeded
Explanation This message will typically occur when permissible single region size is exceeded or total number of entries allowed in tcam for a given application is exceeded.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FEA_DLL-3-UIDB_ERR UIDB [chars] error: [chars]: Err=[dec]
Explanation Feature EA DLL encountered error in completing UIDB operation. This can lead to inconsistency between HW view of configuration and SW view of configuration.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-FATAL fm: fatal error - [chars] (errno = [dec])
Explanation A fatal error occured for the Feature 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-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-SW_ERROR fm: bad state ([chars]) - [chars] ([dec])
Explanation A S/W error occurred which results in a condition/state that should not be achieved
Recommended Action Copy the error message exactly as it appears on the 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 fm: info - [chars]
Explanation This is an informational message in the Feature Manager
Recommended Action No action is required.
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.
Error Message%PKT_INFRA-FM-6-MALLOC_FAILED fm: memory allocation error for bytes
Explanation Unable to allocate memory for Feature 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-6-RES_ALLOC_FAILED fm: resource allocation failed - [chars] ([dec])
Explanation Unable to allocate the specified resource
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FMGR Messages
Error Message%PKT_INFRA-FMGR-3-ACL_WITH_SRC_PORT_NOT_SUPPORTED ACL's with source port are not supported in a policy-map
WARNING: Partial match criteria (without source port) is programmed into hardware.
ACL Name: [chars], ACE ID: [dec]
Explanation Feature Manager, This feature is not supported due to h/w limitations.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FMGR-3-error [chars]. Error = [chars].
Explanation This error is in Feature Manager component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FMGR-4-warning [chars]
Explanation This error is from Feature Manager component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD_HA Messages
Error Message%PKT_INFRA-FWD_HA-2-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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FWD_HA-2-PROCESS_STOP [chars] restart_count = [dec] stop_threshold = [dec]
Explanation The number of restart for this process within a short period of time exceeded the stop threshold, stopping the process from running.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FWD_HA-7-PROCESS_GRACEFUL_RESTART [chars]
Explanation The process is being restarting gracefully.
Recommended Action If this message is seen following a process restart or a pkg upgrade/downgrade, then it can be ignored. If not please copy the error message exactly as it appears, and report it to your technical support representative.
FWD_NETIO_DLL Messages
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-ATTACH_FAILED fwd: netio idb attach failed for plim interface: [hex].
Explanation FWD was not able to attach to plim interface .
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-ATTACH_FAILED fwd: netio idb attach failed for plim interface: [hex].
Explanation FWD was not able to attach to plim interface .
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BAD_COMMAND_RESULT fwd: received bad command result for buffer request: [hex]
Explanation FWD received a bad command result for BMA free buffer request
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BMA_OUT_OF_SEQUENCE fwd: BMA buffer request/response sequence number mismatch - received [dec], expected [dec]
Explanation FWD received an out of sequence BMA buffer request response
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-EGRESSQ_CREATE_FAILED fwd: egressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the egressq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FABRICQ_CREATE_FAILED fwd: fabricq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the fabricq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL fwd: fatal error encountered, reason=[chars]
Explanation Null Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL fwd: fatal error encountered, reason=[chars]
Explanation Null Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason=[chars], errno=[dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason=[chars], errno=[dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-GET_CTX_ERR Failed to get idb ctx for port [dec], error - ([dec])
Explanation FWD driver got a packet but couldn't map a port to an idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-HSRMODE [[chars]]: error getting hsrmode , reason=[chars], errno=[dec]
Explanation Error determining if mode is HSR. Caller will error string and errno. Caller can also supply an additional description (like function name) to identify where this error occurred in the code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-IDB_CTX_NULL FWD idb context for port [hex] is NULL!
Explanation While processing an ingress packet, the fwd driver failed to find idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INFO fwd: service degrading error, reason = [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INGRESSQ_CREATE_FAILED fwd: ingressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the ingressq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PLIM_PORT fwd: invalid plim port for plim interface: [hex]
Explanation FWD was supplied with a plim port that exceeds the limit of num ports.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PORT fwd: invalid plim port for plim interface: [hex]
Explanation FWD was supplied with a plim port or uidb index that exceeds the limit of num ports.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MALLOC_FAILED fwd: fatal memory allocation error for bytes
Explanation FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MALLOC_FAILED fwd: fatal memory allocation error for bytes
Explanation FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MUTEXOPFAIL [chars]: Mutex [chars] operation failed on [chars]; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NETIO_IDB_UNAVAILABLE netio idb for interface [hex] not found, dropping packet 0x[pointer]
Explanation While processing an ingress packet, the fwd driver failed to find netio idb
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NO_OUTSTANDING_BMA_REQ fwd: received BMA buffer request response with no outstanding request
Explanation FWD received a BMA interrupt indicating a response to a BMA buffer request but there was no request made
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NOT_YET_IMPLEMENTED fwd: this function is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NOT_YET_IMPLEMENTED fwd: this function is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-PAK_PROC_ERR [chars] : [chars], pak = [hex], rc = [hex]
Explanation There was an packet processing error. Possible causes 1) Unable to retrieve fabric dest addr from inside the pkt 2) Error setting/getting input ifh from pkt
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_EGRESS_Q_LOOKUP_ERR Failed to find netio egress qad queue. dropping packet 0x[pointer]
Explanation While transmitting a packet down to the fabric, couldn't find the egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_Q_PRODUCE_FAILED Failed to populate netio egress queue, error - [chars]
Explanation FWD driver failed to populate qad netio egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_RX_THREAD_ERR Failed to create forwarder qad rx thread, error - [chars]
Explanation FWD driver failed to create qad rx thread
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-SET_INPUT_IF_ERR Failed to set input interface handle [hex] on packet
Explanation While processing an ingress packet, the fwd driver failed to set input interface
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-4-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb. Could be transient.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-6-INFO fwd: [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD Messages
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 Copy the error message exactly as it appears on the 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]
Explanation FWD Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-FATAL_2 fwd: fatal error encountered, reason=[chars], errno=[dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-FATAL_3 fwd: fatal error encountered, reason=[chars], error=[chars]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An error string corresponging to the failing API will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-GEN_INFO fwd: general information,
Explanation The FWD's informational message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-INFO fwd: service degrading error, reason = [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-MALLOC_FAILED FWD: fatal memory allocation error for bytes
Explanation FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD-3-NOT_YET_IMPLEMENTED fwd: this function is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-NULL_PP_CTX FWD: partner part is NULL in func: [chars].
Explanation FWD encountered a fatal error condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
GSR_aib_hwdrv Messages
Error Message%PKT_INFRA-GSR_aib_hwdrv-3-RES_ERROR Error: [chars]: Err=[chars]
Explanation A error occurred in GSR aib Edge h/w Driver resulting in a failure to provide some system service as indicated in the message text.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-GSR_aib_hwdrv-6-INFO_MSG Info: [chars]
Explanation This is a Informational message in the GSR aib Driver to indicate an operation.
Recommended Action No action is required.
HFR_FWD Messages
Error Message%PKT_INFRA-HFR_FWD-3-FATAL hfr_fwd: fatal error encountered, reason=[chars]
Explanation HFR FWD Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-FATAL_2 hfr_fwd: fatal error encountered, reason=[chars], errno=[dec]
Explanation hfr_fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-GEN_INFO hfr_fwd: general information,
Explanation The HFR FWD's informational message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-INFO hfr_fwd: service degrading error, reason = [chars]
Explanation The hfr_fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-MALLOC_FAILED hfr_fwd: fatal memory allocation error for bytes
Explanation HFR FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-HFR_FWD-3-NOT_YET_IMPLEMENTED hfr_fwd: this function is not yet implemented
Explanation HFR FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-HFR_FWD-3-USAGE hfr_fwd: invalid option passed to fwd server
Explanation Startup option supplied to HFR FWD is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
HFR_PFI Messages
Error Message%PKT_INFRA-HFR_PFI-3-SET_GLOBALS_FAILED [chars] ([chars])
Explanation Platform PFI was unable to set globals
Recommended Action No action is required.
IFMGR_ENCAP Messages
Error Message%PKT_INFRA-IFMGR_ENCAP-3-BC_ERR Encap change for [chars] [chars] [chars] failed(error [chars])
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync
Recommended Action Repeat failed configuration command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR_ENCAP-3-INIT_ERR [chars] initialization 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-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-COMM Communication error [chars] errno [[chars]], msg size [dec]
Explanation The ifmgr 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-IFMGR-3-DEBUG_INIT_EVENT_FAILED Failed to initialise [chars] debugging: [chars]
Explanation Failed to switch ON debug event on IM server side.
Recommended Action The process will restart 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-3-DEFERRED_DOWNLOAD_FAILED Subinterfaces on interface [chars] could not be created: [chars] ([dec])
Explanation Interface Manager is unable to create sub-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-IFMGR-3-ERR_FEATURE_TIMEOUT Feature [chars] timeout for context [chars]
Explanation A feature 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-ERR_FSM FSM error in function [chars]()
Explanation An error was returned from the FSM library.
Recommended Action Copy the error message exactly as it appears on the 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_GET_TREE_NODE Cannot find tree node [hex]
Explanation Interface Manager failed to find a node which should exist in its tree.
Recommended Action This error indicates that the Interface Manager database is not correct. If this message is seen repeatedly then try restarting the ifmgr process, causing it to resync.
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: [hex]. 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 A fatal 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. 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 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 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-INT_ERR Fatal error in [chars] error:[[hex]] [chars]
Explanation The ifmgr process has experienced an error which it cannot 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-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-MALLOC Cannot allocate [unsigned int] bytes in function [chars]
Explanation This process has tried and failed to allocate memory. This probably means that the system as a whole is running low on memory.
Recommended Action Reduce other system activity (e.g. by killing non-essential processes) to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-IFMGR-3-RULE_NAME_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-RULE_NOT_FOUND [chars] rule for type [dec] 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 (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-BAD_COMMAND_LINE Unrecognized command line arg [chars]
Explanation Some arguments on the ifmgr command line are not recognized by the ifmgr program.
Recommended Action 'Copy the error message exactly as it appears on the 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-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 Failed to download rules on the specified node.
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-INIT_RETRY Init error: [chars]: [chars] ([dec]).
Explanation An error occurred while the process was starting up.
Recommended Action The process will retry the operation and try to recover. However until this operation succeeds the process will not function normally. Restarting the ifmgr process may help to solve 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-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 Unexpected problem accessing SysDB.
Recommended Action 'A failure to start a bulk request doesn't matter since the operations will just take place one at a time. A failure to abort a bulk request will not commit the request. A failure to commit the request implies that some or all of the operations within the request failed to take effect, potentially leaving the system in an inconstent state.'
Error Message%PKT_INFRA-IFMGR-4-UNKNOWN_CASE_REACHED Unknown case [unsigned int] hit in function [chars]
Explanation Interface Manager reached a case that was not expected.
Recommended Action This message is for information only and Interface Manager will handle the unknown case by taking no action. However this may indicate that there is a more serious issue so if any other problems are seen then include this message in the report.
Error Message%PKT_INFRA-IFMGR-6-BULK_DOWNLOAD_FAILED Bulk [chars] id:[unsigned int], count:[unsigned int], ifh[0]=[hex], caps:[unsigned int], proto:[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-EXITING ifmgr exiting. This should never happen
Explanation Informational message that ifmgr process is exiting.
Recommended Action 'No action is required.'
Error Message%PKT_INFRA-IFMGR-6-GSP_SEND_RETRY group_send 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.
Error Message%PKT_INFRA-IFMGR-6-IMDC_OVERFLOW Unable to queue messages to IMD due to queue overflow, msg count [dec]
Explanation ifmgr failed to queue messges destined to IMD over GSP, most probably because the transmit queue is full and messages cannot be sent for 30 seconds because GSP is not up yet.
Recommended Action check status of GSP and restart ifmgr.
Error Message%PKT_INFRA-IFMGR-6-STARTING ifmgr starting...
Explanation Informational message that ifmgr process is starting up.
Recommended Action 'No action is required.'
IMAEDM Messages
Error Message%PKT_INFRA-IMAEDM-3-EVENT_ASYNC_ATTACH_FAILED [chars]: could not attach asynchronous event to Event Manager for [chars]: [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-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-MEMORY_ERR [chars]: Could not allocate memory for [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_BIND_FAILED [chars]: Can't bind to SysDB at [chars]: [chars]
Explanation The sysdb_bind 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.
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.
Error Message%PKT_INFRA-IMAEDM-7-SYSDB_UNBIND_FAILED [chars]: Can't unbind from SysDB at [chars]: [chars]
Explanation The sysdb_unbind 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.
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-INIT_SYSMGR Init error: [chars]: [chars] ([dec]).
Explanation An error occurred while the IMD process was starting up.
Recommended Action This message indicates that sysmgr failed to serve the request from imd server as specified in error message. If IMD process is restarting please restart ifmgr process also. If IMD process is starting for first time, ifmgr process need not be restarted. 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-3-NOMEM Failed to allocate [unsigned int] bytes for [chars]
Explanation The IMD process failed to allocate memory.
Recommended Action This problem probably indicates a system-wide issue. Free up resources by removing unnecessary configuration or killing non-essential processes.
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-1-INITIAL_DOWNLOAD_TIMER_EXPIRED Initial Download Timer Expired count=[dec] members=[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.'
Error Message%PKT_INFRA-IMPROXY-3-DOWNLOAD_FAILED download [dec] failed ([dec]:[chars]) pending EA:[chars], prio=[dec] state=[dec] flags=[hex] refcount=[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.'
Error Message%PKT_INFRA-IMPROXY-3-DOWNLOAD_NETIO_RESTART_FAILED Fatal error ([dec]:[chars]) downloading to netio after restart
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-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 be broken as a result of this.
Recommended Action Copy the error message exactly as it appears on the 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 (group_send error [hex]) [chars]
Explanation GSP has difficulty in delivering the mesage to some nodes. There could be a communication problem.
Recommended Action If there is a problem, it might be cleared by restarting improxy.
Error Message%PKT_INFRA-IMPROXY-3-IIR_CONNECT_FAILED (conn_open error [hex]) [chars]
Explanation Improxy failed to open it connection to the IIR service.
Recommended Action If there is a problem, it might be cleared by restarting improxy.
Error Message%PKT_INFRA-IMPROXY-3-INIT Init error: [chars]: [chars] ([hex])
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 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-MALLOC_FAILED Message buffer allocation failed [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.'
Error Message%PKT_INFRA-IMPROXY-3-MSG_GET_CONNID_FAILED netio msg_get_conn_connid 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-IMPROXY-6-EXITING improxy exiting. This should never happen
Explanation Informational message that ifmgr process is exiting.
Recommended Action 'No action is required.'
Error Message%PKT_INFRA-IMPROXY-6-STARTING improxy starting on slot [dec]...
Explanation Informational message that improxy process is starting up.
Recommended Action 'No action is required.'
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 No action is required.
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 No action is required.
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-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.
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_PA_FGID_DB Messages
Error Message%PKT_INFRA-LPTS_PA_FGID_DB-3-INFRA_ERR Unrecoverable error in FGID resource managing infrastructure : [chars]
Explanation A severe internal error was detected while using Fabric Multicast Group Indentifier(FGID) resource managing infrastructure APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PIFIB Messages
Error Message%PKT_INFRA-LPTS_PIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PREIFIB Messages
Error Message%PKT_INFRA-LPTS_PREIFIB-3-BACKEND_EDM [chars]: EDM backend function [chars] failed: [chars]
Explanation An internal EDM backend function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-BAG [chars]: Bag function [chars] failed: [chars]
Explanation An internal bag function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-LPTS_PREIFIB-3-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-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-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-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-PFI_IFH_GET_IF_CHAR [chars]: Failed to get interface characteristic for interface handle [hex]: [chars]
Explanation Failed to get interface characteristic for the given 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-PFI_IFH_GET_IF_INFO [chars]: Failed to get interface information for interface handle [hex]: [chars]
Explanation Failed to get interface information for the given 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-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-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_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-ATTR_INIT_FAILED NetIO debugging partner failed to initialize attribute support for [chars] on [chars], err: [chars]
Explanation The NetIO debugging partner process could not initialize IM attribute support for an attribute on the specified 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-netio_debug-3-DEBUG_REG_FAILED Failed to register for debugging services, (err: [chars]).
Explanation It was not possible for the NetIO debugging partner process to register for debugging.
Recommended Action Restart the NetIO debugging partner process if debug support is required.
Error Message%PKT_INFRA-netio_debug-3-IM_CONNECT_FAILED Failed to connect to IM, err: [chars]
Explanation The NetIO debugging partner process failed to connect to the IM 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-netio_debug-3-IM_INIT_FAILED Failed during IM initialization, err: [chars]
Explanation The NetIO debugging partner process initialization failed whilst trying to connect to IM.
Recommended Action Copy the error message exactly as it appears on the 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-3-INIT_FAILED NetIO debugging partner initialization failed, err: [chars]
Explanation The NetIO debugging partner process 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-netio_debug-3-NETIO_CONNECT_FAILED Failed to connect to NetIO, err: [chars]
Explanation The NetIO debugging partner process failed to connect 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-netio_debug-3-NETIO_INIT_FAILED Failed during NetIO initialization, err: [chars]
Explanation The NetIO debugging partner process initialization failed whilst trying to connect 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-netio_debug-3-NO_MEM Out of memory, at [chars], mallocing [unsigned int] bytes
Explanation The NetIO debuggging partner process has run out of memory.
Recommended Action Install more memory
Error Message%PKT_INFRA-netio_debug-4-ASYNC_HANDLER Couldn't install the default handler for async msgs, err: [chars]
Explanation The NetIO debugging partner process couldn't install the default event handler for async msgs.
Recommended Action No action is required.
Error Message%PKT_INFRA-netio_debug-4-ERROR_DLL_REG_FAILED Failed to register the NetIO debugging partner process error DLL, err: [chars]
Explanation The NetIO debugging partner process failed to register its cerrno error DLL.
Recommended Action No action is required.
Error Message%PKT_INFRA-netio_debug-4-UNEXPECTED_IM_MSG Received an unexpected IM message ([chars]) on [chars].
Explanation The NetIO debugging partner process received an expected IM message that it doesn't have a handler for.
Recommended Action No action is required.
NETIO Messages
Error Message%PKT_INFRA-NETIO-1-CHANNELCREATE_FAILURE channel create failed, errno = [dec], reason: [chars]
Explanation NetIO failed to create the resource manager 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-NETIO-1-INITIAL_DOWNLOAD_FAILED IMP indicated an initial download failure
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-NETIO-1-RESMGR_PATHNAME_ATTACH_FAILURE failed to attach to path [chars], errno = [dec], reason: [chars]
Explanation NetIO failed to attach to the resource manager pathname.
Recommended Action 'Copy the error message exactly as it appears on the 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-1-RESMGR_THREAD_CREATE_FAILURE Fail to create netio resmgr thread: [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-NETIO-1-SELFMANAGE_FAILURE NETIO self-manage upgrade [chars] error: [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-NETIO-1-SELFMANAGE_UPGRADE_FAILURE NetIO: is being upgraded. NetIO will be restarted
Explanation NetIO gets restarted whenever a DLL is being upgraded and the DLL does not support the NetIO upgradability. This should not cause any problems in the router.
Recommended Action This should not cause any problems in the router. If it causes any routing issues such as adjacency going down or some other problem, - 'Copy the error message exactly as it appears on the 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-1-SET_MAX_PROTO_FAILURE set max protocol failed, errno = [dec], reason: [chars]
Explanation NetIO failed to set the maximum protocol 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-NETIO-2-LWM_RECEIVE_RETURNED Unexpected return from netio_lwm_receive(). errno = [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.'
Error Message%PKT_INFRA-NETIO-3-BAD_CHAIN_TYPE Function [chars]() detected bad chain type [hex]
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-NETIO-3-BAD_DEBUG_EVM exit debug_api event-main loop with errno=[dec]
Explanation EVM used by debugging API encountered error.
Recommended Action 'No action is required.'
Error Message%PKT_INFRA-NETIO-3-BADPROTOBLOCK Not transmittable on pdb [dec]; packet dropped
Explanation Selected protocol is null or else has no output 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-NETIO-3-BADPROTOID Bad protocol id [dec]; packet dropped
Explanation Protocol ID was not properly set before sending 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-CTRL_THREAD_CREATE_FAIL Fail to create netio control thread: [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-NETIO-3-DEBUG_INIT_EVENT_FAILED [chars]: debug_init_event([chars]) failed error [chars]
Explanation Failed to switch ON debug event on netio server side.
Recommended Action 'Copy the error message exactly as it appears on the 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-DEBUG_REGISTER_FAILED [chars]: debug_register() failed error [chars]
Explanation Failed to register debug events on netio server side.
Recommended Action 'Copy the error message exactly as it appears on the 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-DI_INIT_FAILURE Driver Infrastructure initialization failed
Explanation As part of netio initialization, driver infrastructure is loaded and initialized. An error was reported from driver infrastructure during this 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.'
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_DLL Unable to load DLL, reason is [chars]
Explanation The system was unable to load a DLL.
Recommended Action 'Copy the error message exactly as it appears on the 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_ROUTINE Couldn't find [chars] init routine
Explanation The system was unable to find an initialization routine
Recommended Action 'Copy the error message exactly as it appears on the 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_MUTEX Couldn't get mutex in funtion [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-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-ERR_SYSDB_CONN Couldn't connect to sysdb
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-NETIO-3-INTERNAL_FAILURE_ERRNO [chars]:[dec] in [chars](): [chars] failed ([dec])[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-NETIO-3-INTERNAL_FAILURE_OTHER [chars]:[dec] in [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-NETIO-3-INTERNAL_FAILURE_RC [chars]:[dec] in [chars](): [chars] failed rc ([dec])[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-NETIO-3-LOADPATH_FAILURE loadpath registration failed
Explanation Failed to do ovl registry for LOADPATH
Recommended Action 'Copy the error message exactly as it appears on the 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 ltrace_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-NETIO-3-MUTEXOPFAIL [chars]: Mutex [chars] operation failed on [chars]; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-NO_DEBUG_EVM netio exiting. event_manager_create() for debug failed ([dec])[chars]
Explanation Problem creating EVM required for debugging 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-NETIO-3-NO_DEBUG_THREAD netio exiting. pthread_create() failed for debug_api_thread ([dec])[chars]
Explanation Second thread in netio is for debugging API. Problem creating this 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-NETIO-3-NO_OVL_INIT_THREAD netio exiting. pthread_create() failed for netio_ovl_init_thread ([dec])[chars]
Explanation This thread in netio is for initializing ovl notifications. Problem creating this 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-NETIO-3-NODE_ROLE_REGISTER_FAILURE node role change registration failed [dec]
Explanation Failed to do node role registry with sysmgr
Recommended Action 'Copy the error message exactly as it appears on the 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-NODE_STATE_FAILURE sysmgr get node state failed [dec]
Explanation Failed to get the node state from sysmgr
Recommended Action 'Copy the error message exactly as it appears on the 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-NULLCHAIN Null chain on puntback; packet dropped
Explanation Packet punted back to NetIO has a NULL chain reference.
Recommended Action 'Copy the error message exactly as it appears on the 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-NULLCHAINELEMENT Null chain element after puntback; In Interface: [chars], Out Interface: [chars], Caps: [chars], Proto: [chars]; Packet dropped
Explanation Puntback chain has no next element.
Recommended Action 'Copy the error message exactly as it appears on the 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-NULLENCAPS Null encapsulation, no chain built, function [chars], line [dec], protocol [dec]
Explanation No encapsulation was defined for this protocol.
Recommended Action 'Copy the error message exactly as it appears on the 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-OVL_THREAD_DETACH_FAILURE netio exiting. pthread_detach() failed for netio_ovl_init_thread ([dec])[chars]
Explanation This thread in netio is for initializing ovl notifications. Problem detaching this thread from the main thread. Without this operation, resources will not be re-claimed from this thread when this thread exits.
Recommended Action 'Copy the error message exactly as it appears on the 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-PAKMAN_CONNECT_FAILED Failed to connect to packet manager ([dec])[chars]
Explanation Fatal failure to connect 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.'
Error Message%PKT_INFRA-NETIO-3-QSM_ADD_FAILURE qsm_add_service_directory() failed [chars] ([dec])
Explanation Initialization of the netio QSM entries 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_BADNUMERIC script [chars]([dec]): error parsing '[chars]' as numeric (zero used)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_BUILDCHAIN Build chain failed for the script: [chars]
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_DUPLICATE script [chars]([dec]): duplicate [chars] (ignored)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_ENV_VAR_NULL Netio script search environment variables are NULL
Explanation An error was detected in locating path of netio script files.
Recommended Action 'Copy the error message exactly as it appears on the 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_EXCEEDSLIMIT script [chars]([dec]): value of [chars] ([dec]) exceeds limit ([dec])
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_EXCESS script [chars]([dec]): excess text on line (discarding past '[chars]')
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_EXEC script [chars]([dec]): command ([chars]) execution error: [chars]
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_EXISTS script [chars]([dec]): [chars] '[chars]' already exists (ignored)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_FILENOTFOUND cannot find/read script file: [chars]
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_MALLOC_FAIL script [chars]([dec]): fail to alloc memory for chain node
Explanation An internal error error was detected in the script 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-NETIO-3-SCRIPT_MISSINGARG script [chars]([dec]): missing argument(s) to '[chars]' (ignored)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_MISSINGTAG script [chars]([dec]): tag missing (record discarded)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_MULTIPLEDEFINITION script [chars]([dec]): multiple definition of [chars]/[dec], last definition is: [chars]/[dec]
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_NOTDEFINED script [chars]([dec]): [chars] is not defined
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_PATH_MALLOC_FAIL 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 on the 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_TOOLONG script [chars]([dec]): '[chars]' exceeds max of [dec] chars (truncated)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_UNKNOWNFLAG script [chars]([dec]): unknown flag '[chars]' (ignored)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_UNKNOWNKEYWORD script [chars]([dec]): unknown keyword '[chars]' (ignored)
Explanation An internal syntax error was detected in the script 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-NETIO-3-SCRIPT_ZERO script [chars]([dec]): a non-zero value is expected for [chars]
Explanation An internal syntax error was detected in the script 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-NETIO-3-SVC_REGISTER_FAILURE svcrm_register failed, errno = [dec], reason: [chars]
Explanation NetIO failed to add service handler for RPC 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-NETIO-3-SVCRM_CREATE_FAILURE svcrm_create failed, errno = [dec], reason: [chars]
Explanation NetIO failed to create the transport for RPC 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-NETIO-3-SYSMGR_PROC_READY_FAILURE sysmgr_proc_ready failed [chars] ([dec])
Explanation Initialization of the netio QSM entries 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-4-BAD_COMMAND_LINE Unrecognized command line arg [chars]
Explanation Some arguments on the netio command line are not recognized by the netio program.
Recommended Action 'Copy the error message exactly as it appears on the 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-REQ_MALLOC_FAIL Fail to alloc memory for input. Failing message.
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-NETIO-6-DEBUG_INIT_FAILURE netio debug initialization failed error [dec]
Explanation Initialization of the netio debug facility failed. This will have no affect on normal operation, but netio debug commands will not enable debug output from the netio process.
Recommended Action 'Copy the error message exactly as it appears on the 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-PAK_EVENT netio_pak_event_function: msgcode is: [unsigned long int]
Explanation Netio has received a notification from the packet manager. This is really here for debugging. Probably turn it into a buginf later. FIXME
Recommended Action 'No action is required.'
Error Message%PKT_INFRA-NETIO-6-STARTING Netio starting...
Explanation Informational message that netio daemon process is starting up.
Recommended Action 'No action is required.'
Error Message%PKT_INFRA-NETIO-7-SELFMANAGE_INFO Upgrade - [chars] dll [chars]
Explanation Netio is upgrading dll. This is really here for information.
Recommended Action 'No action is required.'
PA Messages
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-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_CAPTURE Messages
Error Message%PKT_INFRA-PAK_CAPTURE-4-ECC_ERROR packet dropped in hw due to programming error: pkt type [hex] pkt: [chars]
Explanation A packet was dropped in hardware due to bad programming or a hardware error. This is a raw dump of the packet to aid in debugging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PAK Messages
Error Message%PKT_INFRA-PAK-2-BADSHARE Bad refcount in [chars], ptr=[hex], count=[hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-DEBUGINITFAIL [chars]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-DEBUGREGISTERFAIL [chars]:debug_register failed for packet client :[dec]:[chars]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-EXCEPTION packet exception, file: [chars], line: [dec], reason: [chars]
Explanation An exception had occurred in the software.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-EXCEPTION_LITE packet exception, reason: [chars]
Explanation An exception had occurred in the software.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-GETBUF Bad pak_get_buffer argument, pid=[dec], bytes=[dec]
Explanation The client asked for a buffer larger than the maximum allowed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-GETPTCLFAIL Particle [chars] allocation failed in process [dec] from [hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-GETPTCLHDR Unable to allocate a particle header
Explanation The client asked for a buffer larger than the maximum allowed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-HDRINLIST Packet header already in list, ptr= [hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-HDRSHARED Attempt to return packet header with sharecount [dec], ptr= [hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-LOWMEM Low memory debug exception (limit=[unsigned int] free=[unsigned int])
Explanation The router is running short of packet 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-PAK-2-PTCLINLIST Packet header already in list, ptr= [hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-2-PTCLSHARED Attempt to return particle header with sharecount [dec], ptr= [hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-3-FSVOVRFLOW This request would overflow the packet FSV area
Explanation A call to pak_set_fsv_size() has 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-PAK-3-MUTEXOPFAIL mutex [chars] operation on [chars] in [chars] failed; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAK-3-SIGOPFAIL signal [chars] operation on [dec] in [chars] failed; reason [chars]
Explanation A packet client's attempt to initialize communications with the packet manager 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-PAK-3-TRCINITFAIL Packet event tracing initialization failed.
Explanation The packet subsystem was not able to initialize tracing properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAK-5-RESTART Packet server restarted --
[chars]Explanation A restart of the packet process was requested.
Recommended Action Notification messages only. No action required.
PAKPLATFORM Messages
Error Message%PKT_INFRA-PAKPLATFORM-3-CONNECTFAIL Connect to the packet server failed in [chars]. 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-3-SENDFAIL Send to the packet server failed in [chars]. Reason : [chars]
Explanation The platform driver was not able to send data 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.
PAKSRV Messages
Error Message%PKT_INFRA-PAKSRV-1-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.
Error Message%PKT_INFRA-PAKSRV-2-BADPAKFSV Corruption detects at the FSV area [pointer] of the packet header [pointer] belongs to process [dec]
Explanation Consistency check detects corruption at internal structure of the packet memory. 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-2-BADPAKHDR Corruption detects at the packet header [pointer] belongs to process [dec]
Explanation Consistency check detects corruption at internal structure of the packet memory. 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-2-BADPAKTRC Corruption detects at the Trace area [pointer] of the packet header [pointer] belongs to process [dec]
Explanation Consistency check detects corruption at internal structure of the packet memory. 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-2-BADPTCLBDY Corruption detects at particle body [pointer] owned by pak [pointer] belongs to process [dec]
Explanation Consistency check detects corruption at internal structure of the packet memory. 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-2-BADPTCLHDR Corruption detects at the [chars] particle header [pointer] owned by pak [pointer] belongs to process [dec]
Explanation Consistency check detects corruption at internal structure of the packet memory. 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-2-BCASTFAIL Packet server fails to send broadcast msg [dec] to client [dec] with error: [chars]
Explanation Packet server can not send broadcast message to the client. This will result the client unaware of an event occurs in packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-CHANCREATEFAIL Packet server fails to create a channel and event manager error: [chars]
Explanation Packet server fails 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-2-CHKPTOPFAIL [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-2-CHUNKCREATEFAIL pak_init: chunk_create for packet hdrs failed
Explanation Could not allocate a chunk of memory for the packet trace buffers
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-DEQUEUEFAIL Fail to remove client [dec] from pak_client_list at [chars]
Explanation Can not remove the client from 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-2-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. If available, restore the previous version of the packet manager
Error Message%PKT_INFRA-PAKSRV-2-ENQUEUEFAIL Fail to insert client [dec] into pak_client_list at [chars]
Explanation Can not insert the client into client list queue. This causes the client unable to connect to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-EVENTATTACHFAIL event attach failure.
Explanation The packet subsystem encountered an error when registering 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-2-EVENTBLOCKFAIL event block failure.
Explanation event block error was encountered when blocking for external events.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-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-2-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-2-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-2-GETPIDFAIL Fail to get client's pid at [chars]
Explanation Can not get the client's pid. This will cause the client unable to connect to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-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-2-MALLOCFAIL Malloc fails in process [dec] at [chars]
Explanation The router can not 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-2-MEMUTILMAPFAIL pak_init: mapping for [chars] failed because [chars]
Explanation No large pages are allowed. Need to set up mappings between trace buffers and particle headers.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-MSGREPLYFAIL Fail to reply to client's [dec] requested message [dec] at [chars]
Explanation Can not reply to client's request using light weight messaging. This will result the client to be blocked.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-MUTREVIVEFAIL SyncMutexRevive failed on pak mutex because [chars]
Explanation The packet subsystem failed to revive mutex.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-PAKBCASTFAIL broadcast to clients from pak_manager failed.
Explanation receive the request from pkt_manager to simulate packet server is about to abort.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-PTHREADATTRFAIL pthread attribute error in pakman while creating the [chars] thread
Explanation packet manager server unable to create a new thread
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-PTHREADCREATEFAIL pthread create fail in pakman while creating the [chars] thread
Explanation packet manager server unable to create a new thread
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-PTHREADDETACHFAIL pthread detach error in pakman for the [chars] thread
Explanation packet manager server unable to detach new thread
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-PTHREADMUTEXFAIL pak_init: pthread_mutex_init failed on pak mutex because [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-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-2-SIGNAL signal: [chars].
Explanation The packet subsystem encountered an error while registering/handling a signal.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-SYSDBBINDFAIL sysdb bind fail in pakman
Explanation packet manager server unable to bind to sysdb
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-SYSDBITEMSETFAIL sysdb set item fail in pakman
Explanation packet manager server unable to set item in sysdb
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-SYSMGR_GET_NODE_STATE sysmgr get node state failure: [chars].
Explanation sysmgr_get_node_state failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-SYSMGR_REGISTER node role change registration with sysmgr failed: [chars].
Explanation sysmgr_register_node_state_change failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-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-PAKSRV-2-UNONCRPT Corruption detects at the unknown area [pointer] of the packet header [pointer] belongs to process [dec]
Explanation Consistency check detects corruption at internal structure of the packet memory. This may 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-BADMSGCODE bad msg code [dec] in [chars]
Explanation The packet subsystem detected a message code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKSRV-3-CONDWAITFAIL condition wait operation on [chars] in [chars] failed; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKSRV-3-DEBUGINITFAIL Packet server debug initialization: [chars] failed, error [chars]
Explanation The debug support initalization failed in 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-PAKSRV-3-INITFAIL Packet server initialization failed. Reason : [chars]
Explanation The packet subsystem was not able to initialize properly.
Recommended Action Copy the error message exactly as it appears on the 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-3-INITWARNING Warning([chars]) while initializing the packet process
Explanation The packet subsystem detected some errors while initializing.
Recommended Action Copy the error message exactly as it appears on the 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-3-MUTEXFAIL mutex [chars] operation on [chars] in [chars] failed; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKSRV-3-MUTMONREG_FAIL Packet server registration for mutex monitoring (revival) failed, error [chars]
Explanation The mutex revival monitor routine failed in 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-PAKSRV-3-PARTICLEINITFAIL pak_init: particle_init call failed.
Explanation The particles were not able to initialize properly.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-6-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.
PAKWATCH Messages
Error Message%PKT_INFRA-PAKWATCH-6-INFO Depletion level [dec] percent
for resource [chars]:Explanation The info about number of user and the resource type to be displayed.
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-INFO_BODY [chars] [dec] [dec]
Explanation The resource depletion information.
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.
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 number of user and the resource type to be displayed.
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 number of user and the resource type has been displayed.
Recommended Action It is an informational message.
PFI_IFH Messages
Error Message%PKT_INFRA-PFI_IFH-2-FAIL [chars]: [chars] errno [[hex]] [[chars]]
Explanation There was a critical failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-PFI_IFH-2-FAIL_W_CODE [chars]: [chars] msg code [[hex]] err [[chars]]
Explanation There was a critical failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-PFI_IFH-2-FAIL_W_HDL [chars]: [chars] ifhandle [[hex]] err [[chars]]
Explanation There was a critical failure on the interface with this handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Include the output of show im chains ifh too to find out information about the interface which had the problem.
PFI Messages
Error Message%PKT_INFRA-PFI-3-ASSERT Fatal error - assert condition [chars] failed - [chars] thread [dec]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
PLATFORM_C12000_NETIO_LIB Messages
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
PLATFORM_HFR_NETIO_LIB Messages
Error Message%PKT_INFRA-PLATFORM_HFR_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_HFR_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
PLATFORM_LPTS_COM_IFIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in IFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics (not vital, no Moose congestion mode, low-priority squid queue) applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics (not vital, no Moose congestion mode, low-priority squid queue) applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics (not vital, no Moose congestion mode, low-priority squid queue) applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics (not vital, no Moose congestion mode, low-priority squid queue) applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG [chars]: Missing configuration for IFIB flow handling
Explanation No configuration for IFIB flow handling was found. Default characteristics (not vital, no Moose congestion mode, low-priority squid queue) will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG_MEMORY [chars]: Insufficient memory for IFIB flow handling configuration
Explanation Insufficient memory was available for storing the IFIB flow handling configuration. Default characteristics (not vital, no Moose congestion mode, low-priority squid queue) will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_LPTS_COM_NETIO Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_LPTS_LIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_LIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_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-PLATFORM_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.
PLATFORM_LPTS_PIFIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-BACKEND_EDM [chars]: EDM backend function [chars] failed: [chars]
Explanation An internal EDM backend function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-BAG [chars]: Bag function [chars] failed: [chars]
Explanation An internal bag function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CLEAR_EDM_INIT [chars]: Initialization for clear EDM failed: [chars]
Explanation Initialization for clear EDM failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_FLOW_MEMORY [chars]: Insufficient memory for flow configuration
Explanation There is insufficient memory for the flow configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_FLOW_UNDEFINED [chars]: Flow '[chars]' is undefined
Explanation The named flow type is not defined in the configuration. It will be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_FLOW_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]' definition
Explanation There is an unknown keyword in an input flow definition. The flow may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_MISSING [chars]: No input flow configuration
Explanation There is no input flow configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_NO_FLOWS [chars]: No flow characteristics defined
Explanation No flow characteristics have been defined. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_NO_POLICERS [chars]: No policers defined
Explanation No policers have been defined. All flows will be assigned to one large policer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_MEMORY [chars]: Insufficient memory for policer configuration
Explanation There is insufficient memory for the policer configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_OVERFLOW [chars]: Too many policers defined
Explanation Too many policers are defined in the input flow configuration. Some flows may be assigned to the default policer (0).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_INVALID [chars]: Invalid parameter '[chars]' after '[chars]' in policer '[dec]' definition
Explanation There is an invalid parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_MISSING [chars]: Missing parameter after '[chars]' in policer '[dec]' definition
Explanation There is a missing required parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in policer '[dec]' definition
Explanation There is an unknown keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_UNDEFINED_POLICER [chars]: flow '[chars]' references undefined policer '[dec]'
Explanation An input flow definition references an undefined policer. The flow will be configured to use policer 0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_OPEN [chars]: could not open event connection: [chars]
Explanation An internal error was detected when trying to open event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-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-PLATFORM_LPTS_PIFIB-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-PLATFORM_LPTS_PIFIB-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-PLATFORM_LPTS_PIFIB-3-FAILED_MIPC_NOTIF [chars]: too many failed MIPC Server notifications
Explanation Number of accumulated failed MIPC Server notifications exceeds the maximum expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FAILED_STATS_NOTIF [chars]: too many failed Metro Stats Manager notifications
Explanation Number of accumulated failed Metro Stats Manager notifications exceeds the maximum expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FAILED_TCAM_NOTIF [chars]: too many failed TCAM Manager notifications
Explanation Number of accumulated failed TCAM Manager notifications exceeds the maximum expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-GET_REGION_TOTAL [chars]: failed to get the total number of valid entries in [chars] TCAM region: [chars]
Explanation Failed to get the total number of valid entries in the given TCAM region.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-IFH_UIDB_INDEX [chars]: failed to find uidb index for interface handle [hex]: [chars]
Explanation Platform Mgr failed to find uidb index for the given 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-PLATFORM_LPTS_PIFIB-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-PLATFORM_LPTS_PIFIB-3-INVALID_REG_NAME [chars]: TCAM Manager listed a Pre-IFIB region with unrecognized name: [chars]
Explanation TCAM Manager listed a Pre-IFIB region with unrecognized 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-PLATFORM_LPTS_PIFIB-3-INVALID_TCAM_ENTRY_SIZE [chars]: Invalid TCAM entry size: [dec]
Explanation The given TCAM entry size 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-PLATFORM_LPTS_PIFIB-3-INVALID_TCAM_REGION_TYPE [chars]: Invalid TCAM region type: [dec]
Explanation The given TCAM region type 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-PLATFORM_LPTS_PIFIB-3-LTRACE_FAILED [chars] Failed to initialize the ltrace buffer
Explanation Failed to initialize the ltrace buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MIPC_BIND [chars]: failed to bind to Metro IPC server: [chars]
Explanation Failed to bind to Metro IPC 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-PLATFORM_LPTS_PIFIB-3-MIPC_INIT [chars]: failed to initialize with Metro IPC server: [chars]
Explanation Failed to initialize with Metro IPC 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-PLATFORM_LPTS_PIFIB-3-MIPC_NOTIF_ACK [chars]: failed to acknowledge an MIPC Server notification: [chars]
Explanation failed to acknowledge an MIPC Server notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MIPC_NOTIF_HANDLE [chars]: Failed to handle MIPC Server notification: [chars]
Explanation Failed to handle MIPC Server notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MIPC_SEND_POLICER [chars]: failed to send to MIPC Server to configure Metro policer [dec]: [chars]
Explanation Failed to send to MIPC Server to configure a Metro policer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSTATS_ALLOC [chars]: Metro Stats Manager failed to allocate stats entries: [chars]([dec])
Explanation Metro Stats Manager failed to allocate stats entries.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSTATS_ALLOC_NUM [chars]: Metro Stats Manager number of entries allocated [dec] is not number of entries asked for [dec]
Explanation Metro Stats Manager failed to allocate the number of stats entries asked for.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSTATS_BIND [chars]: Failed to connect to Metro Stats Manager
Explanation Failed to connect to Metro Stats 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-PLATFORM_LPTS_PIFIB-3-MSTATS_DEL_TABLE [chars]: Metro Stats Manager failed to delete table: [chars]([dec])
Explanation Metro Stats Manager failed to delete table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSTATS_FREE [chars]: Metro Stats Manager failed to free stats entries: [chars]([dec])
Explanation Metro Stats Manager failed to free stats entries.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSTATS_INIT [chars]: Failed to initialize stats table: [chars]
Explanation Failed to initialize stats table with Metro Stats 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-PLATFORM_LPTS_PIFIB-3-MSTATS_NEW_TABLE [chars]: Metro Stats Manager failed to create table: [chars]([dec])
Explanation Metro Stats Manager failed to create table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSTATS_RESET [chars]: Metro Stats Manager failed to reset client stats: [chars]([dec])
Explanation Metro Stats Manager failed to reset client stats.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSTATS_UNBIND [chars]: Failed to close the connection to Metro Stats Manager: [chars]([dec])
Explanation Failed to close the connection to Metro Stats 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-PLATFORM_LPTS_PIFIB-3-MSTATS_USE_TABLE [chars]: Metro Stats Manager failed to use existing table: [chars]([dec])
Explanation Metro Stats Manager failed to use existing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-PROGRAM_POLICER_ERRORED [chars]: failed to program the errored Metro policer [dec] for LPTS traffic: [chars]
Explanation Failed to program the errored Metro policer for LPTS traffic.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-PROGRAM_POLICERS [chars]: failed to program Metro policers for LPTS traffic: [chars]
Explanation Failed to program Metro policers for LPTS traffic.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-PROGRAM_REGION [chars]: Failed to program [chars] TCAM region: [chars]
Explanation Failed to program the given TCAM region.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-PROGRAM_REGION_PARTIAL [chars]: Failed to program range [[dec], [dec]) in [chars] TCAM region: [chars]
Explanation Failed to program the given range in TCAM region.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-REPROGRAM_TCAM [chars]: Failed to reprogram TCAM regions: [chars]
Explanation Failed to reprogram TCAM regions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_CLOSE [chars]: Cleanup for EDM failed: [chars]
Explanation Cleanup for EDM failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_INIT [chars]: Initialization for show EDM failed: [chars]
Explanation Initialization for show EDM failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-STATS_NOTIF_HANDLE [chars]: Failed to handle Metro Stats Manager notification: [chars]
Explanation Failed to handle Metro Stats Manager notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SYSDB [chars]: Sysdb function [chars] failed: [chars]
Explanation An internal sysdb function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_CLOSE [chars]: Failed to close connection to TCAM Manager: [chars]
Explanation Failed to close connection to TCAM 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-PLATFORM_LPTS_PIFIB-3-TCAM_CREATE_REGION [chars]: TCAM Manager failed to create region: [chars]
Explanation TCAM Manager failed to create region.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_DELETE_REGION [chars]: TCAM Manager failed to delete region, region handle [dec]: [chars]
Explanation TCAM Manager failed to delete region.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_ERROR_ACK [chars]: Failed to acknowledge TCAM error event: [chars]
Explanation Failed to acknowledge TCAM error 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-PLATFORM_LPTS_PIFIB-3-TCAM_INIT [chars]: failed to initialize TCAM regions: [chars]
Explanation Failed to initialize TCAM regions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_LIST_REGIONS [chars]: TCAM Manager failed to list Pre-IFIB regions: [chars]
Explanation TCAM Manager failed to list Pre-IFIB regions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_NOTIF_HANDLE [chars]: Failed to handle TCAM Manager notification: [chars]
Explanation Failed to handle TCAM Manager notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_OPEN [chars]: Failed to connect to TCAM Manager: [chars]
Explanation Failed to connect to TCAM 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-PLATFORM_LPTS_PIFIB-3-TCAM_OVERFLOW [chars]: not enough space for Pre-IFIB mandatory entries in TCAM region [chars]
Explanation TCAM space is not enough for all Pre-IFIB mandatory entries in the particular TCAM region.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_PREFIX_COMPRESS [chars]: failed to have IPv6 prefix compressed by TCAM Manager: [chars]
Explanation Failed to have IPv6 prefix compressed by TCAM 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-PLATFORM_LPTS_PIFIB-3-TCAM_READ [chars]: TCAM Manager failed to read entries: [chars]
Explanation TCAM Manager failed to read entries.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_READ_NUM [chars]: TCAM Manager number of bytes read [dec] is not number of bytes asked for [dec]
Explanation TCAM Manager failed to read the given number of bytes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_UPDATE_ENTRIES [chars]: TCAM Manager failed to update entries: [chars]
Explanation TCAM Manager failed to update entries.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_PFI Messages
Error Message%PKT_INFRA-PLATFORM_PFI-4-IFHANDLE_DECODE Could not map handle [hex] to slot
Explanation The interface handle cannot be mapped to a slot on the card.
Recommended Action Debug message only. *DEBUG*
Error Message%PKT_INFRA-PLATFORM_PFI-4-INIT Failed to initialise [chars]
Explanation An error occured when a module was going to be initialised. This may cause the process to terminate.
Recommended Action Restarting the process might help.
POS_SHIM_PARTNER Messages
Error Message%PKT_INFRA-POS_SHIM_PARTNER-3-FATAL_ERR Fatal error: [chars]: Err=[dec]
Explanation A fatal error occurred in pos_shim_partner which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PROTECT_NOTIFY Messages
Error Message%PKT_INFRA-PROTECT_NOTIFY-2-CONFIG_NO_MEM Config of notifications for i/f [hex] failed - no memory
Explanation An attempt to configure traffic protection fast notifications for a given interace failed due to no memory available to store the configuration record. 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-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.
TCAM_MGR_LIB Messages
Error Message%PKT_INFRA-TCAM_MGR_LIB-3-FATAL_ERR Fatal error: [chars]
Explanation A fatal error occurred in TCAM Manager library .
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-TCAM_MGR_LIB-3-V6_CMPR_FAILED v6 compression failed: [chars]
Explanation V6 prefix compression failed due lack of extended path
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
TCAM_MGR Messages
Error Message%PKT_INFRA-TCAM_MGR-3-FATAL_ERR Fatal error: [chars]: Err=[dec]
Explanation A fatal error occurred in TCAM Manager which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TCAM_MGR-3-LTRACE_FAILED [chars] Failed to initialize the ltrace buffer
Explanation Failed to initialize the ltrace buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
TNODE Messages
Error Message%PKT_INFRA-TNODE-3-CAPS_LOOKUP Capsulation lookup failed : [chars]
Explanation im_caps_lookup() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-CHAN_CREATE Failed to create channel : [chars]
Explanation Failed to create a channel using event_manager_create.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-EVENT_INIT IM to initialize linecard dpf notification event : [chars]
Explanation event_init_event() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-GET_RP_SLOT Failed to get RP slot number : [chars]
Explanation primary_rp_slot_number() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IF_FIND Failed to obtain interface handle ([chars]) : [chars]
Explanation im_interface_find() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IM_CTRLSVR_BIND Failed to bind to IM control server : [chars]
Explanation im_control_server_bind() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IM_DATAPATH_CTRL IM datapath control failed : [chars]
Explanation im_caps_datapath_control() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-IM_DATASVR_BIND Failed to bind to IM data server : [chars]
Explanation im_data_server_bind() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-LC_CONN_CREATE Failed to create transit-node lc connection : [chars]
Explanation event_conn_create() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-LC_CONN_OPEN Failed to open transit-node lc connection : [chars]
Explanation event_conn_open() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-PROC_RDY Failed to notify System Manager (Ready) : [chars]
Explanation sysmgr_proc_ready() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-SYSDB_BIND Failed to bind to SysDB : [chars]
Explanation sysdb_bind() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-SYSDB_COID Failed to obtain the file descriptor from SysDB connection : [chars]
Explanation sysdb_conn_to_coid() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TNODE-3-SYSDB_REG Failed to register for notification for dpf events : [chars]
Explanation sysdb_register_notification() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
tunnel_ea Messages
Error Message%PKT_INFRA-tunnel_ea-3-DEBUG_INIT_FAILED debug_init 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-tunnel_ea-3-EVENT_BLOCK_FAILED event_block 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-tunnel_ea-3-EVM_CREATE_FAILED Fatal error [chars] creating event manager
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-tunnel_ea-3-IMP_INIT_FAILED imp_init 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-tunnel_ea-3-PLATFORM_MANAGER_ERROR Platform Manger returned the error [chars], for interface [chars] handle [hex]
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-tunnel_ea-3-PROC_READY_FAILED (Sysmgr_proc_ready failed [hex]) [chars]
Explanation sysmgr had difficulty in processing the READY notification for tunnel_ea.
Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea
Error Message%PKT_INFRA-tunnel_ea-3-STATS_INIT_FAILED stats collecton init 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.'
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-2-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-2-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-2-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-2-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.
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.
VMR_BUILDER Messages
Error Message%PKT_INFRA-VMR_BUILDER-4-ANOMALY [chars]
Explanation A SW exception occurred in VMR_BUILDER Module
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.