Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3 - Packet Infrastructure Messages [Cisco IOS XR Software (End-of-Sale)]

Table Of Contents

Packet Infrastructure Messages

FEA_DLL Messages

FEATURE_LPTS Messages

FMGR Messages

FWD_NETIO_DLL Messages

HFR_FWD Messages

HFR_PFI Messages

LPTS_PA_FGID_DB Messages

PAK_CAPTURE Messages

PLATFORM_HFR_NETIO_LIB Messages

PLATFORM_LPTS_COM_IFIB Messages

PLATFORM_LPTS_COM_NETIO Messages

PLATFORM_LPTS_LIB Messages

PLATFORM_LPTS_PIFIB Messages

TCAM_MGR_LIB Messages

TCAM_MGR Messages

tunnel_ea 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:

•FEA_DLL Messages

•FEATURE_LPTS Messages

•FMGR Messages

•FWD_NETIO_DLL Messages

•HFR_FWD Messages

•HFR_PFI Messages

•LPTS_PA_FGID_DB Messages

•PAK_CAPTURE Messages

•PLATFORM_HFR_NETIO_LIB Messages

•PLATFORM_LPTS_COM_IFIB Messages

•PLATFORM_LPTS_COM_NETIO Messages

•PLATFORM_LPTS_LIB Messages

•PLATFORM_LPTS_PIFIB Messages

•TCAM_MGR_LIB Messages

•TCAM_MGR Messages

•tunnel_ea Messages

FEA_DLL Messages
Error Message     
%PKT_INFRA-FEA_DLL-3-MSTATS_ALLOC_ERR MSTATS [chars] region: [chars]
Explanation Feature EA DLL failed to allocate statistics entry for ACL. Number of ACL entries requiring statistics entries has exceeded statistics entries reserved for security ACLs on this line card. As a result, per ACE hardware accouting for the failed ACL entries is not available. There is no impact on ability to apply security ACLs in hardware.
Recommended Action If per ACE hardware accouting is needed for ACL in error message, reduce security ACL configuration on this line card.
Error Message     
%PKT_INFRA-FEA_DLL-3-MSTATS_ERR MSTATS [chars] error: [chars]
Explanation Feature EA DLL encountered error on initializing interface with hardware statistics API. Process will be restarted automatically. On restart, Feature EA DLL will initialize interface with hardware statistics API and no action needs to be taken.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FEA_DLL-3-REPRGM_ERROR Errored during scrub reprogramming [chars] : [chars]
Explanation TCAM entries are reprogrammed every 24 hours to ensure accuracy of hardware entries programmed earlier on user configuration or system changes. This message lists the ACL for which errors have occured during reprogramming.
Recommended Action Detach ACL in the error message from all interfaces of the line card where issue is seen. Now, re-attach ACL to the interfaces. Note that, there is a security hole during re-attachment operation window for these interfaces.
Error Message     
%PKT_INFRA-FEA_DLL-3-TCAM_ERR TCAM [chars] error: [chars]
Explanation Feature EA DLL encountered error in completing TCAM operation. This can lead to mismatch between hardware and software configuration.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FEA_DLL-3-TCAM_LIMIT TCAM [chars] limit exceeded
Explanation This message will typically occur when permissible single region size is exceeded or total number of entries allowed in TCAM for a given application is exceeded.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-FEA_DLL-3-UIDB_ERR UIDB [chars] error: [chars] : [chars]
Explanation UIDB stores the reference to ACL entries programmed in TCAM for the interface, protocol and direction. This error message is due to one of the following reasons: 1. Initialization failure of Feature EA DLL and UIDB manager interface. 2. Failure to set reference of hardware entries programmed or removed for security ACL in UIDB on configuration or system changes. This failure can lead to mismatch between hardware and software configuration.
Recommended Action If the failure is on initialization, process restart is done automatically. No manual action is required. If the failure is to set configuration bits in hardware on detaching a security ACL from interface, attach and detach security ACL again on the interface. In all other cases, detach ACL in the error message from all interfaces of the line card where issue is seen. Now, re-attach ACL to the interfaces.

