BFM_API Messages

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.

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.

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.

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.

Recommended Action Copy the error message exactly as it appears on the 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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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.

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.

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.

Recommended Action Copy the error message exactly as it appears on the 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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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

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.

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.

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.

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.

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.

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.

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-BLOCK_UNTIL_ACTIVE Verification Daemon failed to block on sysmgr for the node to to go active: [chars]

Explanation The Verification Daemon failed to block on sysmgr for the node to go active.

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.

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.

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.

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.

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.

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.

FEA_DLL Messages

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.

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 The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. 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_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 this message is seen during adding acl to the interface, then configuration apply will fail. May be retrying to apply the acl conifg will succeed. If seen during removal of the acl config, this may lead to acl configuration hardware inconsistent. 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.

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.

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.

Recommended Action If this happened during applying acl to the interface the configuration will fail. Please retry the configuration. check status of prm_server process on LC. 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 The most common cause of this error is that there no more free TCAM entries available for ACL. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-FEA_DLL-3-TCAM_LIMIT TCAM [chars] limit exceeded

Explanation This message will typically occur when permissible single region size is exceeded or total number of entries allowed in TCAM for a given application is exceeded.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message

%PKT_INFRA-FEA_DLL-3-UIDB_ERR UIDB [chars] error: [chars] : [chars]

Explanation UIDB stores the reference to ACL entries programmed in TCAM for the interface, protocol and direction. This error message is due to one of the following reasons: 1. Initialization failure of Feature EA DLL and UIDB manager interface. 2. Failure to set reference of hardware entries programmed or removed for security ACL in UIDB on configuration or system changes. This failure can lead to mismatch between hardware and software configuration.

Recommended Action If the failure is on initialization, process restart is done automatically. No manual action is required. If the failure is to set configuration bits in hardware on detaching a security ACL from interface, attach and detach security ACL again on the interface. In all other cases, detach ACL in the error message from all interfaces of the line card where issue is seen. Now, re-attach ACL to the interfaces.

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

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 IOS-XR infra call failure resulting in a failure to provide some infrastructure service. These typically could be some IPC services or debug infrastructure, etc.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Recommended Action Copy the error message exactly as it appears on the 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.

Explanation im_caps_datapath_control to LPTS netio caps dll failed This is not a critical error, on getting the repeated occurrence of this error log, Copy the error message exactly as it appears, and report it to your technical support representative.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Recommended Action Copy the error message exactly as it appears on the 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.

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.

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-DENY_IN_ACL_NOT_SUPPORTED Deny action is not supported and will be ignored in [chars] ACL: [chars], ACE: [dec]

Explanation 'Deny' action for an ACE is not supported and will be ignored. The behavior will be the same as with Permit action.

Recommended Action If the behavior is not acceptable, remove the Qos policy from the interface, otherwise no further action is needed.

Error Message

%PKT_INFRA-FMGR-3-DENY_IN_ACL_NOT_SUPPORTED Deny action is not supported and will be ignored in [chars] ACL: [chars], ACE: [dec]

Explanation 'Deny' action for an ACE is not supported and will be ignored. The behavior will be the same as with Permit action.

Recommended Action If the behavior is not acceptable, remove the Qos policy from the interface, otherwise no further action is needed.

Error Message

%PKT_INFRA-FMGR-3-MATCH_TYPE_IN_ACL_NOT_SUPP_AFMON Match on [chars] is not supported in AFmon policy. ACE [dec] in [chars] ACL [chars] on interface [chars] will be ignored.

Explanation Only the following match types specified in an ACL are supported as part of an AFmon policy: Source/ Destination IP address, Source/ Destination Port values. An ACE containing any other match types will be ignored i.e. it will not be programmed in hardware.

Recommended Action No further action is required if the policy programming behavior, which is explained here, is acceptable. Otherwise the policy can be removed and an acceptable one re-applied.

Explanation The following match criteria specified in an ACL are not supported as part of a QoS policy: Packet Length, TTL, TCP Flags. An ACE containing any of these match fields will be ignored i.e. it will not be programmed.

Recommended Action If the behavior is not acceptable, remove the Qos policy from the interface and re-apply it after removing the un-supported match criteria.

Explanation The following match criteria specified in an ACL are not supported as part of a QoS policy: Packet Length, TTL, TCP Flags. An ACE containing any of these match fields will be ignored i.e. it will not be programmed.

