-
Cisco IOS XR System Error Reference Guide for XR12000 Series Platform Specific Messages, Release 3.4
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Diagnostic Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Index
-
Table Of Contents
Packet Infrastructure 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:
•
PLATFORM_C12000_NETIO_LIB Messages
•
•
•
PA Messages
Error Message%PKT_INFRA-PA-2-CTX_CREATE [chars]: Can't create VRF context structures. VRF '[chars]' ([hex]) error [chars] ([unsigned int])
Explanation PA Can't create VFR context structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-2-INFRA_FAIL [chars]: [chars] failed rc=[dec]
Explanation There was a ENA infra call failure resulting in a failure to provide some infrastructure service.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-PA-2-RSI_ERROR RSI [chars] failed error [chars] ([unsigned int])
Explanation RSI error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-2-RSI_UNKNOWN_EVENT Unknown event from RSI event [unsigned int]
Explanation RSI sent unknown event
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ECM_SETRETRY_FAIL Error setting linear connection retry mechanism : [chars]
Explanation Failed to set linear connection retry mechanism in Port Arbitrator Client
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_ADD_SLICE [chars]: Assign of slice [chars] to node [hex] failed. ([chars])
Explanation The PA failed to assign an IFIB slice.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_BACKEND [chars]: [chars] failed
Explanation Sysdb backend api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_BAG [chars]: [chars] failed: [chars]
Explanation Bag api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_FM_MSG_TIMEOUT [chars]: [chars] update of slice [chars] to node [hex] timed out.
Explanation The PA failed to receive a response to an IFIB table update or an IFIB slice assignment update message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_LOCK [chars] line [dec]: error: [chars]
Explanation An attempt to lock a mutex failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_PIFIB_MSG_TIMEOUT [chars]: Pre-IFIB update for slice [chars] timed out.
Explanation The PA failed to receive a response to a critical Pre-IFIB update.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_SYSDB [chars]: [chars] failed
[chars]Explanation Sysdb api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-ERR_UNLOCK [chars] line [dec]: error: [chars]
Explanation An attempt to lock a mutex failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-3-EVENT_REGISTRATION_FAILED PA failed to connect to the event manager: [chars]
Explanation The PA process failed while attempting to connect to an event manager channel for the indicated subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PA-6-INFO_GENERAL [chars]: [chars]
Explanation The PA encountered some problem in genric nature or plain information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
PAK_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-3-DEBUGINITFAIL [chars]
Explanation An error occurred during packet debug events initilization. Refer to the error message for the particular cause.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-7-EXCEPTION_LITE packet exception, reason: [chars]
Explanation An software exception had occurred in the packet manager library. The client process terminated with exit code -1. The reason is that the client passed an invalid packet to packet manager library and led to the exception.
Recommended Action Normally the client process will restart and re-connect to packet manager. If any of these messages recur, call your technical support representative for assistance.
PAKPLATFORM Messages
Error Message%PKT_INFRA-PAKPLATFORM-3-CONNECTFAIL Connect to the packet server failed. Reason : [chars]
Explanation The platform driver was not able to connect to the packet server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKPLATFORM-6-SENDFAIL Send data to the packet server failed. Reason : [chars]
Explanation The platform driver was not able to send data to the packet manager. This could happen when the platform driver is trying to send the initilization information to the packet manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PAKSRV Messages
Error Message%PKT_INFRA-PAKSRV-2-ERR_MUTEX_REVIVAL Failed to revive the packet mutex, reason: [chars]
Explanation The packet subsystem failed to revive the packet mutex.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-2-MEMUTILMAPFAIL Memory mapping for [chars] failed, reason: [chars]
Explanation Memory maping for the specified area failed and packet server will restart.
Recommended Action If the error is not rectified after two or more restarts, please call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-3-BADPAK Corruption detected in the [chars] at [pointer] owned by packet [pointer] belonging to process [dec]
Explanation Consistency check detected corruption in the specified area of the specified packet. This will cause packet manager to restart. Please report the message and value to your technical support representative.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-3-DIAGFAIL Packet server: line [dec], fatal misalignment.
Explanation Packet server internal structures are misaligned. This is a fatal programming error. The value is a marker for tracking down the misalignment. Please report the message and value to your technical support representative.
Recommended Action Call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-3-ERR_MEM_ALLOC Memory allocation failed in process [dec] at [chars]
Explanation Packet server failed to allocate more memory.
Recommended Action It may be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-BADPTCL_DUMP [chars]: [chars]
Explanation Particle body corruption is detected. This message follows a BADPAK message and dumps the first few bytes of the particle body and the last few bytes of the one before.
Recommended Action None. This is message is only for debugging purpose.
Error Message%PKT_INFRA-PAKSRV-7-BCASTFAIL Failed to send broadcast message [dec] to client [dec], error: [chars]
Explanation Packet server failed to send a broadcast message to the client. This will result in the client being unaware of an event that occurred in the packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-CHANCREATEFAIL Failed to create a channel and event manager, error: [chars]
Explanation Packet server failed to create an event manager and channel. Clients will be unable to connect to packet server, and packet server will be unable to send and receive messages.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-CHUNKCREATEFAIL Chunk creation for packet headers failed
Explanation Could not allocate a chunk of memory for the packet headers.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-CONDWAITFAIL Conditional wait operation on [chars] in [chars] failed; reason [chars]
Explanation The packet subsystem failed to perform a conditional wait. This usually indicates a programming error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKSRV-7-DEBUGINITFAIL Packet server debug initialization: [chars] failed, error [chars]
Explanation The debug support initalization failed in the packet server. It will be restarted by sysmgr and should recover.
Recommended Action If packet manager is unable to start up after several restarts by sysmgr, please collect the 'sh log' output and contact your customer support representative.
Error Message%PKT_INFRA-PAKSRV-7-DEQUEUEFAIL Failed to remove client [dec] from clients list at [chars]
Explanation Packet server failed to remove the specified client from the client list queue. This may cause the client fail to reconnect to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ENQUEUEFAIL Fail to insert client [dec] into the list of clients at [chars]
Explanation Packet Server failed to insert a client into client list queue. This will prevent the client from connecting to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_CHKPT_OP [chars]: [chars] check point operation failed, reason : [chars]
Explanation A check point operation failed in packet manager.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_EVM_ATTACH Failed to attach event handler.
Explanation The packet subsystem encountered an error when attaching a handler for synchronous or asynchronous events.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_MUTEX_INIT Failed to initialize packet mutex, reason: [chars]
Explanation The packet subsystem failed to initialize the packet mutex.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_MUTEX_MONREG Packet server registration for mutex monitoring (revival) failed, error [chars]
Explanation Packet server failed to register for the mutex revival and will exit. It will be restarted by sysmgr.
Recommended Action If packet manager is unable to start up after several restarts by sysmgr, please collect the 'sh log' output and contact your customer support representative.
Error Message%PKT_INFRA-PAKSRV-7-ERR_MUTEX_OP Mutex [chars] operation on [chars] in [chars] failed; reason [chars]
Explanation The packet subsystem failed to perform the specified operation on the specified mutex. This usually indicates a programming error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKSRV-7-ERR_THREAD_ATTR_SET [chars]: Failed to set thread attributes
Explanation Packet server unable to set the thread's attributes.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_THREAD_CREATE Failed to create the [chars] thread
Explanation Packet server was unable to create the specified thread.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-ERR_THREAD_DETACH [chars]: Failed to detach from a new thread
Explanation Packet server was unable to detach from a new thread.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-FSVFAIL [chars]: fsv_register for name=[chars] failed, error : [dec]
Explanation An automatic register for one of the FSVs failed.
Recommended Action If any of these messages occur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-GET_RENDEZVOUS msg_chan_get_rendezvous failure: [chars].
Explanation msg_chan_get_rendezvous failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-GETNODENAMEFAIL failed to get node name in pakman server init
Explanation packet manager server unable to retrieve the hostname for node/linecard.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-GETPIDFAIL Failed to get client's pid at [chars]
Explanation Packet Server failed to get the client's pid. This will prevent the client from connecting to packet server.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-HSSDFAIL [chars]: hssd_register for name=[chars],size=[dec] failed, error : [dec]
Explanation An automatic register for one of the HSSDs failed.
Recommended Action If any of these messages occur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-INITFAIL Packet server initialization failed. Reason : [chars]
Explanation The packet subsystem was not able to initialize properly. It will be restarted by sysmgr and should recover.
Recommended Action If packet manager is unable to start up after several restarts by sysmgr, please collect the 'sh log' output and contact your customer support representative.
Error Message%PKT_INFRA-PAKSRV-7-MSGREPLYFAIL Failed to reply to client [dec] message [dec] at [chars]
Explanation Packet server failed to reply to a client's request. This will result in the client getting blocked on packet server.
Recommended Action Restart the specified client. If the problem is not rectified, contact customer support.
Error Message%PKT_INFRA-PAKSRV-7-PAKBCASTFAIL Broadcast to clients from packet server failed
Explanation Packet server failed to broadcast to message to its clients that it is about to restart.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-PARTICLEINITFAIL Particle initialization failed.
Explanation Packet server was not able to initialize the particles correctly and will restart.
Recommended Action If the error is not rectified after two or more restarts, please call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-QSM_ADD_SERVICE qsm_add_service failure: [chars].
Explanation qsm_add_service failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-SIGALRM Received SIGALRM unexpectedly, ignored.
Explanation An unexpected signal SIGALRM was received.
Recommended Action If any of these messages occur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-SIGNAL signal: [chars].
Explanation The packet subsystem encountered an error while performing a signal operation.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-SYSMGR_GET_NODE_STATE Failed to get node state from Sysmgr: [chars].
Explanation Packet server failed to get node state from sysmgr.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAKSRV-7-TIMER [chars]: timer: [chars].
Explanation The packet subsystem encountered an error while operating/handling a timer.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
PAKWATCH Messages
Error Message%PKT_INFRA-PAKWATCH-6-INFO Depletion level [dec] percent
for resource [chars]:Explanation The info about the current depletion level of the specified resource.
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-INFO_BODY [chars] [dec] [dec]
Explanation The resource depletion information in the following format: PROCESS_NAME PID COUNT
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-INFO_HEAD [chars] [chars] [chars]
Explanation The header for resource depletion information that follows this message. It is of the format: PROCESS_NAME PID COUNT
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-TRACEBACK [chars]
Explanation The traceback info about caller
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-USER_INFO Top [dec] users of [chars]:
Explanation The info about the top users of the specified resource.
Recommended Action It is an informational message.
Error Message%PKT_INFRA-PAKWATCH-6-USER_INFO2 Only [dec] users found using [chars].
Explanation The info about the total number of users of the specified resource.
Recommended Action It is an informational message.
PFI_IFH Messages
Error Message%PKT_INFRA-PFI_IFH-4-FAIL [chars]: [chars] ([hex])
Explanation An error occured in the ifh process. This may lead to problems elsewhere in the system.
Recommended Action If no further problems are seen, this warning may probably safely be ignored. If the message recurs, or problems are seen elsewhere in the system, take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PFI Messages
Error Message%PKT_INFRA-PFI-3-ASSERT Fatal error - assert condition [chars] failed - [chars] thread [dec]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
PLATFORM_C12000_NETIO_LIB Messages
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-PLATFORM_C12000_NETIO_LIB-4-GET_PPINDEX_INFO_FAIL Lookup for ppindex([dec]), pp_proto([dec]), failed due to [chars]
Explanation Unable to get the adjacency and next hop information from given ppindex.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
PLATFORM_HFR_NETIO_LIB Messages
Error Message%PKT_INFRA-PLATFORM_HFR_NETIO_LIB-4-FINT_IDB_NOT_FOUND Failed to obtain netio idb for FINT interface
Explanation The FINT idb is not yet created in netio. This could be a transient condition.
Recommended Action Please capture the following information and if traffic loss also is being observed Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. show logging show proc blocked
Error Message%PKT_INFRA-PLATFORM_HFR_NETIO_LIB-4-GET_MYNODEID_FAIL Failed to obtain my node id [chars]
Explanation Unable to determine my node id using platform api.
Recommended Action Please capture show proc ouput and show logging output - 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
PLATFORM_LPTS_COM_IFIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in IFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG [chars]: Missing configuration for IFIB flow handling
Explanation No configuration for IFIB flow handling was found. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG_MEMORY [chars]: Insufficient memory for IFIB flow handling configuration
Explanation Insufficient memory was available for storing the IFIB flow handling configuration. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
PLATFORM_LPTS_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 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_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when 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_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_LPTS_LIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
PLATFORM_LPTS_PIFIB Messages
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-BACKEND_EDM [chars]: EDM backend function [chars] failed: [chars]
Explanation An internal EDM backend function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-BAG [chars]: Bag function [chars] failed: [chars]
Explanation An internal bag function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CHKPT_INIT [chars]: Checkpoint Initialization function [chars] failed: [chars]
Explanation An internal Checkpoint function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_FLOW_MEMORY [chars]: Insufficient memory for flow configuration
Explanation There is insufficient memory for the flow configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in PIFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_MEMORY [chars]: Insufficient memory for policer configuration
Explanation There is insufficient memory for the policer configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_INVALID [chars]: Invalid parameter '[chars]' after '[chars]' in policer '[dec]' definition
Explanation There is an invalid parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_MISSING [chars]: Missing parameter after '[chars]' in policer '[dec]' definition
Explanation There is a missing required parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in policer '[dec]' definition
Explanation There is an unknown keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_UNDEFINED_POLICER [chars]: flow '[chars]' references undefined policer '[dec]'
Explanation An input flow definition references an undefined policer. The flow will be configured to use policer 0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_IFH_UIDB_INDEX Failed to find uidb index for interface handle [hex]
Explanation Failed to find uidb index for an given interface handle. It is likely to be caused by a programming bug or a programming problem happened in the past.
Recommended Action Run the command 'show uidb index' to verify whether the uidb index is created for the interface. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action When this issue happens, it will trigger an automatic restart. This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_NOTIF_Q_FULL The queue for notifications from [chars] is full
Explanation Too many notifications have been sent to the component. The queue to hold the notification has overflowed.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_OPEN [chars]: could not open event connection: [chars]
Explanation An internal error was detected when trying to open event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_ADD_FEAT2GRP [chars]: fm add feat to group failed for ISIS [chars]
Explanation An internal fm add feature to group function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_ADD_IFH2GRP [chars]: fm add ifh to group failed for ISIS [chars]
Explanation An internal fm add ifh to group function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_CREATE_GROUP [chars]: fm create group failed: [chars]
Explanation An internal fm create group function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_FEAT_PROCESSING [chars]: fm feature registration failed: [chars]
Explanation An internal fm feature registration function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-FM_REGISTER [chars]: fm_register failed: [chars]
Explanation An internal fm_register function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-HFA_REGISTER [chars]: hfa_register failed: [chars]
Explanation An internal hfa_register function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-LTRACE_INIT [chars]: ltrace_init2 failed: [chars]
Explanation An internal ltrace_init2 function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-MSG_ATTACH [chars]: Event Mgr function [chars] failed: [chars]
Explanation An internal Event Manager function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-NO_CONFIG [chars]: Missing configuration for PIFIB flow handling
Explanation No configuration for PIFIB flow handling was found. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_CLOSE [chars]: Cleanup for EDM failed: [chars]
Explanation Cleanup for EDM failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_INIT [chars]: Initialization for show EDM failed: [chars]
Explanation Initialization for show EDM failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-SYSDB [chars]: Sysdb function [chars] failed: [chars]
Explanation An internal sysdb function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-TCAM_FMT_TO_HFA_MAP [chars]: vmr_builder_program_tcam_fmt_from_hfa_map failed: [chars]
Explanation An tcam format to hfa mapping function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_MSTATS_ALLOC Failed to allocate HW counters.
Explanation It failed to allocate HW counters. It may be because of running out of HW counters or encountering internal error.
Recommended Action Disable the numbers of non crucial services which use HW counters.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_INVALID_REG_NAME Found the Pre-IFIB region with unrecognized name: [chars]
Explanation A Pre-IFIB region with unrecognized name is found in the TCAM. It is likely caused by a programming bug or a programming problem happened in the past.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_OVERFLOW Does not have enough space for the Pre-IFIB entry in TCAM region [chars]
Explanation TCAM space is not enough for all Pre-IFIB entries in the particular TCAM region. All control packets which do not have matching Pre-IFIB entries in TCAM will use SW path to forward to destinations.
Recommended Action Disable the numbers of services configured for the system.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_PREFIX_COMPRESS Failed to have IPv6 prefix compressed
Explanation IPv6 prefix compression failed because the line card has run out of internal resources for compressing a preifx. It shouldn't have any major impact on the system service. The in-bound (destined to the system) packets can still reach destinations through SW path.
Recommended Action Try either change the prefix length or change the prefix value of IPv6 addressses used in the system if possible.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT Failed to connect to [chars]: [chars]
Explanation An internal error was detected when trying to connect to the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of the respective component because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT [chars]: [chars]
Explanation An internal error was detected when trying to set up event connection.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_ATTACH Could not set up a timer object: [chars]
Explanation An internal error was detected when trying to allocate a timer object.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_LEAF_NEW Could not create a timer tree leaf objct: [chars]
Explanation An internal error was detected when trying to create a timer tree leaf object.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_INIT_POLICERS Failed to initialize the flow policer [dec]: [chars]
Explanation It failed to program a flow policer during initialization.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_LTRACE_INIT Failed to initialize the ltrace buffer
Explanation An internal error was detected when trying to initalize a ltrace buffer.
Recommended Action When this issue happens, it will not able to use ltrace buffer for debugging. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_INIT Failed to initialize with Metro IPC Server: [chars]
Explanation An internal error was detected when trying to initialize with Metro IPC server.
Recommended Action Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_NOTIF_ACK Failed to acknowledge a MIPC notification: [chars]
Explanation It is an internal error which the system failed to acknowledge a MIPC Server notification.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_MSTATS_INIT Failed to initialize stats table: [chars]
Explanation An internal error was detected when trying to initialize a statistic counter table.
Recommended Action Check the status of Metro Stats Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_NOTIF_HANDLE Failed to handle [chars] notification: [chars]
Explanation An internal error was detected when trying to handle a notification from the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_PROGRAM_ERRORED_POLICER Failed to reprogram the flow policer [dec]: [chars]
Explanation An internal error was detected when trying to program the flow policer.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_REPROGRAM_POLICERS Failed to program the flow policer [dec]: [chars]
Explanation It failed to reprogram a flow policer when it had received a request to reprogram all flow policers to HW.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_SYSDB_DATALIST_CREATE Sysdb datalist function failed to create an object handle: [chars]
Explanation An internal sysdb function failed.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.