FEATURE_LPTS Messages
Error Message     
%PKT-INFRA-FEATURE_LPTS-3-ERR_DOUBLE_FREE Double free of FGID [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-FEATURE_LPTS-3-ERR_UNALLOCATED_FREE Attempt to free unallocated FGID [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-FEATURE_LPTS-3-ERR_UNKNOWN_FGID_DB_ERROR Unknown error from FGID-DB, [chars] FGID [dec] id [dec]: [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.

FMGR Messages
Error Message     
%PKT_INFRA-FMGR-3-MATCH_TYPE_IN_ACL_NOT_SUPPORTED [chars]
Explanation The following match criteria specified in an ACL are not supported in a QoS policy: Source Port (ipv4), Packet Length. However, rest of the match criteria in the ACE (ignoring the unsupported types) have been programmed in hardware.
Recommended Action If the partial match criteria is not acceptable, the QoS policy should be removed from the interface and modified to use supported match-types. Use 'no service-policy ' in interface configuration mode to remove the QoS policy.
Error Message     
%PKT_INFRA-FMGR-3-SUB_ID_MSG_TOO_LARGE [chars]
Explanation A message from Platform Manager containing set/unset notifications for sub-interface VLAN IDs was too large and had to be dropped because enough memory could not be allocated. As a result, for a 'set' notification, QoS was not enabled for the reported VLANs. For an unset notification, QoS was not disabled for the reported VLANs.
Recommended Action Restart feature_mgr process. Example: In exec mode, 'process restart feature_mgr location 0/1/CPU0' This will cause all notifications to be delivered to Feature Manager again. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FMGR-3-TCAM_MGR_ERROR [chars] (error = [chars])
Explanation Request to TCAM Manager for programming QoS match rules into TCAM failed. Feature manager sends this request to TCAM manager when a policy is attached/removed to/from an interface (or fabric), when there is a change in bundle membership or when an ACL which is used in a QoS policy is modified. The most likely cause of this error is not enough space remaining in TCAM.
Recommended Action Try modifying QoS and ACL configuration to reduce TCAM usage. If TCAM space doesn't seem to be the reason, try removing and re-applying the QoS policy. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FMGR-4-UIDB_SET_WARNING Feature Mgr failed to program UIDB for QoS. (reason: [chars])
Explanation Feature Mgr failed to program the correct QoS related information in UIDB (interface data structure in hardware) when enabling/disabling QoS on the interface. The most likely cause of this message is deletion of a vlan sub-interface when there is a qos policy attached on the parent physical interface. In this case, the message is harmless and can be ignored. The reason this happens is because, the feature_mgr process tries to reset QoS related flags in the UIDB, but by that time the UIDB entry has already been deleted. It is possible, though very unlikely, for this message to appear in the following cases: 1) A QoS policy is attached on an interface. 2) QoS policy is removed from an interface. 3) Vlan-id is configured for a sub-interface and a QoS policy exists on the associated physical interface. 4) Vlan-id is un-configured on a sub-interface and a QoS policy exists on the associated physical interface. 5) When all members of a bundle go 'down'. In such cases, the warning message indicates that there could be a problem in enabling/disabling QoS on the interface.
Recommended Action For case 5 mentioned above, message can be ignored. For cases 1, 3 try removing and re-applying the QoS policy. For case 2, try applying the policy and removing it again. For case 4, delete the sub-interface itself and if needed re-create it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FMGR-7-INIT_ERROR [chars] (error: [chars]). Feature Mgr initialization failed!
Explanation Feature Mgr process failed to initialize correctly. In this case process will restart.
Recommended Action No action needed. Process will restart automatically. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

FWD_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-EGRESSQ_CREATE_FAILED fwd: egressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the egressq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-3-FABRICQ_CREATE_FAILED fwd: fabricq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the fabricq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-3-FATAL fwd: fatal error encountered, reason=[chars]
Explanation Null Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason=[chars], errno=[dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-3-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-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-3-INGRESSQ_CREATE_FAILED fwd: ingressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec]
Explanation FWD was not able to create one of the ingressq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-3-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-NOT_YET_IMPLEMENTED fwd: this function is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-3-PAK_PROC_ERR [chars] : [chars], pak = [hex], rc = [hex]