Recommended Action If the behavior is not acceptable, remove the Qos policy from the interface and re-apply it after removing the un-supported match criteria.

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-SUPP_UDP_ONLY_AFMON Only rules matching UDP packets are supported in AFmon policy. ACE [dec] in [chars] ACL [chars] on interface [chars] will be ignored.

Explanation AFmon policy only allows matching on UDP flows. Other types of match rules will be ignored i.e. they will not be programmed in hardware.

Recommended Action No further action is required if the policy programming behavior, which is explained here, is acceptable. Otherwise the policy can be removed and an acceptable one re-applied.

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.

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.

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.

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.

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.

Explanation Null Driver partner encountered a 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation Null Driver partner encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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.

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.

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.

Explanation FWD was supplied with a plim port that exceeds the limit of num ports.

Recommended Action Collect console log and the following information and contact TAC support with this info Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. -debug netio drivers location loc -show netio trace all location loc

Recommended Action Collect console log and the following information and contact TAC support with this info Copy the error message exactly as 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 netio trace all location loc -From k-shell, get the output of following command(s) fwd_netio_debug

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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 An healthy running box, should not hit this point. Please contact TAC Support Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action Collect console log and the following information and contact TAC support with this info Copy the error message exactly as 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 netio trace all location loc -From k-shell, get the output of following command(s) fwd_netio_debug

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

Explanation Information exchanged between Txm node of netio chainwalker thread and bypass thread during bypass init. These pointers should be valid memmap pointers.

Recommended Action None

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.

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

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.

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.

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

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.

GIRO Messages

Explanation Configuration could not be restored on some interfaces after they were created.

Recommended Action Re-enter desired config manually. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation Configuration could not be restored on this interface after the interface was created.

Recommended Action Re-enter desired config manually. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

%PKT_INFRA-GIRO-6-ERROR_EXISTS Already exists error received from IM for interface [hex]

Explanation A caps add or interface create was attempted for a resource that already exists.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-GIRO-6-MTU_NEAR_HW_LIMIT The configured MTU of [unsigned int] on CH[hex] is close to the H/W limit, and hence large frames may be dropped as oversized frames

Explanation The configured MTU is close to the maximum frame size allowed on the interface. Hence large frames bigger than the maximum frame size supported on the interface may be dropped.

Recommended Action It is recommended that the configured MTU of the specified interface is reduced to ensure that all frames are within the H/W limits.

ICPE_DPM Messages

Explanation A SDACP discovery message was received on the interface, but was malformed and could not be decoded.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation There has been a mis-wiring or misbehaving satellite connected over the specified interface - the MAC from which the Satellite is reciving SDACP discovery packets is not the MAC address on which this host is sending them.

Explanation This indicates that a user has attempted to log into the specified satellite and failed authentication.

Recommended Action Check whether the password being used is correct.

Error Message

%PKT_INFRA-ICPE_GCO-5-FAILED_TO_SET_PASSWORD Satellite [dec] failed to set the specified password: '[chars]'

Explanation The satellite failed to set the password requested. This may result in inability to connect to the satellite via telnet.

Recommended Action Attempt to log into the satellite using the configured password. If this does not succeed then it may be necessary to remove and readd the password config, to restart the icpe_gco process, or to restart the satellite.

IFMGR_ENCAP Messages

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.

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.

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

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.

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.

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.

Explanation The ma-feature or ea-feature property was set twice within a rule. This property may have been set implicitly by the feature or owner-string properties. feature and owner-string are synonyms which set both the ma-feature and ea-feature properties. Please check the rules file.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation Multiple rules with the same static id were found in rules files. Every rule should have exactly one static id assigned to it.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-IFMGR-3-RULES_NO_ID Error: ID not found in the rules file [chars]

Explanation A rule with no static id is found in rules file. Every rule should have a static id assigned to it.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-IFMGR-3-RULES_PARSE_ERROR Error: The rules file [chars] could not be parsed. First error on line [dec]

Explanation The rules file cold not be parsed. Please check the rules file.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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-DROPPED_MSG Dropping message from node [chars] ([hex]) due to '[chars]'. Message version is [hex], whilst expected version is [hex]. [unsigned int] messages dropped in total for this reason.

