-
Cisco IOS XR System Error Message Reference Guide, R3.8.4
-
Preface
-
Overview
-
ACL Messages
-
Application Infrastructure Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
HA Messages
-
Installation Messages
-
IP Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Layer 3 Messages
-
License Messages
-
Media Messages
-
MGBL Messages
-
Operating System Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service Messages
-
Routing Messages
-
Security Messages
-
Service Messages
-
SNMP Messages
-
System Database Messages
-
Index
-
Feedback
Table Of Contents
Packet Infrastructure Messages
C12000_FWD_CLIENT_DLL Messages
PLATFORM_C12000_NETIO_LIB Messages
PLATFORM_HFR_NETIO_LIB Messages
Packet Infrastructure Messages
This section contains all Packet Infrastructure related System Error Messages, including ifmgr, tunnels, bundlemgr, pakman, and so forth.
BFM_API Messages
Error Message%PKT_INFRA-BFM_API-3-FATAL bfm: fatal error encountered, reason equals [chars]
Explanation iq manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-FATAL_2 bfm: fatal error encountered, reason equals [chars], errno equals [dec]
Explanation bfm encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-GEN_INFO bfm: general information,[chars]
Explanation The BFM's informational message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-INFO bfm: service degrading error, reason equals [chars]
Explanation The bfm encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-MALLOC_FAILED BFM: fatal memory allocation error for [dec] bytes
Explanation BFM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-BFM_API-3-NOT_YET_IMPLEMENTED bfm: this function [chars] is not yet implemented
Explanation BFM, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-3-USAGE bfm: invalid option [chars] passed to bfm server
Explanation Startup option supplied to BFM is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-4-PTCL_TYPE_WRONG BFM: ptcl type [chars] is not as expected type is [chars]
Explanation BFM encountered a warning condition
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM_API-7-DEBUG bfm: general debug,[chars]
Explanation The BFM's debug message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
BFM Messages
Error Message%PKT_INFRA-BFM-2-UNKNOWN_PLATFORM an unknown platform type.
Explanation platform_get_type returned an unknown platform type.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-BFM-3-BCAST_FAILED BFM: fatal event msg type [dec] bradcast for client jid [dec] error [chars]
Explanation BFM encountered a fatal message event send error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-DEGRAD_INFO bfm: service degrading error, reason equals [chars]
Explanation The bfm encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-EDM BFM: fatal edm error [chars] due to [chars]
Explanation BFM encountered a fatal edm error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-FATAL bfm: fatal error encountered, reason equals [chars]
Explanation iq manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-FATAL_2 bfm: fatal error encountered, reason equals [chars], errno equals [dec]
Explanation bfm encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-FATAL_3 bfm: fatal error encountered, reason equals [chars], error equals [chars]
Explanation bfm encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-GEN_INFO bfm: general information,[chars]
Explanation The BFM's informational message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-MALLOC_FAILED BFM: fatal memory allocation error for [dec] bytes
Explanation BFM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-BFM-3-MSGRPLY_FAILED BFM: fatal msg reply error for client [dec] msg type [dec]
Explanation BFM encountered a fatal message reply error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-NOT_YET_IMPLEMENTED bfm: this function [chars] is not yet implemented
Explanation BFM, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-POOL_STATUS_UNKNOWN A Pool with ID [dec] in region ID [dec] found to be in *unknown* state
Explanation BFM encountered a fatal pool state error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-USAGE bfm: invalid option [chars] passed to bfm server
Explanation Startup option supplied to BFM is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-3-WARNING bfm: An error encountered, reason equals [chars], error equals [chars]
Explanation iq manager encountered an error and is not able recover from the error. A reason text will be supplied call support with this text. Some of the functionality may not work until this error is removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-BFM-4-INIT_ERROR bfm: init error encountered, reason equals [chars], attempt equals [dec], error equals [chars]
Explanation bfm encountered a error and is not able to recover from the error trying again. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
C12000_FWD_CLIENT_DLL Messages
Error Message%PKT_INFRA-C12000_FWD_CLIENT_DLL-3-ERR [chars][dec]
Explanation An error occured in the forwarder netio client dll (possible the plim driver)
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DM Messages
Error Message%PKT_INFRA-DM-7-INFO [chars]
Explanation An error occurred during initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ENCAP_RM Messages
Error Message%PKT_INFRA-ENCAP_RM-3-FATAL_ERR Fatal error: [chars]: Err equals [dec]
Explanation A fatal error occurred in L2 Encap String RM which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-MSG_SEND_FAILED encap_rm: msg: [dec], retried: [dec] time(s), failed to send, errno: [chars]
Explanation Unable to send a message to the L2 Encap String RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-NONFATAL_ERR Nonfatal error: [chars]: Err equals [dec]
Explanation This is a error message in the L2 Encap String RM to indicate anomalies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temporary situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-3-OOR Failed to insert L2 encapsulation string. Out of resource condition reached.
Explanation A request to insert a L2 encapsulation string into the encapsulation table has failed due to out of resource condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ENCAP_RM-6-INFO_MSG Info: [chars]
Explanation This is an informational message in the L2 Encap String RM.
Recommended Action No action is required.
ERRDIS Messages
Error Message%PKT_INFRA-ERRDIS-3-AUTO_RECOVERY_RETRY_DISABLED Auto-recovery failed on interface [hex] which has since had auto-recovery disabled
Explanation Auto-recovery failed on an interface and will not be retried due to the auto-recovery configuration being deleted.
Recommended Action This is a warning message and no action is required. The interface will remain in error-disable state and will not be auto-recovered.
Error Message%PKT_INFRA-ERRDIS-3-AUTO_RECOVERY_RETRY_FAILED Auto-recovery failed on interface CH[hex]: [chars]
Explanation Auto-recovery failed to restart on the given interface. This interface will remain in Error-Disable state until manually cleared.
Recommended Action Manually clear Error-Disable state on the given interface if desired, else reconfigure an Auto-Recovery period to retry. 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-ERRDIS-3-DEBUG_INIT_FAILED The Verification Daemon Debug failed to initialize: [chars]
Explanation The Verification Daemon Debug failed to initialize. This is a fatal error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ERRDIS-3-EVENT_BLOCK Failed to begin processing events: [chars]
Explanation The Verification Daemon failed to start processing events. This is a fatal error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ERRDIS-3-MISCONFIGURED Invalid configuration has been received by the owner library: [chars]
Explanation The owner library has received configuration that should have been rejected by the verification daemon.
Recommended Action Copy and save this message, and call your technical support representative for assistance.
Error Message%PKT_INFRA-ERRDIS-3-SYSMGR_FAIL Failed to shut down process correctly: [chars]
Explanation The Verification Daemon failed to inform SysManager of it shutting down due to removal of configuration. This is not a fatal error but should be investigated all the same as it may cause the process to restart when no configuration is present.
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-ERRDIS-4-CFG_CLEANUP_FAILED The Verification Daemon failed to cleanup the config module: [chars]
Explanation The Verification Daemon failed to cleanup the config module.
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-ERRDIS-4-CFG_INIT_FAILED Verification Daemon failed to initialize the config module: [chars]
Explanation The Verification Daemon failed to initialize the config module.
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-ERRDIS-4-COULD_NOT_GET_NODEID Failed to get node ID that the owner is running on: [chars]
Explanation Could not get the node ID that the owner is running on.
Recommended Action Copy and save this message, and call your technical support representative for assistance.
Error Message%PKT_INFRA-ERRDIS-4-DEBUG_CLEANUP_FAILED Failed to cleanup debug module: [chars]
Explanation Could not cleanup the debug module.
Recommended Action Copy and save this message, and call your technical support representative for assistance.
Error Message%PKT_INFRA-ERRDIS-4-DEBUG_CLEANUP_FAILED The Verification Daemon failed to cleanup the debug module: [chars]
Explanation The Verification Daemon failed to cleanup the debug module.
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-ERRDIS-4-EVM_CLEANUP_FAILED The Verification Daemon failed to shutdown the event manager: [chars]
Explanation The Verification Daemon failed to shutdown the event manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ERRDIS-4-EVM_INIT_FAILED Verification Daemon failed to initialize the event manager: [chars]
Explanation The Verification Daemon failed to initialize the event manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-ERRDIS-4-PROC_READY_FAILED Verification Daemon failed to inform SysMgr that the process is ready: [chars]
Explanation The Verification Daemon failed to inform sysmgr that the process is ready.
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-ERRDIS-6-ERROR_DISABLE CH[hex]: Error disabling due to reason: [chars]
Explanation The interface is being error disabled. This has occurred due to the reason given in the log.
Recommended Action This is an informational message.
FEA_DLL Messages
Error Message%PKT_INFRA-FEA_DLL-2-PRM_SSH_ERR PRM SSH [chars] error: [chars]
Explanation Feature EA DLL encountered error in completing PRM SSH operation. This can lead to failure of configuration.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-CHKPT_ERR [chars] error. region [chars] direction [chars] ([chars])
Explanation After a process restart, an error was encountered while recovering checkpoint memory/database. The running-configuration and hardware programming may be inconsistent. Problems may be encountered with future configuration changes as well.
Recommended Action Try to manually restart pfilter-ea. If the problem/log persists, a reload of the line card is necessary.
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_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-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-PRM_INIT_ERR PRM INIT [chars] error: [chars]
Explanation Feature EA DLL encountered error in completing PRM init operation. This can lead to malfunction or restart of pfilter ea process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-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-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-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-STATS_ALLOC_ERR STATS [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-STATS_ERR STATS [chars] error: [chars]
Explanation Feature EA DLL encountered error on interacting with PRM Stats APIs.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FEA_DLL-3-TCAM_ERR TCAM [chars] error: [chars]
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_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-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.
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.
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.
Error Message%PKT_INFRA-FEA_DLL-4-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.
FINT_N2N_NETIO Messages
Error Message%PKT_INFRA-FINT_N2N_NETIO-3-SET_MAPPING_FAILED control set mapping for capsulation [chars] protocol [dec] ([chars]) failed: [chars]
Explanation FINT n2n protocol dll could not set certain internal protocol mapping. This should not affect the functionality of any other protocol traffic, but might affect n2n protocol traffic only.
Recommended Action Try restarting the netio process. This could sometimes help fix the problem as the set mapping will be trigged again and we might not hit the failure the 2nd time. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FM Messages
Error Message%PKT_INFRA-FM-2-INFRA_FAIL [chars]: [chars] failed rc equals [dec]
Explanation There was a ENA infra call failure resulting in a failure to provide some infrastructure service.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-BACKEND_EDM_DATALIST Failed to call the backend parser to handle all datalist requests : [chars]
Explanation backend_edm_datalist() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-BACKEND_EDM_GET Failed to call the backend parser to handle all get requests : [chars]
Explanation backend_edm_get() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-DATAPATH_CONTROL_FAILED [chars]: im_caps_datapath_control failed err [[chars]]
Explanation im_caps_datapath_control to LPTS netio caps dll failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-EDM_REGISTER_FAILED FM EDM initialization failed: [chars]
Explanation The FM process failed to initialize its edm manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-ERR_BAG [chars]: [chars] failed
Explanation bag_xxxx() call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-ERR_INVALID_ARGS [chars]: Invalid Params
Explanation Internal error. Function was passed an Invalid Parameter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-ERR_MALLOC Cannot allocate memory in function [chars]()
Explanation Internal error. System is out of memory - malloc failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-ERR_SYSDB [chars]: [chars] failed
[chars]Explanation Sysdb api call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-EVENT_CONN_NOTIFY [chars]: could not set notify handler for connection open/close/error: [chars]
Explanation An internal error was detected when trying to set notify handler for connection opens, closes and errors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-EVENT_CONN_OPEN_ALL [chars]: could not open all event connections attached to an Event Manager: [chars]
Explanation An internal error was detected when trying to open all event connections attached to an Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-3-IM_API_FAILED [chars]: [chars] failed
Explanation Interface Manager client api call failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PKT_INFRA-FM-3-INIT_ERROR Process initialization failed: ([chars]%s)
Explanation The feature manager (feat_mgr) process failed to initialize. This process programs packet classification hardware for features which require an action to be performed based on the packet classification. If the feat_mgr process fails to initialize, the access control list cannot be programmed into the hardware. %s - indicates the reason for the initialization failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process feat_mgr location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart feat_mgr location 0/x/cpu0'. Collect all debug information if the process is continually restarting: 'debug featmgr error location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FM-6-INFO_GENERAL [chars]: [chars]
Explanation The FM encountered a problem of a generic nature or an informational message.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
FMGR Messages
Error Message%PKT_INFRA-FMGR-3-MATCH_TYPE_IN_ACL_NOT_SUPPORTED [chars]
Explanation The following match criteria specified in an ACL are not supported in a QoS policy: Source Port (ipv4), Packet Length. However, rest of the match criteria in the ACE (ignoring the unsupported types) have been programmed in hardware.
Recommended Action If the partial match criteria is not acceptable, the QoS policy should be removed from the interface and modified to use supported match-types. Use 'no service-policy input|output policy_name' in interface configuration mode to remove the QoS policy.
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 input|output policy_name' 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-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 equals [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-3-TCAM_MGR_ERROR [chars] (error equals [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-3-TCAM_MGR_QOSID_ALLOC_ERROR [chars] (error equals [chars])
Explanation Request to TCAM Manager for allocating a QOS Policy ID for a policy attached to an interface failed. The most likely cause of this error is not enough ACL IDs remaining in TCAM manager. QOS policy on this interface will not take effect since TCAM entries are not programmed.
Recommended Action The QoS policy on this interface must be removed to free up other allocated hardware resources. QOS IDs may become available if policies are removed from other interfaces.
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-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.
Error Message%PKT_INFRA-FMGR-7-INIT_ERROR [chars] (error: [chars]). Feature Mgr initialization failed!
Explanation Feature Mgr process failed to initialize correctly. In this case process will restart.
Recommended Action No action needed. Process will restart automatically. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD_BASE_NETIO Messages
Error Message%PKT_INFRA-FWD_BASE_NETIO-3-ERR_MEM_ALLOC Unable to get heap memory during upgrade: [chars]
Explanation Fwd basecaps dll was not able to get heap memory.
Recommended Action This message could be seen under low memory conditions and should recover once memory becomes available. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_BASE_NETIO-5-INCORRECT_SAVE_DATA_LEN Unexpected saved data length during upgrade for DLL. Expected len [unsigned int], got [unsigned int]
Explanation FINT DLL saves data across DLL upgrades. It expects the length of saved data to be same before and after upgrade, else it would cause netio to take default action (to restart) for upgrade to take effect.
Recommended Action This message indicates that netio will take default action to restart as fwd netio dll does not support dll upgrade with different saved data length. No further action is needed.
Error Message%PKT_INFRA-FWD_BASE_NETIO-5-UNSUP_MAJOR_VERSION DLL upgrade with change in major version number is not supported. Expected version [dec], got [dec]
Explanation FINT DLL does not support DLL upgrade across major version changes. This will cause netio to take default action to restart for upgrade to take effect.
Recommended Action This message indicates that netio will take default action to restart as fwd netio dll does not support dll upgrade across major version number changes. No action is needed.
FWD_NETIO_DLL Messages
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-ATTACH_FAILED netio idb attach failed for plim interface: [hex].
Explanation FWD was not able to attach to plim interface .
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-ATTACH_FAILED fwd: netio idb attach failed for plim interface: [hex].
Explanation FWD was not able to attach to plim interface .
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-ATTACH_FAILED fwd: netio idb attach failed for plim interface: [hex].
Explanation FWD was not able to attach to plim interface .
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-ATTACH_FAILED fwd: netio idb attach failed for plim interface: [hex].
Explanation FWD was not able to attach to plim interface .
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BAD_COMMAND_RESULT fwd: received bad command result for buffer request: [hex]
Explanation FWD received a bad command result for BMA free buffer request
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BAD_COMMAND_RESULT fwd: received bad command result for buffer request: [hex]
Explanation FWD received a bad command result for BMA free buffer request
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BMA_OUT_OF_SEQUENCE fwd: BMA buffer request/response sequence number mismatch - received [dec], expected [dec]
Explanation FWD received an out of sequence BMA buffer request response
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-BMA_OUT_OF_SEQUENCE fwd: BMA buffer request/response sequence number mismatch - received [dec], expected [dec]
Explanation FWD received an out of sequence BMA buffer request response
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-EGRESSQ_CREATE_FAILED egressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc equals [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-EGRESSQ_CREATE_FAILED fwd: egressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc equals [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-ERR_MEM_ALLOC fatal memory allocation error for [dec] 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-ERROR fatal error encountered, reason equals [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FABRICQ_CREATE_FAILED fabricq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc equals [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-FABRICQ_CREATE_FAILED fwd: fabricq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc equals [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 equals [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL fwd: fatal error encountered, reason equals [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL fwd: fatal error encountered, reason equals [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason equals [chars], errno equals [dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason equals [chars], errno equals [dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-FATAL_2 fwd: fatal error encountered, reason equals [chars], errno equals [dec]
Explanation fwd encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-GET_CTX_ERR Failed to get idb ctx for port [dec], error - ([dec])
Explanation FWD driver got a packet but couldn't map a port to an idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-GET_CTX_ERR Failed to get idb ctx for port [dec], error - ([dec])
Explanation FWD driver got a packet but couldn't map a port to an idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-HSRMODE [[chars]]: error getting hsrmode , reason equals [chars], errno equals [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-HSRMODE [[chars]]: error getting hsrmode , reason equals [chars], errno equals [dec]
Explanation Error determining if mode is HSR. Caller will error string and errno. Caller can also supply an additional description (like function name) to identify where this error occurred in the code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-IDB_CTX_NULL --
Explanation While processing an ingress packet, the fwd driver failed to find idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-IDB_CTX_NULL --
Explanation While processing an ingress packet, the fwd driver failed to find idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-IDB_CTX_NULL FWD idb context for port [hex] is NULL!
Explanation While processing an ingress packet, the fwd driver failed to find idb context
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INCORRECT_IDB looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INCORRECT_IDB fwd: looking for plim interface: [hex], netio gave us: [hex].
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INFO fwd: service degrading error, reason equals [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INFO fwd: service degrading error, reason equals [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INGRESSQ_CREATE_FAILED fwd: ingressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc equals [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-INGRESSQ_CREATE_FAILED ingressq queue creation failed, q: [dec], rx: [dec], client: [dec], dev: [dec], rc equals [dec]
Explanation FWD was not able to create one of the ingressq queues.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PLIM_PORT fwd: invalid plim port [dec] for plim interface: [hex]
Explanation FWD was supplied with a plim port that exceeds the limit of num ports.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PLIM_PORT fwd: invalid plim port [dec] for plim interface: [hex]
Explanation FWD was supplied with a plim port that exceeds the limit of num ports.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PORT fwd: invalid plim port [dec] for plim interface: [hex]
Explanation FWD was supplied with a plim port or uidb index that exceeds the limit of num ports.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-INVALID_PORT invalid plim port [dec] 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 [dec] bytes
Explanation FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MALLOC_FAILED fwd: fatal memory allocation error for [dec] bytes
Explanation FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MALLOC_FAILED fwd: fatal memory allocation error for [dec] bytes
Explanation FWD encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MUTEXOPFAIL [chars]: Mutex [chars] operation failed on [chars]; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-MUTEXOPFAIL [chars]: Mutex [chars] operation failed on [chars]; reason [chars]
Explanation The packet subsystem failed to get mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NETIO_IDB_UNAVAILABLE netio idb for interface [hex] not found, dropping packet 0x[pointer]
Explanation While processing an ingress packet, the fwd driver failed to find netio idb
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NETIO_IDB_UNAVAILABLE netio idb for interface [hex] not found, dropping packet 0x[pointer]
Explanation While processing an ingress packet, the fwd driver failed to find netio idb
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NO_OUTSTANDING_BMA_REQ fwd: received BMA buffer request response with no outstanding request
Explanation FWD received a BMA interrupt indicating a response to a BMA buffer request but there was no request made
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NO_OUTSTANDING_BMA_REQ fwd: received BMA buffer request response with no outstanding request
Explanation FWD received a BMA interrupt indicating a response to a BMA buffer request but there was no request made
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NOT_YET_IMPLEMENTED fwd: this function [chars] is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NOT_YET_IMPLEMENTED fwd: this function [chars] is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-NOT_YET_IMPLEMENTED fwd: this function [chars] 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 equals [hex], rc equals [hex]
Explanation There was an packet processing error. Possible causes 1) Unable to retrieve fabric dest addr from inside the pkt 2) Error setting/getting input ifh from pkt
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-PAK_PROC_ERR [chars] : [chars], pak equals [hex], rc equals [hex]
Explanation There was an packet processing error. Possible causes 1) Unable to retrieve fabric dest addr from inside the pkt 2) Error setting/getting input ifh from pkt
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_EGRESS_Q_LOOKUP_ERR Failed to find netio egress qad queue. dropping packet 0x[pointer]
Explanation While transmitting a packet down to the fabric, couldn't find the egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_EGRESS_Q_LOOKUP_ERR Failed to find netio egress qad queue. dropping packet 0x[pointer]
Explanation While transmitting a packet down to the fabric, couldn't find the egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_Q_PRODUCE_FAILED Failed to populate netio egress queue, error - [chars]
Explanation FWD driver failed to populate qad netio egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_Q_PRODUCE_FAILED Failed to populate netio egress queue, error - [chars]
Explanation FWD driver failed to populate qad netio egress queue
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_RX_THREAD_ERR Failed to create forwarder qad rx thread, error - [chars]
Explanation FWD driver failed to create qad rx thread
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-QAD_RX_THREAD_ERR Failed to create forwarder qad rx thread, error - [chars]
Explanation FWD driver failed to create qad rx thread
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-SET_INPUT_IF_ERR Failed to set input interface handle [hex] on packet
Explanation While processing an ingress packet, the fwd driver failed to set input interface
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-3-SET_INPUT_IF_ERR Failed to set input interface handle [hex] on packet
Explanation While processing an ingress packet, the fwd driver failed to set input interface
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-4-MISSING_IDB fwd: plim interface: [hex] does not have a netio idb. Could be transient.
Explanation FWD was supplied with a plim interface that does not have an idb yet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PKT_INFRA-FWD_NETIO_DLL-5-UNEXPECTED_PKT Unexpected packet has been received by PRP3 Netio Forward Driver. Type: [dec]
Explanation An unexpected packet type was sent to the PRP3 Fabric. This will not impact functionality or performance. It is being reported for informational purposes only. Type: %d is the type of the packet that the driver rejected.
Recommended Action No intervention is required. A log of these messages together with the gathered data should be kept for future reference by your Cisco technical representative.
Error Message%PKT_INFRA-FWD_NETIO_DLL-6-INFO fwd: [chars]
Explanation The fwd encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD_TP_NETIO Messages
Error Message%PKT_INFRA-FWD_TP_NETIO-3-DEBUG_FAIL Failed to [chars] [chars] with the debugging subsystem: '[chars]'
Explanation Teleport Netio DLL failed initialization or registration with the debugging subsystem. This resulted in the restart of NetIO process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_TP_NETIO-3-DEBUG_GET_EVM_FAIL Failed to get event manager handle to register with the debugging subsystem: '[chars]'
Explanation Teleport Netio DLL failed to get the event manager handle from netio to register with debug system. This resulted in the restart of NetIO process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD_TP_NETIO-5-DEBUG_CLEANUP_FAIL Failed to cleanup registration with debugging subsystem: '[chars]'
Explanation Teleport Netio DLL failed to cleanup the registration with the debugging subsystem. This may result in error when fwd DLL is re-registering with the debug system. If such an error is not noticed, no further action is needed.
Recommended Action If error is observed during reregistration, this error message could be a clue about the reregistration failing. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FWD Messages
Error Message%PKT_INFRA-FWD-3-CAPS_ADD_FAIL Failed to add encapsulation [dec] protocol [dec] to interface CH[hex] ([hex]): [chars]
Explanation Forwarder was not able to add this encapsulation to the forwarder interface. This will effect the traffic of this protocol type going to/from fabric.
Recommended Action Based on the type of error, restart of forwarder or ifmgr process might help in the capsulation addition to the interface. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-CHKPT_SAVE_ERR Error checkpointing data. This will not affect present service but forwarding of CPU bound traffic from this interface may be affected on fwd_driver_partner process restart. Ifh equals [hex], port num equals [dec], error equals [chars]
Explanation FWD encountered an error while checkpointing interface info. While this will not affect present service, it will affect CPU bound fwding if partner process restarts.
Recommended Action If any traffic is affected after partner process restart, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-FATAL fwd: fatal error encountered, reason equals [chars], error equals [chars]
Explanation FWD Driver partner encountered a fatal error and is not able to recover from the error.
Recommended Action The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed the there is no need to take any action. Otherwise check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-3-USAGE fwd: invalid option [chars] passed to fwd server
Explanation Startup option supplied to FWD is not valid.
Recommended Action The process will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed the there is no need to take any action. Otherwise Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-4-NOT_YET_IMPLEMENTED fwd: this function [chars] is not yet implemented
Explanation FWD, a function was not implemented.
Recommended Action No action needs to be taken.
Error Message%PKT_INFRA-FWD-6-IFMGR_REPLY_FAIL Response to IM Notfn [chars] failed for interface CH[hex] ([hex]), caps [dec], proto [dec] with error [chars]
Explanation Forwarder was not able to reply to IFMGR notification. Based on the type of notification the traffic flowing through forwarder interface might or might not be affected.
Recommended Action If any traffic is affected, restarting forwarder process or ifmgr process might help in fixing the issue. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-FWD-7-SPECIFY_PLIM_INTERFACE_RETRIES_COMPLETE All retries now complete. Forwarder and NetIO are in sync.
Explanation All queued retries from forwarder to its NetIO DLL have been completed successfully. The two are now in sync and all slow-path forwarding should be operational.
Recommended Action None - this is an indication of an error situation clearing.
Error Message%PKT_INFRA-FWD-7-SPECIFY_PLIM_INTERFACE_RETRY_QUEUED [unsigned int] failures encountered (first error: [chars]) sending specify plim interface information to Forwarder NetIO DLL. Enqueuing retries
Explanation The forwarder NetIO DLL returned errors when sent a bulk of specify plim interface information, most likely because the interface is not yet in NetIO. A retry has been enqueued.
Recommended Action If this condition persists, it is likely NetIO is out of sync. Restarting NetIO should clear the issue. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
HFR_FWD Messages
Error Message%PKT_INFRA-HFR_FWD-3-FATAL hfr_fwd: fatal error encountered, reason equals [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 equals [chars], errno equals [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,[chars]
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 equals [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 [dec] 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 [chars] 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 [chars] 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.
Error Message%PKT_INFRA-HFR_PFI-3-SET_GLOBALS_FAILED [chars] ([chars])
Explanation Platform PFI was unable to set globals
Recommended Action No action is required.
IFMGR_ENCAP Messages
Error Message%PKT_INFRA-IFMGR_ENCAP-3-BC_ERR Encap change for [chars] [chars] [chars] failed(error [chars])
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync
Recommended Action Repeat failed configuration command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR_ENCAP-3-INIT_ERR Process initialisation failed. [chars] : [chars] ([hex])
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync
Recommended Action Repeat failed configuration command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR_ENCAP-3-SYSDB_ERR Sysdb [chars] for [chars] failed(error [chars])
Explanation The code has hit an error situation for which there is no current handling, therefore the system may now be out of sync
Recommended Action Repeat failed configuration command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IFMGR Messages
Error Message%PKT_INFRA-IFMGR-3-CAPS_DELETE Implicit remove: Intf [hex] ([chars]) caps [unsigned int], proto [unsigned int] (views [hex])
Explanation IM has implicitly removed some caps nodes as part of an interface delete. These caps nodes should have been removed prior to the interface delete.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-GSP_SEND_FAILED [chars] message send failed. Group ID: [hex], Group Name: [chars], Error: [hex] [chars]
Explanation GSP has difficulty in delivering the message to some nodes. There could be a communication problem.
Recommended Action If there is a problem, it might be cleared by restarting ifmgr. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-INIT Process initialisation failed. [chars]: [chars] ([hex])
Explanation There was a software error during process startup.
Recommended Action The process will restart and try to recover. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart, then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If the process does not restart automatically, restart it manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-MISSING_RULES Failed to find [chars] rule for ID [unsigned int]
Explanation IM is unable to create an interface/caps due to static information about the resource type being missing. The system may be in an inconsistent state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-RDQ_CLIENT_SEND_FAILED Failed to send message to IM Server: [chars]
Explanation An IM client has failed to send a message to the server, most likely because the server's queue is full.
Recommended Action Check the ifmgr process. If it is blocked then try restarting it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-RDQ_SERVER_SEND_FAILED Failed to send message to client '[chars]' (cb [hex]): [chars]
Explanation IM has failed to send a message to a client, most likely because the client's queue is full.
Recommended Action Check the process name listed in the message. If it is blocked then try restarting it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-RULES_DUPLICATE_ID Error: Duplicate ID [dec] found in rules file [chars]
Explanation A rule with no static id is found in rules file. Every rule should have exactly one static id assigned to it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-3-RULES_NO_ID Error: ID not found in the rules file [chars]
Explanation A rule with no static id is found in rules file. Every rule should have a static id assigned to it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-CAPS_NOT_ALLOWED [chars] caps is not allowed on interface type [unsigned int] (allowed caps equals [chars]) ([chars])
Explanation The current operation failed because the capsulation is not allowed on this interface.
Recommended Action Configure a valid caps on this interface or choose a different interface on which to configure this capsulation.
Error Message%PKT_INFRA-IFMGR-4-CLIENT_API_ABUSE [chars]: [chars]
Explanation An IM client has used the IM API in an unexpected way, usually implying a bug in the client 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-IFMGR-4-IIR_ID_CONFLICT Member ID conflict while attempting to add interface CH[hex] to CH[hex]. [chars]
Explanation Each member interface must have a unique ID, however during the addition of a new member an existing member with a matching ID was detected. The system will attempt to recover from this situation but if this is not possible then the system may end up in an inconsistent state.
Recommended Action Check the status of the main interface and any members. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-LWM_UNEXPECTED_ERROR Unexpected error received in reply: code: [hex] (msgno equals [unsigned int], sparts equals [unsigned int] rparts equals [unsigned int])
Explanation This is a temporary ios_msg to identify when an unexpected error is returned when communicating with the IM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-MTU_RANGE MTU out of range for interface CH[hex], protocol [unsigned int], encapsulation [unsigned int]. Minimum MTU [unsigned int], maximum MTU [unsigned int], actual MTU [unsigned int].
Explanation The MTU on an interface or encapsulation is outside its operational range. This may result in traffic loss on the interface.
Recommended Action Check the MTU configuration on the interface, it may be necessary to raise or lower any configured values to achieve MTU values within the supported range. If this does not help Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-4-NB_DPC_DOWNLOAD_ERROR An error was encountered processing a non-blocking DPC for feature [chars] on interface CH[hex]. The system may be in an inconsistent state. Error: [chars]
Explanation An error has been encountered during processing of a DPC that cannot be handled by the client due to the client having already been unblocked. This may have left the system in an inconsistent state, as this specified feature may not be configured correctly on the given interface.
Recommended Action Try shutting down / no-shutting the interface in question. If this doesn't work, try restarting the MA process for the feature in question. If this does not help Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-6-GSP_SEND_RETRY [chars] message send error. Group ID: [hex], Group Name: [chars], Error: [hex] [chars]
Explanation GSP has difficulty in delivering a message to some nodes. There could be a communication problem. This warning is for information only since the message will be resent.
Recommended Action No action is required.
Error Message%PKT_INFRA-IFMGR-6-IMPLICIT_DOWNLOAD_FAIL After [unsigned int] minutes of retries, implicit download of [unsigned int] interfaces is still failing (first intf CH[hex], error: [chars])
Explanation An error was repeatedly encountered while attempting to replicate the dataplane of an interface to a node to which it implicitly required replication (e.g. due to wildcard replication being used, and a new node coming up later). This may cause forwarding on this interface (via this node) to be broken.
Recommended Action The download will continue to be retried, so if the issue is transient and just taking a long time to clear then it will clear eventually and this message will stop appearing. If this message continues to be seen for a long time Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-6-LWM_UNEXPECTED_PULSE Ignoring unexpected pulse with code [unsigned int], value [hex]
Explanation This error message indicates that a pulse has been delivered to the event manager in the IM client library which was intended for someone else. This is almost certainly harmless in this case since IM has detected and ignored the event.
Recommended Action No action is required.
Error Message%PKT_INFRA-IFMGR-6-MUTEX_MONITOR_EVENT_REGISTER Failure registering for mutex revival
Explanation IM was unable to perform a system operation that it expects to succeed. IM will exit and restart in an effort to help clear the condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-6-OUT_OF_MEMORY Ifmgr was unable to allocate memory for an operation. Ifmgr will exit and restart to attempt to clear this condition
Explanation IM was unable to allocate the memory it needed - indicating the system is in a very low-memory condition, which should be recovered by wdsysmon automatically. IM will exit and restart in an effort to help clear the low memory condition
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IFMGR-6-PREMATURE_OP [chars] operation from callback [hex] received for interface CH[hex] that has not been created.
Explanation A client performed an operation on an interface that is in the progress of being created. In general, the interface handle for the interface being created is not published until the interface create has completed. The most likely reason for this log is that the client is using a stale interface handle (for example, from before a linecard OIR). An IM_ERROR_NOTFOUND error is returned to the 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-IFMGR-6-SYSTEM_ERR Ifmgr encountered an unexpected error calling '[chars]': [chars] ([dec]). [chars]
Explanation IM was unable to perform a system operation that it expects to succeed. IM may exit and restart in an effort to help clear the condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IMAEDM Messages
Error Message%PKT_INFRA-IMAEDM-3-EVENT_CONN_CREATE_FAILED [chars]: could not create connection structure for the connection to [chars]: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-EVENT_CONN_NOTIFY_FAILED [chars]: could not set notify handler for connection opens and errors to [chars] : [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-EVENT_CONN_OPEN_ALL_FAILED [chars]: opening all connections of Event Manager failed: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-INTERNAL_ERR [chars]: Internal error: [chars]: [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-3-SYSMGR_PROC_READY_FAILED [chars]: sysmgr_proc_ready failed: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-3-TIMER_CREATE_FAILED [chars]: Timer creation failed: [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-7-BAG_REG_FAILED [chars]: bag register error is detected; [chars].
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-IMAEDM-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the im/imaedm/[chars] event failed: [chars]
Explanation An error was returned when the IM Attribute EDM server called the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-7-DEBUG_REGISTER [chars]: Debug registration for IM Attribute EDM server failed: [chars]
Explanation An error was returned when the IM Attribute EDM server called the debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-7-EDM_INIT_FAILED [chars]: Failed to open EDM connections (retries [unsigned int][chars]). Turn on debug imaedm errors to diagnose failure.
Explanation The opening of EDM connections has failed repeatedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMAEDM-7-EVM_CREATE_FAILED [chars]: event_manager_create failed; [chars]
Explanation The event_manager_create function reported an error trying to initialize the event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IMATTR Messages
Error Message%PKT_INFRA-IMATTR-3-DUPLICATE Received duplicate successful replies for interface [hex], attribute type [chars]
Explanation The attribute client has received duplicate successful responses for this attribute on this interface. This would suggest that multiple attribute owners have been configured for this (interface, attribute) pair.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-IMATTR-3-NOTIFY_FAILED A bulked notification message failed to be sent: [chars]
Explanation The attribute owner library has failed to send a bulk notification message to the attribute clients. However, the attribute owner that produced these notifications is not aware that they failed to be sent. This could result in the attribute clients being out of sync with this owner.
Recommended Action If the system appears to be in a low-memory condition (check the output of 'show mem summary') then this is most likely the cause of the problem. Please try to fix the low-memory condition. If this is not the case, then contact technical support.
Error Message%PKT_INFRA-IMATTR-3-SET_REPLY_FAILED At least 1 item in a bulk set/clear operation succeeded, but the client cannot be informed due to an error: [chars]
Explanation The attribute owner library has failed to reply to the client to inform it that a set or clear operation has succeeded. This could result in the client being out of sync with the owner.
Recommended Action If the system appears to be in a low-memory condition (check the output of 'show mem summary') then this is most likely the cause of the problem. Please try to fix the low-memory condition. If this is not the case, then contact technical support.
Error Message%PKT_INFRA-IMATTR-3-UNKNOWN_PULSE Received an asynchronous message from an unknown source which has been dropped (pulse code [hex], request 0x[pointer])
Explanation The attribute client or owner has received a pulse which is not expected, and cannot be handled. This message has been dropped. If no other problems are seen then the error can be considered harmless.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
INTERFACE_CONFIG Messages
Error Message%PKT_INFRA-INTERFACE_CONFIG-3-SET_DEFAULT_ERR Couldn't reset MAC address value for interface [chars] (error: [chars])
Explanation An error occurred while resetting the MAC address for the specified interface to the default. The interface may still have the wrong MAC address, and different parts of the system may be using different values for the interface's MAC address.
Recommended Action If the message appeared as a result of applying configuration, try removing and re-applying the configuration concerned. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-3-SET_ERR Could not set MAC address for interface [chars] (error: [chars])
Explanation An error occurred while setting the MAC address for the specified interface to the configured value. The interface may still have the wrong MAC address, and different parts of the system may be using different values for the interface's MAC address.
Recommended Action If the message appeared as a result of applying configuration, try removing and re-applying the configuration concerned. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-4-EVENT_BLOCK_ERROR An error occurred while waiting for an event (error: [chars])
Explanation The Interface Configuration process encountered an error while waiting for an event. The process will automatically restart and retry.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-INTERFACE_CONFIG-4-INIT_FAILURE Initialisation failure during [chars]: error [chars]
Explanation The Interface Configuration process encountered an error while initialising. It will not be possible to configure interface MAC addresses until the process starts successfully. The process will automatically restart and retry.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
INTF_MGBL Messages
Error Message%PKT_INFRA-INTF_MGBL-7-INIT_FAILED Initialisation Failed. Task: '[chars]' Error: '[chars]'
Explanation The process failed to initialise and will exit.
Recommended Action The process will be restarted automatically. If the error happens repeatedly then contact support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LINEPROTO Messages
Error Message%PKT_INFRA-LINEPROTO-5-UPDOWN Line protocol on Interface [chars], changed state to [chars]
Explanation The data link level line protocol changed state.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface and line protocol.
LINK Messages
Error Message%PKT_INFRA-LINK-3-UPDOWN Interface [chars], changed state to [chars]
Explanation The interface hardware went either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
Error Message%PKT_INFRA-LINK-4-BERTADMINDOWN [chars] is administratively down
Explanation Unable to start BERT because controller in admin down state
Recommended Action None.
Error Message%PKT_INFRA-LINK-4-BERTNOTRUNNING [chars] is not running BERT
Explanation Trying to stop BERT when not running
Recommended Action None.
Error Message%PKT_INFRA-LINK-4-BERTRESTART [chars] is already running BERT
Explanation Restarting a running BERT is not allowed
Recommended Action None.
Error Message%PKT_INFRA-LINK-4-BERTSTART [chars] could not start BERT
Explanation BERT could not be started
Recommended Action None.
Error Message%PKT_INFRA-LINK-4-BERTSTATUS [chars] [chars]
Explanation The bert status of the link
Recommended Action None.
Error Message%PKT_INFRA-LINK-5-CHANGED Interface [chars], changed state to [chars]
Explanation The interface has changed state.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
LPTS_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.
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.
netio_debug Messages
Error Message%PKT_INFRA-netio_debug-3-INIT_FAILED NetIO debugging partner initialization failed: [chars] (Err equals [chars])
Explanation The NetIO debugging partner process initialization failed. This could happen due to errors in various server processes. The error code and its text in the message will reveal the source of the error.
Recommended Action If the process restarts and this message is not repeating, no actions are needed. If this message recurs, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-netio_debug-4-ASYNC_HANDLER Couldn't install the default handler for async messages, err: [chars]
Explanation The NetIO debugging partner process couldn't install the default event handler for async messages.
Recommended Action No action is required.
NETIO Messages
Error Message%PKT_INFRA-NETIO-3-ERR_ARP [chars], [chars], [dec]
Explanation ARP netio error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_AUTOLOAD Failed to load DLL for caps [chars] ([unsigned int]), error: [chars]
Explanation An error occurred while auto-loading a caps DLL. If this message is repeatedly seen then the software packet path on this node may be broken.
Recommended Action The process will reconnect to Interface Manager and try again. If this message is not seen again then the issue has been recovered and no further action is required. If this message continues to be seen Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_DELETE_FINT Error: NetIO received a request to delete the Forwarder Interface
Explanation Interface Manager has requested NetIO to delete the Forwarder Interface. This should not occur - the system assumes the Forwarder Interface is never deleted.
Recommended Action If this message is seen then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.. When this condition is hit, NetIO will assert and restart in an attempt to recover.
Error Message%PKT_INFRA-NETIO-3-ERR_INIT [chars] : Failed to initialize ipv4 proto for [chars] with error ([chars])
Explanation netio initialization error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_MEDIA_REGISTER [chars] : Failed for ipv4 proto to [chars] ([chars])
Explanation netio media register or callback error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_PACKET_INPUT Failed to input the packet for [chars] ([chars])
Explanation Failed to input the packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-ERR_RESYNC An error occurred during a synchronization with Interface Manager: Failed to [chars], error: [chars]
Explanation An error occurred while processing a resync from Interface Manager. If this message is repeatedly seen then the software packet path on this node may be broken.
Recommended Action The process will reconnect to Interface Manager and try to recover. If this message is not seen again then the issue has been recovered and no further action is required. If this message continues to be seen Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-LTRACE_INIT ltrace_init failed for '[chars]': [chars]
Explanation Netio ltrace facility failed to initlize one of the trace buffers. The Netio trace information will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-PAK_NETIO_MUTEX_LOCK [chars] : Failed to acquire pak netio mutex lock ([chars])
Explanation ARP netio error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-SCRIPT_ERR_MEM_ALLOC Cannot allocate memory in [chars]
Explanation Internal error. System is out of memory - malloc failed.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-3-SCRIPT_FAIL netio script failed: [chars]
Explanation An error occurred during netio script processing. Please check the error message for more details.
Recommended Action Check if the script file exists and is in correct format. If the message recurs, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-3-SELFMANAGE_FAILURE [chars] failed during self managed upgrade of DLL/SMU, Error: [chars]
Explanation NetIO was attempting a hitless upgrade of a DLL that was part of a SMU/PIE. A step during this operation encountered this error. Netio may or may not be able to perform the DLL upgrade successfully when this error is encountered.
Recommended Action If the DLL upgrade is successful, no further action is needed. Otherwise it is recommended that netio is restarted, to recover from an inconsistent DLL upgrade state in NetIO. Restart of netio should lead to the new DLL take effect and bring back things to normal.
Error Message%PKT_INFRA-NETIO-4-BAD_PACKET NetIO received a packet with no data particle in it, packet: 0x[pointer], packet PID: [dec]
Explanation NetIO received a bad packet from the driver (or from an application) that had no particle data in it. NetIO drops these packets. If too many such packets belonging to a routing protocol are received and dropped, we have a potential possibility of an adjancency flap.
Recommended Action If no side effects are observed nothing needs to be done and NetIO would just drop these packets and continue with its normal operation. If this message is seen many number of times, it indicates some sort of issue in the driver sending packets to NetIO and the driver needs to be analysed further, in that case Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-NETIO-4-SCRIPT_WARNING script [chars]([dec]): [chars]
Explanation An internal syntax error was detected in the script file. The current line was skipped and the execution of the script continued.
Recommended Action Check the script for the skipped or ignored line. Make syntax changes as needed.
Error Message%PKT_INFRA-NETIO-5-SELFMANAGE_UPGRADE_NOTICE NetIO DLL [chars] is being upgraded. NetIO will be restarted
Explanation NetIO gets restarted whenever we upgrade a DLL that does not support NetIO DLL upgrade. This should not cause any problems to the router and NetIO should come back up fine after restart.
Recommended Action This should not cause any problems in the router, NetIO should restart and come back up fine & resume its normal functionality. If it causes any routing issues such as adjacency going down or some other problem, one potential cause is that NetIO took longer to restart. NetIO restart time is a function of number of interfaces configured in NetIO on this node. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-6-ERR_THREAD_MUTEX packet mutex [chars] failed : [chars]
Explanation NetIO was unable lock/unlock the packet mutex. This could lead to certain cases when the same packet is used
Recommended Action --
Error Message%PKT_INFRA-NETIO-6-SELFMANAGE_INFO NetIO is upgrading([chars]) the dll [chars]
Explanation Netio is upgrading this dll. This is here only for informational purpose only. No further action is recommended/needed.
Recommended Action 'No action is required.'
Error Message%PKT_INFRA-NETIO-7-ERR_CREATE_IDB create idb error: interface ifhandle [hex] already in datastore with name [chars], new name [chars]
Explanation Netio already has this IDB in its datastore. It is getting a request for create for the same interface handle but with a different name. This could possibly cause issues with this interface in NetIO.
Recommended Action After the information is gathered, restart of netio/improxy should possibly bring netio in sync with ifmgr leading to the delete of this idb from Netio. If the create operation is retried it might succeed. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-7-ERR_DELETE_IDB_SUBBLOCK delete idb:interface (ifhandle equals [hex], name [chars]) having subblocks (name [chars], refcount [dec]) cannot be deleted. Error: [chars]
Explanation NetIO cannot delete an interface which still has subblocks associated with it. This error could potentially cause issues with recreate of any interface, if the same interface handle is reused.
Recommended Action After the information is gathered, restart of netio/improxy should possibly will bring them in sync with ifmgr & delete the protocol chains and hence the subblocks. If restart doesnot help. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-7-ERR_DELETE_IDB_SUBINTF delete idb: interface (ifhandle equals [hex], name [chars]) having subinterfaces (demux index: [dec], ifh [hex], name [chars]) cannot be deleted. Error: [chars]
Explanation NetIO cannot delete a interface which still have subinterfaces under it. This could potentially cause issues with recreate of any interface, if the same interface handle is reused.
Recommended Action After the information is gathered, restart of netio/improxy should possibly bring them in sync with ifmgr & delete the main and subinterfaces. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-7-ERR_DELETE_IDB_SUBINTF_ASSOC delete idb: interface (ifhandle equals [hex], name [chars]) has [unsigned int] subinterfaces associated with it and cannot be deleted. Error: [chars]
Explanation NetIO cannot delete a interface which still have subinterfaces under it. This could potentially cause issues with recreate of any interface, if the same interface handle is reused.
Recommended Action After the information is gathered, restart of netio should possibly bring netio in sync with ifmgr & delete the main and subinterfaces. 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PKT_INFRA-NETIO-7-ERROR_INIT [chars] Failed, Error: [chars]
Explanation NetIO process has problem initializing its database and attempts to restart in an attempt to recover from the error.
Recommended Action The process attempts to restart on detecting this failure, in an effort to recover from the failure. If after restart things recover, then nothing more needs to be done. If the error is seen when the system is low on system resources, once the system resource like memory, cpu go back to normal state, the process should succeed in coming back up. If the process fails to recover and repeatedly exits then the ios message will have the details of what part of initialization failed and the reason for it, for further action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
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.
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-3-PTCL_LIST_NOT_NULL --
Explanation --
Recommended Action Please collect a core dump of the packet client that emitted the message, or whose pid matches that in the error message with 'exception pakmem on' configured.
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.
Error Message%PKT_INFRA-PAK-7-GETNODENAMEFAIL Failed to get node name
Explanation The Packet manager library was unable to retrieve the nodename for the node/linecard.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%PKT_INFRA-PAK-7-SPP_TRYMAP __spp_trymap: [chars]
Explanation The vector packet path API bind routine has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-REGION_TOO_BIG Platform attempted to define a packet region that was too large: Start:0x[pointer] Size:[dec]
Explanation The platform driver attempted to define a packet memory region larger than is currently supported. This will be automatically reduced to a supported size.
Recommended Action Copy the error message exactly as it appears on the 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 equals [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-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 equals [chars],size equals [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-2-DEPLETION_CATASTROPHIC Depletion level [dec] percent for resource [chars]
Explanation The depletion level of the specified packet resource is catastrophic. At this level of depletion, all services and protocols on the specified node are not able to allocate packets and node may not be able to function properly unless the depletion levels improve.
Recommended Action Customer should monitor depletion levels using 'show packet-memory' commands. If packet memory remains depleted for significant period of time then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKWATCH-3-DEPLETION_CRITICAL Depletion level [dec] percent for resource [chars]
Explanation The depletion level of the specified packet resource is critical. At this level of depletion, routing protocols on the impacted node are not able to allocate packets and the software packet path will be impacted. Critical services on the node may not be able to allocate packets and thus could be impacted.
Recommended Action Customer should monitor depletion levels using 'show packet-memory' commands. If packet memory remains depleted for significant period of time then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKWATCH-4-DEPLETION_WARNING Depletion level [dec] percent for resource [chars]
Explanation The depletion level of the specified packet resource has reached warning level. If the depletion level does not improve then routing protocols on the impacted node will not be able to allocate packets and the software packet path will be impacted. At warning depletion level, critical services on the node should still be able to allocate packets and thus shouldn't be impacted.
Recommended Action Customer should monitor depletion levels using 'show packet-memory' commands. If packet memory remains depleted for significant period of time then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKWATCH-6-DEPLETION_INFO Depletion level [dec] percent for resource [chars]
Explanation Information about the current depletion level of the specified resource. At this level of depletion functionality should not be impacted.
Recommended Action Customer should monitor depletion levels using 'show packet-memory' commands. If packet memory reaches higher depletion levels for significant period of time then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKWATCH-6-DOUBLE_FREE Particle [pointer] with [dec] refcount being freed
Explanation An attempt has been made to free a packet buffer that is already freed. This usually indicates the process using the particle has used it after it has been returned.
Recommended Action Please collect a core dump of the process from which the message is output, using the 'dumpcore running' command to catch the current packet memory state ('exception pakmem on' must also be configured). Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-PAKWATCH-6-HEADER_CORRUPTION --
Explanation The particle/header free list and particle/header free count are out of sync; probable corruption of packet memory.
Recommended Action Please collect a core dump of the process from which the message is output, using the 'dumpcore running' command to catch the current packet memory state ('exception pakmem on' must also be configured). Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-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-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.'
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_PFI Messages
Error Message%PKT_INFRA-PLATFORM_PFI-4-IFHANDLE_DECODE Could not map handle [hex] to slot
Explanation The interface handle cannot be mapped to a slot on the card.
Recommended Action Debug message only. *DEBUG*
Error Message%PKT_INFRA-PLATFORM_PFI-4-INIT Failed to initialise [chars]
Explanation An error occured when a module was going to be initialised. This may cause the process to terminate.
Recommended Action Restarting the process might help.
PQMON Messages
Error Message%PKT_INFRA-PQMON-6-QUEUE_DROP Taildrop on [chars] queue [dec] owned by [chars] (jid equals [dec])
Explanation A producer process was unable to produce into a software queue because the queue was full. This typically means that the owning process is blocked or CPU is under heavy stress.
Recommended Action These messages are for the purpose of proactively alerting the operator to any potential issues that may arise from tail drops on the software queues. If no impact (such as routing protocol flaps or traffic loss) is seen, these messages can be ignored. For debugging, please collect the following information. 'show logging' 'show pqmon trace' 'show packet-memory trace mutex'
Error Message%PKT_INFRA-PQMON-6-QUEUE_HIGH_THRESH Build-up detected on [chars] queue [dec] owned by [chars] (jid equals [dec])
Explanation The amount of work queued into a software queue has crossed the high threshold (three-fourths of the queue size). This typically means that the owning process is blocked or CPU is under heavy stress and, hence, the owner process is unable to process the queued work items.
Recommended Action These messages are for the purpose of proactively alerting the operator to any potential issues that may arise from queue build-up on the software queues. If no impact (such as routing protocol flaps or traffic loss) is seen, these messages can be ignored. For debugging, please collect the following information. 'show logging' 'show pqmon trace' 'show packet-memory trace mutex'
Error Message%PKT_INFRA-PQMON-6-QUEUE_LOW_THRESH Build-up cleared on [chars] queue [dec] owned by [chars] (jid equals [dec])
Explanation Informational message to indicate that a queue build-up has cleared up. This message coupled with the corresponding queue build-up message can give an indication of how long the queue build-up condition lasted.
Recommended Action None.
spp Messages
Error Message%PKT_INFRA-spp-0-EMERG [chars]
Explanation An emergency error has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-spp-1-ALERT [chars]
Explanation An alert error has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-spp-2-CRIT [chars]
Explanation A critical error has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-spp-3-ERR [chars]
Explanation An error has been detected.
Recommended Action If the process restarts and this message is not repeating, no actions are needed. If this message recurs, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-spp-4-WARNING [chars]
Explanation A warning codition has been detected.
Recommended Action If this message is not repeating, no actions are needed. If this message recurs, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-spp-5-NOTICE [chars]
Explanation A condition worthy of note has been detected.
Recommended Action No action is required.
Error Message%PKT_INFRA-spp-6-INFO [chars]
Explanation An informational message.
Recommended Action No action is required.
Error Message%PKT_INFRA-spp-6-INFO_TRACEBACK [chars]
Explanation An informational message.
Recommended Action No action is required.
Error Message%PKT_INFRA-spp-7-DEBUG [chars]
Explanation A debug message.
Recommended Action No action is required.
SVII_ADJ_LIB Messages
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-ADJ_DATA_CORRUPT The SVI Adjacency Manager was provided with corrupt adjacency data for [chars] SSC belonging to service [chars] on location [chars]
Explanation Either the active or standby Service State Controller for the location given in the message provided the Adjacency Manager with corrupt data. This most likely indicates a bug in the Service State Controller logic. No adjacencies will be installed for the named service, so no traffic will be forwarded to or from it.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-FOLLOW_STANDBY_MISMATCH The SVI Adjacency Manager was provided with conflicting settings for installing adjacencies for interface [hex]
Explanation Conflicting 'follow standby' instructions were supplied to the Adjacency Manager for an interface. 'Follow standby' is specified for an interface by a Service State Controller if it believes that traffic should be directed towards the standby, rather than active, service instance. This message indicates that the active and standby Service State Controllers gave conflicting information about where traffic to be directed to. This indicates an inconsistency between the system state as viewed by the Service State Controllers that are responsible for the service to which the interface belongs. Restarting those processes may help, after allowing any other problems that could lead to inconsistencies being resolved. No adjacencies will be installed for the interface, and all traffic to it will be dropped.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars]
Explanation The SVI Adjacency Manager Library's initialization has failed. The process will exit and automatically restart.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-3-SERVICE_FAILED An error occurred while setting up adjacencies for service '[chars]': [chars]
Explanation The SVII Adjacency Manager encountered an error while preparing to set up adjacencies for the specified service. It is likely that packets will not be forwarded to interfaces for that service. This may be caused by a lack of resources or other system problems. Restarting the 'svi_adj_mgr' process on the affected node (after any other problems have been cleared up) will restore adjacencies for the affected service.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-INTF_DB_INCONSISTENT An inconsistency has been found in the interface database (interface handle [hex])
Explanation An inconsistency has been found in the adjacency manager interface database. The adjacency manager will automatically recover from this; nevertheless it may indicate a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-REFRESH_FAILED An error occurred while requesting adjacency refresh for service '[chars]': [chars]
Explanation The SVII Adjacency Manager encountered an error while resynchronising its adjacencies. The adjacencies for the specified service may not be correctly set up on the specified card, meaning that traffic for that service arriving at that card may not be forwarded correctly.
Recommended Action Restarting the 'svi_adj_mgr' process on the affected node (after any other problems - such as lack of memory - have been cleared up) will restore adjacencies for the affected service. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-RESTART_FAILED An error occurred while trying to restart cleanly: [chars]
Explanation The SVII Adjacency Manager encountered an error while preparing to restart itself. It will restart itself anyway, but there may be other errors.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-SDIR_INVALID The Service Director library passed invalid parameters to the SVII Adjacency Manager process.
Explanation The Service Director process/library sent an invalid message to the SVII Adjacency Manager. This indicates a problem with the Service Director. It is likely that packets will not be correctly forwarded to some Service Virtual Interfaces.
Recommended Action It may help to restart the SVII Adjacency Manager and/or the Service Director processes. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_LIB-4-SRV_CLEANUP_FAILED The SVI Adjacency Manager 'publish' library encountered an error when trying to clean up after a service unregistered. Error [chars]
Explanation A Service owner tried to revoke a request for adjacencies to be managed by the SVI Adjacency Manager. It is likely that the originally published request has not been cleaned up correctly. This should not have any adverse effects, other than the use of some additional resouces, but probably indicates some kind of programming error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SVII_ADJ_MGR Messages
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-ADJ_FAILED An error occurred while trying to program an adjacency: [chars] (interface handle equals [hex])
Explanation The SVII Adjacency Manager encountered an error while programming an adjacency. Packets may not be forwarded to the affected service interface. The name of the interface can be retrieved with 'show im chains ifhandle 0xabc', where '0xabc' is the interface handle shown in the message.
Recommended Action This error should only arise due to resource constraints (eg memory). Determine which resources are short, and make more available; then restart the 'svi_adj_mgr' process on the affected node.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-ECM_ERROR_FAILED An error occurred while trying to recover from a previous failure: [chars]
Explanation The SVII Adjacency Manager encountered an error while calling AIB. Normally, it would recover from this error. However, a secondary failure has occurred while invoking the recovery mechanism. After this error, packets may not be forwarded correctly for some service virtual interfaces.
Recommended Action The system can be recovered by restarting the 'svi_adj_mgr' process on the affected node. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars]
Explanation The SVI Adjacency Manager's initialization has failed. The process will exit and automatically restart.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-LOOP_FAILED Event Loop failed, error: [chars]
Explanation The SVII Adjacency Manager encountered an error while waiting for an event. This should not ordinarily happen, but may indicate a temporary glitch that will automatically recover. If it occurs very frequently it may be necessary to restart the SVII Adjacency Manager process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-RECEIVE_MESSAGE An error occurred whilst processing a '[chars]' message from a client, during operation [chars]: [chars]
Explanation The process encountered an error while trying to handle a message from a Service on a line card. If this happens frequently, then restarting the process that caused the error may fix the problem. It may indicate that the card is low on memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-3-SYSMGR Failure communicating readiness to System Manager. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-4-RESTART A failure occured while re-syncing state with AIB after a restart: [chars]
Explanation After a restart, the adjacency manager attempts to re-sync its state with AIB. A failure occurred during this process. This could result in adjacencies being erroneously deleted in AIB, and hence forwarding could be interrupted.
Recommended Action Wait five minutes, then restart the adjacency manager again by entering the command: 'process restart svii_adj_mgr location node'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-SVII_ADJ_MGR-6-CERRNO_FAILED Error registration failed ([chars]) - some messages may not be displayed correctly
Explanation The SVI Adjacency Manager encountered an error while registering its error messages. Some error messages may be displayed numerically rather than with full messages. No other problems will be caused by this failure.
Recommended Action No action need be taken.
TCAM_MGR_LIB Messages
Error Message%PKT_INFRA-TCAM_MGR_LIB-3-INTERNAL_ERR Internal error: [chars]
Explanation An internal error occurred in TCAM Manager which involves exiting the process. After the TCAM Manager process restarts, the error should have been cleared. *DDTS*
Recommended Action Collect the configuration, syslog and coredump file. Attach them to the ddts. After the process restarts automatically, the error should have been cleared and no user action is needed.
Error Message%PKT_INFRA-TCAM_MGR_LIB-3-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.
Error Message%PKT_INFRA-TCAM_MGR_LIB-6-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.
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.
Error Message%PKT_INFRA-TCAM_MGR-6-V6_ANCHOR_PREFIX IPv6 compression anchor prefixes are changed. A linecard reload is needed to make this change effective Existing anchor prefix length [dec] [dec] [dec] [dec] [dec] [dec] Pending anchor prefix length [dec] [dec] [dec] [dec] [dec] [dec]
Explanation The IPv6 compression anchor prefixes are changed. The linecard needs to be reloaed to make the changes effective. This is not an error message or condition.
Recommended Action The IPv6 compression anchor prefixes are changed. The linecard needs to be reloaed to make the changes effective. This is not an error message or condition.
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-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-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-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-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-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-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-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-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-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-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-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-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.'
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.'
Error Message%PKT_INFRA-tunnel_ea-3-STATS_INIT_FAILED stats collecton init failed [chars]
Explanation Internal error
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
TUNNEL Messages
Error Message%PKT_INFRA-TUNNEL-1-RESOURCES Could not program hardware resources for interface [chars]
Explanation Some hardware resource could not be programmed. The reason details which resource failed
Recommended Action Ensure that enough resources are available. The user may have to unconfigure some resources, and then will have to reapply the xconnect configuration.
Error Message%PKT_INFRA-TUNNEL-3-API_ERR The [chars] API function to [chars] returned the following error: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-API_ERROR [chars]: [chars] - error ([hex]): [chars]
Explanation The specified API returned the specified error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-API_ERROR_2 [chars]: [chars] - error: [chars]
Explanation The specified API returned the specified error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-BAD_CHAIN Invalid chain type ([dec])
Explanation An invalid chain type was received by the chain builder. This is an internal error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-BAD_CHECKSUM Bad checksum - computed equals [hex], received equals [hex]
Explanation Mismatch in received/computed checksum was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-BAD_KEY Incorrect key - received: [dec], expected: [dec]
Explanation A packet was received with a bad key.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-CONFIG_SCAN_FAILED [chars]: item [chars]: [chars]
Explanation An unexpected error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-CURRENT_MAXIMUM_HIGH Current maximum [dec] exceeds absolute maximum [dec]
Explanation New current maximum is larger than the absolute max.
Recommended Action Use a current maximum value which is lower than the abosulte max value.
Error Message%PKT_INFRA-TUNNEL-3-CURRENT_MAXIMUM_LOW New current max [dec] is lower than the number of tunnels currently configured [dec].
Explanation New current max is lower than the current tunnel count.
Recommended Action Use a current maximum value which is lower than the current tunnel count.
Error Message%PKT_INFRA-TUNNEL-3-CURRENT_MAXIMUM_REACHED tunnel-[chars]: Current Maximum # of configured tunnels reached [dec]
Explanation Tunnel Count has reached the current maximum limit.
Recommended Action Use the 'maximum tunnel-te N' config CLI to increase the current maximum value.
Error Message%PKT_INFRA-TUNNEL-3-GENERIC [chars]
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-IM_ERR The interface manager API function to [chars] returned the following error: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-IMP_ERROR Unknown condition code received from imp: ([dec])
Explanation The specified condition code was received from imp.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-INIT_FAIL Tunnel process initialization failed while [chars] with error: [chars]
Explanation The tunnel process responsible for the creation of tunnel interfaces failed during initialization. The process will exit and as a result, no tunnel interfaces can be configured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-INVALID_IDB datapath_control information for unknown IDB
Explanation A datapath_control message was received for an unknown interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-LOOPING Encapsulation looping detected: inner: [chars], outer: [chars]
Explanation An encapsulation loop was detected.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-NEGATIVE_CURRENT_COUNT tunnel-[chars]: current tunnel count became negative, restarting
Explanation Tunnel count has been decremented till it became negative. process tunnel_infra will restart to recover from the situation.
Recommended Action Ideally this should never happen and points to a serious bug in pfi/tunnel/infra File a tracking DDTS if it happens.
Error Message%PKT_INFRA-TUNNEL-3-NO_IDB IDB not available in context
Explanation Could not find the tunnel IDB in the context structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-NO_INTERFACE Interface [chars] does not exist to delete
Explanation A request to delete a non-existent interface has been received. This is relatively a harmless error, unless it is too frequent, in which case the reason for the error must be investigated, starting with the name of the interface printed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-NULL_DPC --
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-TUNNEL-3-NULL_NEXT --
Explanation The decapsulated packet could not be forwarded. This is an internal error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-ROUTING GRE tunnel packet received with source routing
Explanation A GRE tunnel packet with the source routing option was received.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-SEQUENCE GRE tunnel packet received with sequence option
Explanation A GRE packet was received with the sequence option.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-SOCKET Socket op [chars] failed: [chars]
Explanation The specified socket operation failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_GRE_TUNNEL Packet received for unknown tunnel or bad key. Source: [chars], Destination: [chars], Key: [dec]
Explanation A GRE tunnel packet was received for a tunnel that is not configured in this router or there was a key mis-match.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_HANDLE IDB for interface [hex] not found
Explanation The EA received a datapath control indication for an unknown interface handle
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_IPIP_TUNNEL Packet received for unknown tunnel. Source: [chars], Destination: [chars]
Explanation An IPinIP tunnel packet was received for a tunnel that is not configured in this router.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_MSG Received unexpected message opcode [dec] in Interface Manager handler
Explanation An unexpected message was received by this process. This is relatively a harmless error and should not have any immediate impact on the operation of tunnel interfaces. It must still be reported and looked into.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNKNOWN_PROTOCOL Unknown protocol [dec] received by the gre socket handler
Explanation A packet with an unknown protocol type was passed to the GRE socket handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNSUPPORTED_CODE_RCVD Unsupported code received ([dec])
Explanation An unexpected error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-3-UNSUPPORTED_PROTOCOL An unsupported protocol type [dec] received in GRE tunnel
Explanation An GRE tunnel packet was received with an unsupported protocol type as the payload.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-3-VERSION GRE tunnel packet received with bad version number ([dec])
Explanation A GRE tunnel packet was received with a bad version number.
Recommended Action NONE*
Error Message%PKT_INFRA-TUNNEL-3-ZERO_HEADER Encapsulation IP header length is zero
Explanation The length of the tunnel encapsulating header is zero.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-TUNNEL-6-DEBUG_ERROR Invalid value [dec] for debug
Explanation An invalid value was received for the debug flag.
Recommended Action No action is required.
Error Message%PKT_INFRA-TUNNEL-7-IFACE_NOT_UP Packet received on tunnel whose interface is not up
Explanation A packet was received on a tunnel whose interface status is not up.
Recommended Action No action is required.
VI_REPL Messages
Error Message%PKT_INFRA-VI_REPL-3-ISSU Failure during ISSU operation. [chars]. Error: [chars].
Explanation A failure occurred during the special handling that takes place during an ISSU operation.
Recommended Action The consequences of this error are unpredictable. There may be no problem but it is also possible it will affect virtual interface configuration during the ISSU. It is advisable to check all virtual interface configuration on the active and standby nodes before continuing with the ISSU operation.
Error Message%PKT_INFRA-VI_REPL-3-NAMESTRING Failure during initialization of virtual interface namestring [chars] for replication. [chars]. Error: [chars].
Explanation A failure occurred during the registration of a virtual interface namestring for replication.
Recommended Action The process will attempt to recover from this error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-VI_REPL-3-REPLICATE Virtual Interface config replication failed. [chars]. Error: [chars].
Explanation A failure occurred during the replication of an item of virtual interface configuration to one or more of the backup RPs.
Recommended Action The process will restart and attempt to recover from this error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-VI_REPL-7-EVENT Unrecoverable error in event loop. Error: [chars]
Explanation An unhandled error occured while waiting for an event.
Recommended Action The process will restart and attempt to recover from this problem. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PKT_INFRA-VI_REPL-7-INIT Failed to intialize config replicator. [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the Virtual Interface Config Replicator process.
Recommended Action The vi_config_replicator process will restart and attempt to recover from this error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.