Explanation There was an packet processing error. Possible causes 1) Unable to retrieve fabric dest addr from inside the pkt 2) Error setting/getting input ifh from pkt
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-4-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb. Could be transient.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-FWD_NETIO_DLL-6-INFO fwd: [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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.

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.

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-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
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_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

PLATFORM_LPTS_LIB Messages
Error Message     
%PKT_INFRA-PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.

PLATFORM_LPTS_PIFIB Messages
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_IFH_UIDB_INDEX Failed to find uidb index for interface handle [hex]
Explanation Failed to find uidb index for an given interface handle. It is likely to be caused by a programming bug or a programming problem happened in the past.
Recommended Action Run the command 'show uidb index' to verify whether the uidb index is created for the interface. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action When this issue happens, it will trigger an automatic restart. This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_NOTIF_Q_FULL The queue for notifications from [chars] is full
Explanation Too many notifications have been sent to the component. The queue to hold the notification has overflowed.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_MSTATS_ALLOC Failed to allocate HW counters.
Explanation It failed to allocate HW counters. It may be because of running out of HW counters or encountering internal error.
Recommended Action Disable the numbers of non crucial services which use HW counters.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_INVALID_REG_NAME Found the Pre-IFIB region with unrecognized name: [chars]
Explanation A Pre-IFIB region with unrecognized name is found in the TCAM. It is likely caused by a programming bug or a programming problem happened in the past.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_OVERFLOW Does not have enough space for the Pre-IFIB entry in TCAM region [chars]
Explanation TCAM space is not enough for all Pre-IFIB entries in the particular TCAM region. All control packets which do not have matching Pre-IFIB entries in TCAM will use SW path to forward to destinations.
Recommended Action Disable the numbers of services configured for the system.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_PREFIX_COMPRESS Failed to have IPv6 prefix compressed
Explanation IPv6 prefix compression failed because the line card has run out of internal resources for compressing a preifx. It shouldn't have any major impact on the system service. The in-bound (destined to the system) packets can still reach destinations through SW path.
Recommended Action Try either change the prefix length or change the prefix value of IPv6 addressses used in the system if possible.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT Failed to connect to [chars]: [chars]
Explanation An internal error was detected when trying to connect to the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of the respective component because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT [chars]: [chars]
Explanation An internal error was detected when trying to set up event connection.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_ATTACH Could not set up a timer object: [chars]
Explanation An internal error was detected when trying to allocate a timer object.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_LEAF_NEW Could not create a timer tree leaf objct: [chars]
Explanation An internal error was detected when trying to create a timer tree leaf object.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_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 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 flow policers [chars]
Explanation It failed to reprogram flow policers when it had received a request to reprogram flow policers to HW.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_SYSDB_DATALIST_CREATE Sysdb datalist function failed to create an object handle: [chars]
Explanation An internal sysdb function failed.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_TCAM_INIT Failed to initialize TCAM regions: [chars]
Explanation An internal error was detected when trying to initialize TCAM regions.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

TCAM_MGR_LIB Messages
Error Message     
%PKT_INFRA-TCAM_MGR_LIB-3-INTERNAL_ERR Internal error: [chars]
Explanation An internal error occurred in TCAM Manager which involves exiting the process. After the TCAM Manager process restarts, the error should have been cleared. *DDTS*
Recommended Action Collect the configuration, syslog and coredump file. Attach them to the ddts. After the process restarts automatically, the error should have been cleared and no user action is needed.
Error Message     
%PKT_INFRA-TCAM_MGR_LIB-3-V6_CMPR_FAILED v6 source prefix compression failed: [chars]
Explanation V6 source prefix compression failed due to lack of extended path. This failure indicates that a particular v6 prefix indicated in the message will not be compressed. There are 3 workarounds of this problem. 1) do not use this entry. 2) change the prefix length. 3) change the prefix value. For example if an entry failed during an ACL programming then try removing that ACE indicated in the message and apply the configuration again. *DDTS*
Recommended Action Ouput generated by this message and related config, for example v6 ACL failed in case of ACL configuration. Attach them to the ddts. This failure indicates that a particular v6 prefix indicated in the message will not be compressed. There are 3 workarounds of this problem. 1) do not use this entry. 2) change the prefix length. 3) change the prefix value. For example if an entry failed during an ACL programming then try removing that ACE indicated in the message and apply the configuration again.