Explanation A message received from the Interface Manager on a different node has been dropped. This is due to incompatible versions of the software communicating with each other and will result in interfaces not working correctly.

Recommended Action Verify that all nodes are using consistent image versions. If performing an upgrade this message will stop appearing once all nodes are consistent. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

Explanation The maximum packet size requested on an interface is outside its operational range. This may result in traffic loss on the interface.

Recommended Action Check the MTU configuration on the interface and its subinterfaces, 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.

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-NOTIF_DELIVERY_FAILED [chars] notification failed to be delivered to client: [chars]

Explanation An IM notification failed to be delivered to one of its clients. The most likely reason for this is an out-of-memory condition. This will have left that client out-of-sync with IM.

Recommended Action Check if the system is in a low-memory condition, and if so attempt to rectify this. Restart the ifmgr process on the affect node to attempt to bring it's clients back in-sync. If this doesn't 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.

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-IMPLICIT_DOWNLOAD_IN_PROGRESS After [unsigned int] minutes, implicit download of [unsigned int] interfaces has still not completed

Explanation An attempt 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) has taken an exceptionally long time. This may cause forwarding on this interface (via this node) to be broken.

Recommended Action The download will continue to be processed, 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.

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.

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.

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.

IFO_EA Messages

Error Message

%PKT_INFRA-IFO_EA-6-PD_ERROR_UL_INTF_REMOVAL The IFO EA platform DLL returned an error handling a interface update for an underlying interface removal operation on interface CH[hex]([hex]): [chars]. This interface may no longer correctly operate.

Explanation During the handling of a bundle member update notification, the platform returned an error which cannot be handled. The interface may continue trying to send traffic over an interface which it should no longer be using, resulting in traffic drops.

Recommended Action Copy the error message exactly as 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.'

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

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.

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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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

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. This may be caused by a transport drop.

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. This can also be caused by transport drops, e.g. as a consequence of removing a card. If neither of these cases hold, 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

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.

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

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-DAMPENING Line protocol on Interface [chars], dampening state changed to [chars]

Explanation The interface line protocol dampening state changed. When the state is 'suppressed' the interface will be held down. In 'unsuppressed' state, link state changes are allowed to occur as normal.

Recommended Action If the dampening state change was unexpected, confirm the configuration settings for the interface.

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.

Recommended Action Copy the error message exactly as 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

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.

NETIO Messages

Explanation This error indicates that a code sanity check has failed. This indicates the size of the global HSSD area defined in Pakman does not match the size that NetIO is expecting.

Recommended Action NetIO will not start properly until the code is fixed.

Error Message

%PKT_INFRA-NETIO-1-ERROR_HSSD_UNKNOWN Global HSSD area '[chars]' not known to NetIO

Explanation This error indicates that a code sanity check has failed. This indicates a new global HSSD area was added to Pakman without adding the appropriate endian transform code to NetIO.

Recommended Action NetIO will not start properly until the code is fixed.

Error Message

%PKT_INFRA-NETIO-3-BAD_PUNT_NODE NetIO DLL attempted to use a bad chain node (magic number [hex]) in packet punt to [chars]

Explanation A NetIO feature DLL has attempted to pass a bad chain node to a NetIO packet punt API. The packet has been dropped.

Recommended Action Identify the NetIO DLL that is passing the bad node, and contact the owners Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-NETIO-3-ERR_ARP [chars], [chars], [pointer]

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.

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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation A statically linked NetIO DLL has invoked a NetIO API before the callbacks table has been initialized

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

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.

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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Error Message

%PKT_INFRA-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.

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.

Recommended Action If the problem persists get the output of 'show process blocked' and 'show process netio'

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-ERR_PACKET_INPUT Failed to input the packet for [chars] ([chars])

Explanation This message indicates that the ARP packet queue is filling up faster than ARP can process the packets. It could be due to many addresses needing to be resolved on initial bring up. In this case packet drops are not a problem. Addresses will resolved as quick as possible and the condition will clear. If seen for a while then could imply some potential problem.

Recommended Action Copy the error message exactly as it appears on the 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.

Explanation NetIO gets restarted if a NetIO DLL fails to process an install event. 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-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.'

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

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

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

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.

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

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.

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.

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

Recommended Action If any of these messages recur, 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.

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.

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.

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.

PAKWATCH Messages

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.

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.

Explanation An attempt has been made to free a packet buffer that is already freed or that a buffer that is not owned by the calling process. This usually indicates the process using the packet has used it after it has been returned or after it has been sent to another process.

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), the full console logs and 'show proc pidin loc loc' Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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.

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.

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_BODY2 [hex] [dec]

Explanation The resource depletion information in the following format: PROGRAM_COUNTER 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-INFO_HEAD2 [chars] [chars]

Explanation The header for resource depletion information that follows this message. It is of the format: PROGRAM_COUNTER COUNT

PLATFORM_ASR9K_NETIO_LIB Messages

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

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_C12000_NETIO_LIB Messages

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

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_FWD Messages

Explanation Failed to get the logical port for the specified interface from the Platform Mgr. This will cause the interface to not get created properly.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-PLATFORM_FWD-3-ERROR [chars], [chars]

Explanation An error was encountered. A reason text will be supplied in the 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.

PLATFORM_HFR_NETIO_LIB Messages

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

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.

PQMON Messages

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'

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'

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.

PTP_OFFLOAD Messages

Error Message

%PKT_INFRA-PTP_OFFLOAD-3-PACKET_DROP Dropped a packet for an unknown protocol. Supported protocols are [chars]

Explanation The Prescision Time Protocol (PTP) received a packet with an unknown protocol encapsulation and dropped it. This may have been an incorrectly encapsulated PTP packet, in which case PTP may operate incorrectly, or a misdirected packet for another protocol, in which case other protocols may operate incorrectly.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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-CLIENT_NOTIFY_FAILED_FATAL Failed to notify packet-processing client (PID [dec]) of received packets, and unable to recover after repeated retries

Explanation An error was enountered when attempting to alert a packet- processing client of packets that have been delivered to it for processing, and repeated retries have not resolved the problem. No further retries will be attempted.

Recommended Action Restarting the process with the Process ID specified in the message may resolve the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-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.

Explanation SPP or one of its clients was unable to allocate a block in the SPP shared memory window. This indicates that either system resources are low, or that there is an internal problem with SPP or the shared memory infrastructure. It is likely that both ingress and egress packets will be dropped.

Recommended Action Wait until any situation which is putting stress on system resources is resolved, and then try the requested action 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.

Explanation An error was encountered while trying to perform an operation on a lock. The process will continue without retrying the operation. In most cases, no further adverse behaviour should be observed.

Recommended Action If the same message is seen repeatedly for a process, restarting the process may fix the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation An error was enountered when attempting to alert a packet- processing client of packets that have been delivered to it for processing. The system will retry to attempt to recover.

Recommended Action The system will attempt to recover by retrying. If the retries are successful then no further action is needed, or if unable to recover and the problem appears fatal then another message will be displayed. Alternatively, restarting the process with the Process ID specified in the message may resolve the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-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.

Explanation An interrupt pulse was received by SPP from the OS, but no handler was registered to take appropriate action. This indicates a problem in an SPP plug-in, which has registered for receiving the interrupt, but has not registered a corresponding handler. It is likely that ingress packets will be dropped.

Recommended Action Restarting the process may help to resynchronize the system state. 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.

Explanation A pulse was received by SPP from the OS or another process, but no handler was registered to take appropriate action. This indicates a problem with SPP if the pulse was received from the OS, or another process which sent the unexpected pulse.

Recommended Action Restarting the process may help to resynchronize the system state. 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-spp-4-INIT_FAILED Failed to initialize [chars]: [chars]%s

Explanation An error was encountered while the specified process was initializing. The error message contains details about the source of the error.

Recommended Action The process will exit and will be restarted. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation SPP or one of its clients was unable to register to monitor a shared memory mutex. This indicates that either system resources are low, or that there is an internal problem with SPP or the shared memory infrastructure. Restarting SPP or its client processes may result in memory leaks.

Recommended Action Wait until any situation which is putting stress on system resources is resolved, and then try the requested action 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.

Explanation A packet client was unable to allocate the required number of packets for transmission because no more packets are available. This may be a transient issue, if the system is under unusually heavy load, or if the situation persists it may indicate a packet client problem.

Recommended Action Attempt to reduce load on the system before trying the requested action 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.

Explanation An error was encountered while trying to load an SPP plugin library. The plugin will not be used. Packets may not be sent or received correctly for the affected location.

Recommended Action This problem may indicate an incompatible version of a plugin library has been installed. If the problem was triggered by an install operation, reversing the operation may fix the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-spp-4-TIMER_FAILED Failed to initialize 1Hz timer used to handle rollover of the system timestamp clock. Some SPP show commands may show incorrect timings. Error: [chars]

Explanation SPP failed to initialize its periodic 1Hz timer, which is used to ensure that rollover of the system timestamp is handled correctly. It is likely that times reported by the following show commands will be incorrect as a result: - show spp node

Recommended Action Restarting the SPP process may help to resynchronize the system state. 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-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.

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.

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.

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.

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.

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.

SW_OFFLOAD Messages

Error Message

%PKT_INFRA-SW_OFFLOAD-4-PROTOCOL_UPDATE_FAILED Protocols may not operate correctly

Explanation An error was encountered while attempting to set up protocol sessions. Affected protocols may operate incorrectly or not at all.

Recommended Action The system has already made repeated attempts to correct the problem automatically but without success. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

TCAM_MGR_LIB Messages

Error Message

%PKT_INFRA-TCAM_MGR_LIB-3-INTERNAL_ERR Internal error: [chars]

Explanation An internal error occurred in TCAM Manager which involves exiting the process. After the TCAM Manager process restarts, the error should have been cleared. *DDTS*

Recommended Action Collect the configuration, syslog and coredump file. Attach them to the ddts. After the process restarts automatically, the error should have been cleared and no user action is needed.

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. 4) use the compression anchor prefix cli controller pse tcam location R/S/I compression ipv6 anchor-prefix to configure the common IPv6 prefix lengths 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

Explanation 'Typically this indicates an error condition, ' 'such as tcam mgr crashes while internal dats are updated. ' 'and leave the internal data in an inconsistent state ' 'To recover from the error, ' 'TCAM Manager has to reset its internal data.'

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.

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 This is an internal initialization error.

Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea. If the problem persists, copy the error message as it appears on the console and any noticeable side effects. Copy the error message exactly as it appears on the 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 This is typically an internal error in the software. The software failed to initialize the code that handles/processes events related to tunnel_ea.

Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea. If the problem persists, copy the error message as it appears on the console and any noticeable side effects. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Explanation This is typically an internal error in the software. The software failed to initialize a communication channel in the card where the error is seen.

Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea. If the problem persists, copy the error message as it appears on the console and any noticeable side effects. Copy the error message exactly as it appears on the 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 This is typically an internal error in the software. The software failed to initialize a connection to another process in the card where the error is seen.

Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea. If the problem persists, copy the error message as it appears on the console and any noticeable side effects. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Explanation This is typically an internal error in the software. The software failed to create the interface on the engine..

Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea. If the problem persists, copy the error message as it appears on the console and any noticeable side effects. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation This is typically an internal error in the software. The software is not signalled to start accepting events associated with it.

Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea. If the problem persists, copy the error message as it appears on the console and any noticeable side effects. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Explanation This is typically an internal error in the software. The software failed to initialize statistics infrastructure on the card where the error is seen.

Recommended Action If there is a problem, it might be cleared by restarting tunnel_ea. If the problem persists, copy the error message as it appears on the console and any noticeable side effects. Copy the error message exactly as 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.

Recommended Action Copy the error message exactly as it appears on the 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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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.

Explanation Tunnel count has been decremented till it became negative. process tunnel_infra will restart to recover from the situation.

Recommended Action Ideally this should never happen and points to a serious bug in pfi/tunnel/infra File a tracking DDTS if it happens.

Error Message

%PKT_INFRA-TUNNEL-3-NO_IDB IDB not available in context

Explanation Could not find the tunnel IDB in the context structure.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-TUNNEL-3-NO_INTERFACE Interface [chars] does not exist to delete

Explanation A request to delete a non-existent interface has been received. This is relatively a harmless error, unless it is too frequent, in which case the reason for the error must be investigated, starting with the name of the interface printed in the error message.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%PKT_INFRA-TUNNEL-3-NULL_DPC NULL DPC received

Explanation The EA received a datapath control with NULL input data.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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.

Recommended Action Copy the error message exactly as it appears on the 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 Copy the error message exactly as it appears on the 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

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.

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.

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.

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.