TCAM_MGR Messages
Error Message     
%PKT_INFRA-TCAM_MGR-3-INTERNAL_ERR Internal error: [chars]: [chars]
Explanation An internal error occurred in TCAM Manager which involves exiting the process. After the TCAM Manager process restarts, the error should have been cleared. *DDTS*
Recommended Action Collect the configuration, syslog and coredump file. Attach them to the ddts. After the process restarts automatically, the error should have been cleared and no user action is needed.

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

	Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3
	Packet Infrastructure Messages
Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3 Overview Preface Diagnostic Messages Driver Messages Fabric Messages High Availability (HA) Messages Installation Messages Internet Protocol (IP) Messages Layer 2 (L2) Messages Media Messages Manageability (MGBL) Messages Packet Infrastructure Messages Platform Messages Quality of Service (QOS) Messages Routing Messages	Download this chapter Packet Infrastructure Messages Download the complete book Book-level PDF: Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages (PDF - 2 MB) Feedback Table Of Contents Packet Infrastructure Messages FEA_DLL Messages FEATURE_LPTS Messages FMGR Messages FWD_NETIO_DLL Messages HFR_FWD Messages HFR_PFI Messages LPTS_PA_FGID_DB Messages PAK_CAPTURE Messages PLATFORM_HFR_NETIO_LIB Messages PLATFORM_LPTS_COM_IFIB Messages PLATFORM_LPTS_COM_NETIO Messages PLATFORM_LPTS_LIB Messages PLATFORM_LPTS_PIFIB Messages TCAM_MGR_LIB Messages TCAM_MGR Messages tunnel_ea 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: •FEA_DLL Messages •FEATURE_LPTS Messages •FMGR Messages •FWD_NETIO_DLL Messages •HFR_FWD Messages •HFR_PFI Messages •LPTS_PA_FGID_DB Messages •PAK_CAPTURE Messages •PLATFORM_HFR_NETIO_LIB Messages •PLATFORM_LPTS_COM_IFIB Messages •PLATFORM_LPTS_COM_NETIO Messages •PLATFORM_LPTS_LIB Messages •PLATFORM_LPTS_PIFIB Messages •TCAM_MGR_LIB Messages •TCAM_MGR Messages •tunnel_ea Messages FEA_DLL Messages Error Message %PKT_INFRA-FEA_DLL-3-MSTATS_ALLOC_ERR MSTATS [chars] region: [chars] Explanation Feature EA DLL failed to allocate statistics entry for ACL. Number of ACL entries requiring statistics entries has exceeded statistics entries reserved for security ACLs on this line card. As a result, per ACE hardware accouting for the failed ACL entries is not available. There is no impact on ability to apply security ACLs in hardware. Recommended Action If per ACE hardware accouting is needed for ACL in error message, reduce security ACL configuration on this line card. Error Message %PKT_INFRA-FEA_DLL-3-MSTATS_ERR MSTATS [chars] error: [chars] Explanation Feature EA DLL encountered error on initializing interface with hardware statistics API. Process will be restarted automatically. On restart, Feature EA DLL will initialize interface with hardware statistics API and no action needs to be taken. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FEA_DLL-3-REPRGM_ERROR Errored during scrub reprogramming [chars] : [chars] Explanation TCAM entries are reprogrammed every 24 hours to ensure accuracy of hardware entries programmed earlier on user configuration or system changes. This message lists the ACL for which errors have occured during reprogramming. Recommended Action Detach ACL in the error message from all interfaces of the line card where issue is seen. Now, re-attach ACL to the interfaces. Note that, there is a security hole during re-attachment operation window for these interfaces. Error Message %PKT_INFRA-FEA_DLL-3-TCAM_ERR TCAM [chars] error: [chars] Explanation Feature EA DLL encountered error in completing TCAM operation. This can lead to mismatch between hardware and software configuration. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FEA_DLL-3-TCAM_LIMIT TCAM [chars] limit exceeded Explanation This message will typically occur when permissible single region size is exceeded or total number of entries allowed in TCAM for a given application is exceeded. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-FEA_DLL-3-UIDB_ERR UIDB [chars] error: [chars] : [chars] Explanation UIDB stores the reference to ACL entries programmed in TCAM for the interface, protocol and direction. This error message is due to one of the following reasons: 1. Initialization failure of Feature EA DLL and UIDB manager interface. 2. Failure to set reference of hardware entries programmed or removed for security ACL in UIDB on configuration or system changes. This failure can lead to mismatch between hardware and software configuration. Recommended Action If the failure is on initialization, process restart is done automatically. No manual action is required. If the failure is to set configuration bits in hardware on detaching a security ACL from interface, attach and detach security ACL again on the interface. In all other cases, detach ACL in the error message from all interfaces of the line card where issue is seen. Now, re-attach ACL to the interfaces. FEATURE_LPTS Messages Error Message %PKT-INFRA-FEATURE_LPTS-3-ERR_DOUBLE_FREE Double free of FGID [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-FEATURE_LPTS-3-ERR_UNALLOCATED_FREE Attempt to free unallocated FGID [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-FEATURE_LPTS-3-ERR_UNKNOWN_FGID_DB_ERROR Unknown error from FGID-DB, [chars] FGID [dec] id [dec]: [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. FMGR Messages Error Message %PKT_INFRA-FMGR-3-MATCH_TYPE_IN_ACL_NOT_SUPPORTED [chars] Explanation The following match criteria specified in an ACL are not supported in a QoS policy: Source Port (ipv4), Packet Length. However, rest of the match criteria in the ACE (ignoring the unsupported types) have been programmed in hardware. Recommended Action If the partial match criteria is not acceptable, the QoS policy should be removed from the interface and modified to use supported match-types. Use 'no service-policy ' in interface configuration mode to remove the QoS policy. Error Message %PKT_INFRA-FMGR-3-SUB_ID_MSG_TOO_LARGE [chars] Explanation A message from Platform Manager containing set/unset notifications for sub-interface VLAN IDs was too large and had to be dropped because enough memory could not be allocated. As a result, for a 'set' notification, QoS was not enabled for the reported VLANs. For an unset notification, QoS was not disabled for the reported VLANs. Recommended Action Restart feature_mgr process. Example: In exec mode, 'process restart feature_mgr location 0/1/CPU0' This will cause all notifications to be delivered to Feature Manager again. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FMGR-3-TCAM_MGR_ERROR [chars] (error = [chars]) Explanation Request to TCAM Manager for programming QoS match rules into TCAM failed. Feature manager sends this request to TCAM manager when a policy is attached/removed to/from an interface (or fabric), when there is a change in bundle membership or when an ACL which is used in a QoS policy is modified. The most likely cause of this error is not enough space remaining in TCAM. Recommended Action Try modifying QoS and ACL configuration to reduce TCAM usage. If TCAM space doesn't seem to be the reason, try removing and re-applying the QoS policy. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FMGR-4-UIDB_SET_WARNING Feature Mgr failed to program UIDB for QoS. (reason: [chars]) Explanation Feature Mgr failed to program the correct QoS related information in UIDB (interface data structure in hardware) when enabling/disabling QoS on the interface. The most likely cause of this message is deletion of a vlan sub-interface when there is a qos policy attached on the parent physical interface. In this case, the message is harmless and can be ignored. The reason this happens is because, the feature_mgr process tries to reset QoS related flags in the UIDB, but by that time the UIDB entry has already been deleted. It is possible, though very unlikely, for this message to appear in the following cases: 1) A QoS policy is attached on an interface. 2) QoS policy is removed from an interface. 3) Vlan-id is configured for a sub-interface and a QoS policy exists on the associated physical interface. 4) Vlan-id is un-configured on a sub-interface and a QoS policy exists on the associated physical interface. 5) When all members of a bundle go 'down'. In such cases, the warning message indicates that there could be a problem in enabling/disabling QoS on the interface. Recommended Action For case 5 mentioned above, message can be ignored. For cases 1, 3 try removing and re-applying the QoS policy. For case 2, try applying the policy and removing it again. For case 4, delete the sub-interface itself and if needed re-create it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FMGR-7-INIT_ERROR [chars] (error: [chars]). Feature Mgr initialization failed! Explanation Feature Mgr process failed to initialize correctly. In this case process will restart. Recommended Action No action needed. Process will restart automatically. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. FWD_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-EGRESSQ_CREATE_FAILED fwd: egressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec] Explanation FWD was not able to create one of the egressq queues. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-FWD_NETIO_DLL-3-FABRICQ_CREATE_FAILED fwd: fabricq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec] Explanation FWD was not able to create one of the fabricq queues. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-FWD_NETIO_DLL-3-FATAL fwd: fatal error encountered, reason=[chars] Explanation Null Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason=[chars], errno=[dec] Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FWD_NETIO_DLL-3-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-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex]. Explanation FWD was supplied with a plim interface that does not have an idb yet. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-FWD_NETIO_DLL-3-INGRESSQ_CREATE_FAILED fwd: ingressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc = [dec] Explanation FWD was not able to create one of the ingressq queues. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-FWD_NETIO_DLL-3-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-NOT_YET_IMPLEMENTED fwd: this function is not yet implemented Explanation FWD, a function was not implemented. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FWD_NETIO_DLL-3-PAK_PROC_ERR [chars] : [chars], pak = [hex], rc = [hex] Explanation There was an packet processing error. Possible causes 1) Unable to retrieve fabric dest addr from inside the pkt 2) Error setting/getting input ifh from pkt Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-FWD_NETIO_DLL-4-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb. Could be transient. Explanation FWD was supplied with a plim interface that does not have an idb yet. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-FWD_NETIO_DLL-6-INFO fwd: [chars] Explanation The fwd encountered an error that would lead to degraded service. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. 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. 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. 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. 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-ERR_MEM_ALLOC Failed to allocate memory Explanation The system failed to allocate memory. It's likely that the system is running low in memory. Recommended Action This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-PLATFORM_LPTS_COM_IFIB-7-ERR_DEBUG_INIT [chars]: [chars] Explanation An error was returned when initializing debug. The facility to debug the component may not work. 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_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars] Explanation An error was returned when initializing debug. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars] Explanation An error was returned when registering debug. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. PLATFORM_LPTS_LIB Messages Error Message %PKT_INFRA-PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT [chars]: [chars] Explanation An error was returned when initializing debug. The facility to debug the component may not work. Recommended Action Debug message only. No action is required. PLATFORM_LPTS_PIFIB Messages Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_IFH_UIDB_INDEX Failed to find uidb index for interface handle [hex] Explanation Failed to find uidb index for an given interface handle. It is likely to be caused by a programming bug or a programming problem happened in the past. Recommended Action Run the command 'show uidb index' to verify whether the uidb index is created for the interface. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC Failed to allocate memory Explanation The system failed to allocate memory. It's likely that the system is running low in memory. Recommended Action When this issue happens, it will trigger an automatic restart. This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-3-ERR_NOTIF_Q_FULL The queue for notifications from [chars] is full Explanation Too many notifications have been sent to the component. The queue to hold the notification has overflowed. Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_MSTATS_ALLOC Failed to allocate HW counters. Explanation It failed to allocate HW counters. It may be because of running out of HW counters or encountering internal error. Recommended Action Disable the numbers of non crucial services which use HW counters. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_INVALID_REG_NAME Found the Pre-IFIB region with unrecognized name: [chars] Explanation A Pre-IFIB region with unrecognized name is found in the TCAM. It is likely caused by a programming bug or a programming problem happened in the past. Recommended Action Check the status of TCAM Manger because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_OVERFLOW Does not have enough space for the Pre-IFIB entry in TCAM region [chars] Explanation TCAM space is not enough for all Pre-IFIB entries in the particular TCAM region. All control packets which do not have matching Pre-IFIB entries in TCAM will use SW path to forward to destinations. Recommended Action Disable the numbers of services configured for the system. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_PREFIX_COMPRESS Failed to have IPv6 prefix compressed Explanation IPv6 prefix compression failed because the line card has run out of internal resources for compressing a preifx. It shouldn't have any major impact on the system service. The in-bound (destined to the system) packets can still reach destinations through SW path. Recommended Action Try either change the prefix length or change the prefix value of IPv6 addressses used in the system if possible. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT Failed to connect to [chars]: [chars] Explanation An internal error was detected when trying to connect to the respective component. Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of the respective component because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT [chars]: [chars] Explanation An error was returned when initializing debug. The facility to debug the component may not work. Recommended Action Debug message only. No action is required. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT [chars]: [chars] Explanation An internal error was detected when trying to set up event connection. Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_ATTACH Could not set up a timer object: [chars] Explanation An internal error was detected when trying to allocate a timer object. Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_LEAF_NEW Could not create a timer tree leaf objct: [chars] Explanation An internal error was detected when trying to create a timer tree leaf object. Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_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 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 flow policers [chars] Explanation It failed to reprogram flow policers when it had received a request to reprogram flow policers to HW. Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_SYSDB_DATALIST_CREATE Sysdb datalist function failed to create an object handle: [chars] Explanation An internal sysdb function failed. Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %PKT_INFRA-PLATFORM_LPTS_PIFIB-7-ERR_TCAM_INIT Failed to initialize TCAM regions: [chars] Explanation An internal error was detected when trying to initialize TCAM regions. Recommended Action Check the status of TCAM Manger because this issue is likely related to it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. TCAM_MGR_LIB Messages Error Message %PKT_INFRA-TCAM_MGR_LIB-3-INTERNAL_ERR Internal error: [chars] Explanation An internal error occurred in TCAM Manager which involves exiting the process. After the TCAM Manager process restarts, the error should have been cleared. DDTS Recommended Action Collect the configuration, syslog and coredump file. Attach them to the ddts. After the process restarts automatically, the error should have been cleared and no user action is needed. Error Message %PKT_INFRA-TCAM_MGR_LIB-3-V6_CMPR_FAILED v6 source prefix compression failed: [chars] Explanation V6 source prefix compression failed due to lack of extended path. This failure indicates that a particular v6 prefix indicated in the message will not be compressed. There are 3 workarounds of this problem. 1) do not use this entry. 2) change the prefix length. 3) change the prefix value. For example if an entry failed during an ACL programming then try removing that ACE indicated in the message and apply the configuration again. DDTS Recommended Action Ouput generated by this message and related config, for example v6 ACL failed in case of ACL configuration. Attach them to the ddts. This failure indicates that a particular v6 prefix indicated in the message will not be compressed. There are 3 workarounds of this problem. 1) do not use this entry. 2) change the prefix length. 3) change the prefix value. For example if an entry failed during an ACL programming then try removing that ACE indicated in the message and apply the configuration again. TCAM_MGR Messages Error Message %PKT_INFRA-TCAM_MGR-3-INTERNAL_ERR Internal error: [chars]: [chars] Explanation An internal error occurred in TCAM Manager which involves exiting the process. After the TCAM Manager process restarts, the error should have been cleared. DDTS Recommended Action Collect the configuration, syslog and coredump file. Attach them to the ddts. After the process restarts automatically, the error should have been cleared and no user action is needed. 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.'
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks