Cisco SD-WAN System Error Messages Guide for Cisco IOS XE SD-WAN 16.11.x

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco SD-WAN System Error Messages Guide for Cisco IOS XE SD-WAN 16.11.x

Chapter Title

ENVIRONMENTAL through GBIC_SECURITY

Results

Updated:
May 2, 2019

Chapter: ENVIRONMENTAL through GBIC_SECURITY

ENVIRONMENTAL through GBIC_SECURITY

ENVIRONMENTAL through ESS_FEATURE

ENVIRONMENTAL

%ENVIRONMENTAL-3-TDLERROR : Error processing TDL message. [dec]
Explanation An unexpected condition in which IOS has received a TDL message which it can not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ENVIRONMENTAL-1-ALERT : [chars], Location: [chars], State: [chars], Reading: [dec] [chars]
Explanation One of the sensors in the system is reading an out of normal value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ENVIRONMENTAL-6-NOTICE : [chars], Location: [chars], State: [chars], Reading: [dec] [chars]
Explanation Informational message on the sensor reading
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ENVIRONMENTAL-5-SENSOROK : [chars], Location: [chars], State: normal
Explanation One of the sensors in the system had been in a failure condition but is now operating normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ENVIRONMENTAL-1-SENSORFAIL : [chars], Location [chars], State: fail
Explanation One of the sensors in the system has detected a failure condition from which it can not recover. This sensor is no longer reporting readings to the environmental monitoring subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ENVIRONMENTAL-3-CHASFSERR : Sensor [chars] on FRU [chars] has an invalid chasfs device state [chars]
Explanation The system does not understand the state that the sensor is reporting. This is most likely a filesystem corruption or ISSU problem. You may try rebooting the router to see if the problem corrects itself.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ENVIRONMENTAL-6-INFO : [chars]
Explanation Informational message of ambient sensor reading
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ENVM

%ENVM-3-NOFORK : Could not create environmental polling process
Explanation
Recommended Action


%ENVM-4-READERROR : Error reading temperature sensor [dec]
Explanation
Recommended Action


%ENVM-4-LONGBUSYREAD : C2W Interface busy for long time reading temperature sensor [dec]
Explanation
Recommended Action


%ENVM-4-WRITEERROR : Error writing temperature sensor [dec]
Explanation
Recommended Action


%ENVM-4-LONGBUSYWRITE : C2W Interface busy for long time writing temperature sensor [dec]
Explanation
Recommended Action


EPBR_PROXY

%EPBR_PROXY-2-EPBR_MSG_PROXYINIT_FAILURE : EPBR - Failed to register IPC message handler, result code [int]
Explanation QFP EPBR feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EPBR_PROXY-3-EPBR_MSG_PROXY_UNKNOWN_IPCMSG : EPBR - Received an unknown type (code [int]), IPC message
Explanation QFP EPBR feature received an unknown message from another layer of EPBR feature's software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%EPBR_PROXY-3-EPBR_MSG_PROXY_INVALID_MSGLEN : EPBR - Received an invalid length IPC message
Explanation QFP EPBR feature received an incorrect length of IPC message from anoter layer of EPBR feature's software stack, m_enum %d, m_subtype %d, m_len %d, m_flags 0x%x, m_source %d.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EPBR_PROXY-3-EPBR_MSG_PROXY_ALLOC_FAILURE : EPBR - Failed to get [int] bytes space for IPC reply message
Explanation QFP ET-Anallytics feature detected buffer allocation failure while sending reply to a message from another layer of EPBR feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EPBR_PROXY-3-EPBR_MSG_PROXY_OPENREPLY_FAIL : EPBR - Failed to open reply message part of IPC packet
Explanation QFP EPBR feature failed to open message part of IPC packet while sending a reply to another layer of EPBR feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EPBR_PROXY-3-EPBR_MSG_PROXY_IPCSEND_FAIL : EPBR - Failed to send IPC message, result code [dec]
Explanation QFP EPBR feature failed to send IPC message to another layer of EPBR feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EPBR_PROXY-3-EPBR_MSG_PROXY_DEBUG_REG_FAILED :
Explanation EPBR Conditional Debugging Registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EPBR_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid EPBR IPC message length.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


EPC

%EPC-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for EPC
Explanation EPC Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION


%EPC-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for EPC
Explanation EPC Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION


EPM

%EPM-6-POLICY_REQ :
Explanation This message indicates that a policy application/remove request has been received by the EPM
Recommended Action No action required


%EPM-6-POLICY_APP_SUCCESS :
Explanation This message indicates that the displayed policy for the client has been applied successfully by the EPM
Recommended Action No action required


%EPM-4-POLICY_APP_FAILURE :
Explanation This message indicates that the displayed policy for the client could not be applied by the EPM
Recommended Action Policy application failure could happen due to multiple reasons.The reason for the failure is notified to the client and the client has to take appropriate action based on it


%EPM-6-AAA :
Explanation This message indicates a download request has been sent/downloaded successfully for the specified dACL
Recommended Action No action required


%EPM-4-ACL_CONFIG_ERROR :
Explanation This message indicates that adding an ACE to the specified ACL was ignored because of wrong configuration
Recommended Action Change ACE configuration for the specifed ACL


%EPM-6-IPEVENT :
Explanation This message indicates the IP event Wait/Release/Assignment that has occured with respect to the specified host
Recommended Action No action required


%EPM-6-AUTH_ACL :
Explanation his message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been applied or removed
Recommended Action No action required


EPM_PLUGIN

%EPM_PLUGIN-5-ERR_VLAN_NOT_FOUND :
Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VTP database.
Recommended Action Make sure the VLAN exists and is not shutdown or use another VLAN.


EPOCH

%EPOCH-6-EPOCH_REJECTED : Peer [chars] has rejected epoch: [chars]
Explanation This error occurs if epoch from shell-manager has been rejected by the peer.
Recommended Action Check the epoch and peer state.


ERM

%ERM-6-NOTIFY : Owner: [chars](%0llx), User: [chars](%0llx), Threshold Type: [chars], Level: [chars], Direction: [chars], Limit: [int], Usage: [int], Policy ID: [dec]
Explanation A notification has been sent out by the resource owner because of a threshold violation.
Recommended Action This is just informational message only. This message appears because a threshold has been violated. Do 'show runnning' and look for the configuration under the mode 'resource manager' and check the thresholds that has been set. This is just a notification that the threshold has been violated - nothing to stop the resource exhaustion is being done here.


ERSPAN

%ERSPAN-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for ERSPAN
Explanation ERSPAN Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION


%ERSPAN-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for ERSPAN
Explanation ERSPAN Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION


ESS_FEATURE

%ESS_FEATURE-3-ESF_STUB : CPP ESS per-session feature ([chars]) executes stub entry in [chars] direction
Explanation Cisco internal software error. CPP ESS per-session feature stub entry got executed. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_FEATURE-4-ESF_DROP_POLICY : CPP ESS feature encounted unexpected linktype=[dec]
Explanation Cisco internal software error. CPP ESS per-session feature encounted unexpected linktype when executing output drop policy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ESS_IPSUB through ETHERNET_PROXY

ESS_IPSUB

%ESS_IPSUB-3-ESS_IPSUB_STUB : CPP ESS IPSUB executes stub entry in [chars] direction
Explanation Cisco internal software error. CPP ESS IPSUB stub entry got executed. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_IPSUB-3-FSOL_THROTTLE_ERR : Allocation of [chars] memory failed for ESS IP Subscriber
Explanation Allocation of memory resource demanded by ESS IPSUB FSOL throttle failed. This is a serious problem at the ESS IPSUB FSOL initialization for throttling.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ESS_PROXY

%ESS_PROXY-2-IPC_THROTTLE_ERR : Allocation of [chars] memory failed for ESS Proxy unsolicited event throttling
Explanation Allocation of memory resource demanded by ESS Proxy throttle failed. This is a serious problem at the ESS Proxy IPC initialization for unsolicited event throttling.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-2-PROXY_IPC_INIT_FAILED : CPP ESS Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP ESS Proxy initialization detected that the IPC interface initialization failed. CPP ESS proxy will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-3-PROXY_BAD_MSG : CPP ESS Proxy received bad length message type [dec]
Explanation Cisco internal software error. CPP ESS Proxy received a corrupted message from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-3-PROXY_INV_MSG : CPP ESS Proxy received invalid message type [dec]
Explanation Cisco internal software error. CPP ESS Proxy received an invalid message type from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-3-PROXY_IPC_ALLOC_FAILED : CPP ESS Proxy [chars] message lost due to message buffer allocation failure., MSGDEF_LIMIT_MEDIUM
Explanation Cisco internal software error. CPP ESS Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-3-PROXY_IPC_SEND_FAILED : CPP ESS Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. CPP ESS Proxy message processing detected a message sent failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-3-PROXY_IPC_NO_HDLR : CPP ESS Proxy received unregistered message type [dec]
Explanation Cisco internal software error. CPP ESS Proxy received a message from control plane but there is no registered handler. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-2-KA_CHANNEL_ALLOC_FAILED : CPP ESS Proxy Session Keepalive channel creation failure.
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the channel creation failed. CPP ESS proxy session keepalive will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-2-KA_PKT_REPLICA_REG_FAILED : CPP ESS Proxy Session Keepalive packet replication registration failure (result: [dec]).
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the packet replication registration failed. CPP ESS proxy session keepalive will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-2-KA_TIMER_INIT_FAILED : CPP ESS Proxy Session Keepalive timer initialization failure.
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the timer initialization failed. CPP ESS proxy session keepalive will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_PROXY-2-KA_PKT_TMPL_BFR_ALLOC_FAILED : CPP ESS Proxy Session Keepalive packet template allocation failure ([chars] buffer length: [dec]).
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the packet template buffer allocation failed. CPP ESS proxy session keepalive will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ESS_SWITCH

%ESS_SWITCH-3-ESS_STUB : CPP ESS switching ([chars]) feature executes stub entry in [chars] direction
Explanation Cisco internal software error. CPP ESS Switching feature stub entry got executed. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ESS_SWITCH-3-STATS_INVALID_PTR : CPP ESS Switching invalid statistics block for session [chars]., MSGDEF_LIMIT_GLACIAL
Explanation Cisco internal software error. CPP ESS Switching session contains an invalid statistics block. The session statistics is lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ETHERCHANNEL

%ETHERCHANNEL-2-PROXY_IPC_INIT_FAILED : QFP Etherchannel Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Etherchannel initialization detected that the Proxy IPC interface initialization failed. The EC Bundle interfaces will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERCHANNEL-3-INV_PROXY_MSG : QFP ETHERCHANNEL Proxy received invalid Message ID [dec]
Explanation Cisco internal software error. QFP Etherchannel Proxy received an invalid Message ID. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERCHANNEL-3-PROXY_IPC_ALLOC_FAIL : QFP ETHERCHANNEL Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP ETHERCHANNEL Proxy message processing detected a IPC buffer allocation failure during response processing. The associated ETHERCHANNEL interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERCHANNEL-3-PROXY_SID_UPDATE_LOCK_ERROR : QFP EC Proxy ([chars]) Multiple SID Update Locks to same interface (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP EC Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERCHANNEL-3-PROXY_SID_UPDATE_COMPLETE_ERROR : QFP EC Proxy ([chars]) SID Update Complete w/o Preceeding Lock (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP EC Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERCHANNEL-3-LOCK_ERROR : QFP EC Lock Failure: retval:[dec] tries[dec]
Explanation Cisco internal software error. QFP EC Lock Failure locking attempt failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERCHANNEL-3-LOCK_STATE_ERROR : QFP EC Lock State Failure: retval:[dec]
Explanation Cisco internal software error. QFP EC Lock State Failure Illegal lock state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ETHERCHANNEL_LB

%ETHERCHANNEL_LB-3-MSG_SEND_FAIL : The load-balance message [dec] has failed to send
Explanation The load-balancing feature has detected an error while trying to send an internal message.
Recommended Action If this message was the result of performing a configuration command, then try unconfiguring and reconfiguring the same command. If the error message continues to be displayed then it may indicate that the system is low on memory. The show memory free command should be used to check if the system has sufficient available memory. If the system appears to have available memory and the error continues to be displayed, then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the version of IOS being used.


%ETHERCHANNEL_LB-3-XDR_MSG_XMIT_FAIL : Failed to transmit XDR message of size [dec] to slot [dec]
Explanation An error occurred while attempting to send a load-balancing XDR message to the specified slot.
Recommended Action Because the message failed to send, the specified slot may now be out of sync with the rest of the system. To correct the issue the card in the specified slot may be rebooted, at which point the full configuration will be re-synced with the card in that slot. If the specified slot is zero, then that message was intended for cards in all slots, and the router should be reloaded to re-sync the entire system.


ETHERNET_LACP

%ETHERNET_LACP-1-ISSU_NOMEMORY : msgtxt_nomemory
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%ETHERNET_LACP-3-ISSU_SENDFAILED : LACP ISSU: send message failed, rc = [dec]
Explanation The sending of a message has failed. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_LACP-4-ISSU_INCOMPATIBLE : lacp-issu-compat: returned FALSE
Explanation The ISSU compatibility matrix check has failed. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_LACP-4-ISSU_XFORM : [chars]: failed, rc=[chars]
Explanation The ISSU transform has failed. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_LACP-4-RF_CLIENT_INIT : LACP HA: Unable to initiate RF client.
Explanation LACP is unable to initialize as a RF client. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_LACP-4-RF_CLIENT_BUNDLE : LACP HA: Unable initiate checkpoint bundle mode.
Explanation LACP is unable to initialize checkpoint bundle mode. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


ETHERNET_MLACP

%ETHERNET_MLACP-3-SYS_CFG_DUPL_ID : Remote mLACP peer has duplicate mLACP node-id [dec]
Explanation A remote mLACP peer is configured with the same mLACP node-id as this device.
Recommended Action Reconfigure the mLACP node-id to be unique between the two devices with the mlacp node-id configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP.


%ETHERNET_MLACP-3-SYS_CFG_INVALID_ID : Received invalid mLACP node-id [dec] from peer
Explanation A remote mLACP peer is configured with an invalid mLACP node-id.
Recommended Action Reconfigure the peer to send a valid mLACP node-id with the mlacp node-id configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP.


%ETHERNET_MLACP-3-PEER_ICCP_VERSION_INCOMPATIBLE : Peer ICCP version [dec] is incompatible with local ICCP version [dec].
Explanation mLACP peer is running with a different version of ICCP. Incompatible ICCP would prevent mLACP from working properly.
Recommended Action Reboot peer with identical IOS version would correct the issue. Compatible ICCP version between different IOS images can still be achieved by doing show lacp multichassis group on the both devices to check if ICCP versions are compatible. If ICCP versions are incompatible, repeat IOS image loading and CLI above until a compatible image is loaded.


%ETHERNET_MLACP-4-ICRM_CLIENT_RECV_REJ : Received rejected mLACP TLV from peer with message ID [dec]
Explanation A remote mLACP peer has rejected an mLACP TLV.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.


%ETHERNET_MLACP-4-ICRM_CLIENT_RECV_BAD_LEN : Received an mLACP TLV with bad length [dec], total message length [dec]
Explanation The mLACP TLV length is longer than the total message length.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative. Provide the representative with the exact message being seen as well as the output of the following commands, show version, show run, show lacp multi-chassis group, and show lacp multi-chassis port-channel.


%ETHERNET_MLACP-4-ICRM_CLIENT_RECV_NO_TYPELEN : Received an mLACP TLV without a type and/or length field ([dec])
Explanation mLACP received an improperly formatted TLV from the peer. As a result the local and peer devices may have mismatched state data.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.


%ETHERNET_MLACP-4-CORE_ISOLATION : mLACP Core isolation failure: Attempting to failover [dec] LAGs in redundancy group [int]
Explanation mLACP has detected isolation from the core and has attempted to failover.
Recommended Action Use the show interchassis redundancy command to determine which core facing interface has triggered the isolation failure. Correct the failure for the given interface, this will clear the mLACP core isolation failure. Reference the mLACP section of the IOS documentation for more information on core isolation failures and related configuration commands.


%ETHERNET_MLACP-4-CORE_CONNECTED : mLACP has recovered from a core isolation failure. Attempting to recover [dec] LAGs in redundancy group [int]
Explanation mLACP has recovered from core isolation and has attempted to recover the LAGs in the redundancy group.
Recommended Action This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on core isolation failures and related configuration commands.


%ETHERNET_MLACP-4-PEER_DOWN : mLACP Peer down failure: Attempting to make [dec] local LAGs active in redundancy group [int]
Explanation mLACP has detected a peer down failure and has attempted to make the local port-channels become active.
Recommended Action The peer down failure should be corrected by re-enabling communication with the peer mLACP device. Use the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures.


%ETHERNET_MLACP-4-PEER_UP : mLACP has recovered from a peer down failure in redundancy group [int]
Explanation mLACP is now in communication with the peer device, and has recovered from a previous peer down failure.
Recommended Action This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on peer down failures and related configuration commands.


%ETHERNET_MLACP-4-PEER_DISCONNECT : An mLACP peer has disconnected from redundancy group [int], attempting to reconnect
Explanation mLACP has detected that a peer device from the specified redundancy group has disconnected. mLACP will attempt to reconnect to the device until successful.
Recommended Action This message is typically caused by a configuration event on the peer router, and so no action may be necessary. However if this message is unexpected then issue the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures.


%ETHERNET_MLACP-4-PEER_RECONNECT_FAILED : The attempt to reconnect to the peer in redundancy group [int] has failed
Explanation After an mLACP peer device disconnected, an attempt was made to reconnect, however that attempt has failed.
Recommended Action To reinitialize the connection, unconfigure mlacp interchassis group from the port-channel, and then reconfigure it. After doing that, issue show redundancy interchassis to get the peer member IP connection status and the mLACP connection state. If the peer member IP connection status is not CONNECTED then there is a more basic communication issue that needs to be fixed. Otherwise if the peer member IP is CONNECTED but the mLACP state is not CONNECTED, then there could be a software issue. In that case collect the output of show redundancy interchassis, show lacp multi-chassis group, and show lacp multi-chassis port-channel. Then please contact your Cisco technical support representative and provide the collected information.


%ETHERNET_MLACP-6-PEER_CONNECT : mLACP peer is now connected in redundancy group [int]
Explanation This message indicates that the local mLACP device is now connected to a peer device in the specified redundancy group.
Recommended Action No action is required. To view the peer information the command show lacp multi-chassis port-channel or show lacp multi-chassis group may be issued.


%ETHERNET_MLACP-4-PC_CHANGE : mLACP [chars] status changed to [chars]
Explanation A mLACP port-channel state change event has occurred. This might have been caused by a mLACP failure or recovery event on the local or peer POA in the same redundancy group. It is normal to get these messages during provisioning and administrative actions on the mLACP port-channel.
Recommended Action User should debug further to analyze root cause of the event. Use show redundancy interchassis , show lacp multi-chassis port-channel, show lacp multi-chassis group and show lacp internal on both POAs to check mLACP port-channel health. If any failure exists, appropriate actions should be taken to recover port-channel from failure. If failure persists then please contact your Cisco technical support representative and provide the collected information.


ETHERNET_OAM

%ETHERNET_OAM-2-CRIT_ERR : The Ethernet OAM protocol has encountered the critical error: [chars].
Explanation The protocol has run into a critical error. The reason should be given in the brackets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_OAM-6-CRITICAL_EVENT : The client on interface [chars] has received a Critical Event indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates a Critical Event has occurred. The indicated action will be performed. If the action is error-block the link will go into error-block state, where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable, the link is brought down.
Recommended Action Investigate the issue on the remote peer


%ETHERNET_OAM-6-DYING_GASP : The client on interface [chars] has received a Dying Gasp indication from its remote peer (failure reason = [chars], action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates a Dying Gasp, which may signal that the remote client is about to go down. The indicated action will be performed. If the action is error-block the link will go into error-block state, where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable, the link is brought down.
Recommended Action Investigate the issue on the remote peer


%ETHERNET_OAM-6-LINK_FAULT : The client on interface [chars] has received a Link Fault indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates a Link Fault has been detected. This indicates a fault has occurred in the receive direction of the sending client. The indicated action will be performed. If the action is error-block the link will go into error-block state, where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable, the link is brought down.
Recommended Action Check the wiring between the two interfaces.


%ETHERNET_OAM-6-CRITICAL_EVENT_CLEAR : The client on interface [chars] has received a clear of the Critical Event indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates that the Critical Event condition previously seen has cleared. If the action was error-block, traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface.
Recommended Action No action is required.


%ETHERNET_OAM-6-DYING_GASP_CLEAR : The client on interface [chars] has received a clear of the Dying Gasp indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates that the Dying Gasp condition previously seen has cleared. If the action was error-block, traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface.
Recommended Action No action is required.


%ETHERNET_OAM-6-LINK_FAULT_CLEAR : The client on interface [chars] has received a clear of the Link Fault indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates that the Link Fault condition previously seen has cleared. If the action was error-block, traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface.
Recommended Action No action is required.


%ETHERNET_OAM-5-LINK_MONITOR : [chars] detected over the last [chars] on interface [chars].
Explanation A monitored error has been detected to have crossed the user-specified threshold.
Recommended Action No action is required.


%ETHERNET_OAM-5-EVENTTLV : [chars] is received from the remote client on interface [chars].
Explanation An Event TLV is received from the remote OAM client. It must have detected errors in receiving frames from this local interface.
Recommended Action No action is required.


%ETHERNET_OAM-6-LOOPBACK : Interface [chars] has [chars] the [chars] loopback mode.
Explanation The specified interface has entered or exited loopback mode because of protocol control or an external event, such as the interface link going down.
Recommended Action No action is required.


%ETHERNET_OAM-3-LOOPBACK_ERROR : Loopback operation on interface [chars] has encountered an error([chars]).
Explanation Because of the specified error, the loopback operation has ended abnormally.
Recommended Action No action is required.


%ETHERNET_OAM-6-ENTER_SESSION : The client on interface [chars] has entered the OAM session.
Explanation Ethernet OAM client on the specified interface has detected a remote client and has entered the OAM session.
Recommended Action No action is required.


%ETHERNET_OAM-6-EXIT_SESSION : The client on interface [chars] has left the OAM session.
Explanation Ethernet OAM client on the specified interface has experienced some state change.
Recommended Action No action is required.


%ETHERNET_OAM-6-LINK_TIMEOUT : The client on interface [chars] has timed out and exited the OAM session.
Explanation The Ethernet OAM client on the specified interface has not received any OAMPDUs in the number of seconds for timeout that were configured by the user. The client has exited the OAM session.
Recommended Action No action is required.


%ETHERNET_OAM-4-ISSU_INCOMPATIBLE : ether_oam-issu-compat: returned FALSE
Explanation The compatibility checking has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_OAM-3-TRANSFORM_FAIL : ETHERNET OAM ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the ETHERNET OAM state between the active device and the standby device is not identical.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>)


%ETHERNET_OAM-2-GET_BUFFER : ETHERNET OAM ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


%ETHERNET_OAM-3-SESSION_UNREGISTRY : ETHERNET OAM ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client failed to unregister session information.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%ETHERNET_OAM-2-INIT : ETHERNET OAM ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_OAM-2-SEND_NEGO_FAILED : ETHERNET OAM ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


%ETHERNET_OAM-2-SESSION_REGISTRY : ETHERNET OAM ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%ETHERNET_OAM-3-INVALID_SESSION : ETHERNET OAM ISSU client does not have a valid registered session.
Explanation The ETHERNET OAM ISSU client does not have a valid registered session.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%ETHERNET_OAM-3-MSG_SIZE : ETHERNET OAM ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client failed to calculate the MTU for the specified message. The ETHERNET OAM ISSU client is not able to send the message to the standby device.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%ETHERNET_OAM-2-SESSION_NEGO : ETHERNET OAM ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The ETHERNET OAM ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


ETHERNET_PMLACP

%ETHERNET_PMLACP-3-SYS_CFG_DUPL_ID : Remote P-mLACP peer has duplicate P-mLACP node-id [dec]
Explanation A remote P-mLACP peer is configured with the same P-mLACP node-id as this device.
Recommended Action Reconfigure the P-mLACP node-id to be unique between the two devices with the mlacp node-id configuration command. Refer to the P-mLACP configuration section of the Cisco IOS documentation for more information on configuring P-mLACP.


%ETHERNET_PMLACP-3-SYS_CFG_INVALID_ID : Received invalid P-mLACP node-id [dec] from peer
Explanation A remote P-mLACP peer is configured with an invalid P-mLACP node-id.
Recommended Action Reconfigure the peer to send a valid P-mLACP node-id with the mlacp node-id configuration command. Refer to the P-mLACP configuration section of the Cisco IOS documentation for more information on configuring P-mLACP.


%ETHERNET_PMLACP-3-PEER_ICCP_VERSION_INCOMPATIBLE : Peer ICCP version [dec] is incompatible with local ICCP version [dec].
Explanation P-mLACP peer is running with a different version of ICCP. Incompatible ICCP would prevent P-mLACP from working properly.
Recommended Action Reboot peer with identical IOS version would correct the issue. Compatible ICCP version between different IOS images can still be achieved by doing show lacp multichassis load-balance group on the both devices to check if ICCP versions are compatible. If ICCP versions are incompatible, repeat IOS image loading and CLI above until a compatible image is loaded.


%ETHERNET_PMLACP-4-ICRM_CLIENT_RECV_REJ : Received rejected P-mLACP TLV from peer with message ID [dec]
Explanation A remote P-mLACP peer has rejected an P-mLACP TLV.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the P-mLACP section of the IOS documentation to verify that P-mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.


%ETHERNET_PMLACP-4-ICRM_CLIENT_RECV_BAD_LEN : Received an P-mLACP TLV with bad length [dec], total message length [dec]
Explanation The P-mLACP TLV length is longer than the total message length.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the P-mLACP section of the IOS documentation to verify that P-mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative. Provide the representative with the exact message being seen as well as the output of the following commands, show version, show run, show lacp multi-chassis load-balance group, and show lacp multi-chassis load-balance port-channel.


%ETHERNET_PMLACP-4-ICRM_CLIENT_RECV_NO_TYPELEN : Received an P-mLACP TLV without a type and/or length field ([dec])
Explanation P-mLACP received an improperly formatted TLV from the peer. As a result the local and peer devices may have mismatched state data.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the P-mLACP section of the IOS documentation to verify that P-mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.


%ETHERNET_PMLACP-4-CORE_ISOLATION : P-mLACP Core isolation failure: Attempting to failover [dec] ports in redundancy group [int]
Explanation P-mLACP has detected isolation from the core and has attempted to failover.
Recommended Action Use the show interchassis redundancy command to determine which core facing interface has triggered the isolation failure. Correct the failure for the given interface, this will clear the P-mLACP core isolation failure. Reference the P-mLACP section of the IOS documentation for more information on core isolation failures and related configuration commands.


%ETHERNET_PMLACP-4-CORE_CONNECTED : P-mLACP has recovered from a core isolation failure. Attempting to recover [dec] ports in redundancy group [int]
Explanation P-mLACP has recovered from core isolation and has attempted to recover the ports in the redundancy group.
Recommended Action This message may not require any action. However the show lacp multi-chassis load-balance group and show lacp multi-chassis load-balance port-channel commands may be used to verify the state of the P-mLACP port-channels. Reference the P-mLACP section of the IOS documentation for details on core isolation failures and related configuration commands.


%ETHERNET_PMLACP-4-PEER_DOWN : P-mLACP Peer down failure: Attempting to make [dec] local ports active in redundancy group [int]
Explanation P-mLACP has detected a peer down failure and has attempted to make the local port-channels become active.
Recommended Action The peer down failure should be corrected by re-enabling communication with the peer P-mLACP device. Use the show redundancy interchassis command on both the local and peer P-mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the P-mLACP section of the IOS documentation for more information on peer down failures.


%ETHERNET_PMLACP-4-PEER_UP : P-mLACP has recovered from a peer down failure in redundancy group [int]
Explanation P-mLACP is now in communication with the peer device, and has recovered from a previous peer down failure.
Recommended Action This message may not require any action. However the show lacp multi-chassis load-balance group and show lacp multi-chassis load-balance port-channel commands may be used to verify the state of the P-mLACP port-channels. Reference the P-mLACP section of the IOS documentation for details on peer down failures and related configuration commands.


%ETHERNET_PMLACP-4-PEER_DISCONNECT : An P-mLACP peer has disconnected from redundancy group [int], attempting to reconnect
Explanation P-mLACP has detected that a peer device from the specified redundancy group has disconnected. P-mLACP will attempt to reconnect to the device until successful.
Recommended Action This message is typically caused by a configuration event on the peer router, and so no action may be necessary. However if this message is unexpected then issue the show redundancy interchassis command on both the local and peer P-mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the P-mLACP section of the IOS documentation for more information on peer down failures.


%ETHERNET_PMLACP-4-PEER_RECONNECT_FAILED : The attempt to reconnect to the peer in redundancy group [int] has failed
Explanation After an P-mLACP peer device disconnected, an attempt was made to reconnect, however that attempt has failed.
Recommended Action To reinitialize the connection, unconfigure mlacp interchassis group from the port-channel, and then reconfigure it. After doing that, issue show redundancy interchassis to get the peer member IP connection status and the P-mLACP connection state. If the peer member IP connection status is not CONNECTED then there is a more basic communication issue that needs to be fixed. Otherwise if the peer member IP is CONNECTED but the P-mLACP state is not CONNECTED, then there could be a software issue. In that case collect the output of show redundancy interchassis, show lacp multi-chassis load-balance group, and show lacp multi-chassis load-balance port-channel. Then please contact your Cisco technical support representative and provide the collected information.


%ETHERNET_PMLACP-6-PEER_CONNECT : P-mLACP peer is now connected in redundancy group [int]
Explanation This message indicates that the local P-mLACP device is now connected to a peer device in the specified redundancy group.
Recommended Action No action is required. To view the peer information the command show lacp multi-chassis load-balance port-channel or show lacp multi-chassis load-balance group may be issued.


ETHERNET_PROXY

%ETHERNET_PROXY-2-PROXY_IPC_INIT_FAILED : CPP ETHERNET Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP ETHERNET Proxy initialization detected that the IPC interface initialization failed. CPP ETHERNET proxy will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_PROXY-3-PROXY_BAD_MSG : CPP ETHERNET Proxy received bad length message type [dec]
Explanation Cisco internal software error. CPP ETHERNET Proxy received a corrupted message from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_PROXY-3-PROXY_INV_MSG : CPP ETHERNET Proxy received invalid message type [dec]
Explanation Cisco internal software error. CPP ETHERNET Proxy received an invalid message type from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_PROXY-3-PROXY_IPC_ALLOC_FAILED : CPP ETHERNET Proxy [chars] message lost due to message buffer allocation failure., MSGDEF_LIMIT_MEDIUM
Explanation Cisco internal software error. CPP ETHERNET Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_PROXY-3-PROXY_IPC_SEND_FAILED : CPP ETHERNET Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. CPP ETHERNET Proxy message processing detected a message sent failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHERNET_PROXY-3-PROXY_IPC_NO_HDLR : CPP ETHERNET Proxy received unregistered message type [dec]
Explanation Cisco internal software error. CPP ETHERNET Proxy received a message from control plane but there is no registered handler. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ETHER_LMI through EVENT

ETHER_LMI

%ETHER_LMI-6-MISMATCHED_VLAN_CONFIGURED : VLAN [chars] configured but not in VLAN mapping for UNI [chars]
Explanation VLANs configured on UNI but do not exist according to VLAN mapping received from Network via Ethernet LMI.
Recommended Action Verify configurations of VLANs on UNI to match those assigned.


%ETHER_LMI-6-MISMATCHED_VLAN_NOT_CONFIGURED : VLAN [chars] not configured but in VLAN mapping for UNI [chars]
Explanation VLAN mapping received from Network via Ethernet LMI do not match those which are configured on the UNI.
Recommended Action Verify configurations of VLANs on UNI to match those assigned.


ETHER_LMI_HA

%ETHER_LMI_HA-2-INIT : Ether LMI ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Ether LMI ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHER_LMI_HA-3-TRANSFORM : Ether LMI ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The Ether LMI ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Ether LMI state between the active device and the standby device is not identical.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>)


%ETHER_LMI_HA-3-MSG_NOT_OK : Ether LMI ISSU client 'Message Type [dec]' is not compatible
Explanation The Ether LMI ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%ETHER_LMI_HA-3-MSG_SIZE : Ether LMI ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Ether LMI ISSU client failed to calculate the MTU for the specified message. The Ether LMI ISSU client will not able to send the message to the standby device.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%ETHER_LMI_HA-3-INVALID_SESSION : Ether LMI ISSU client does not have a valid registered session.
Explanation The Ether LMI ISSU client does not have a valid registered session.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%ETHER_LMI_HA-2-SESSION_REGISTRY : Ether LMI ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Ether LMI ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%ETHER_LMI_HA-3-SESSION_UNREGISTRY : Ether LMI ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Ether LMI ISSU client failed to unregister session information.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%ETHER_LMI_HA-2-SESSION_NEGO : Ether LMI ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The Ether LMI ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%ETHER_LMI_HA-2-SEND_NEGO_FAILED : Ether LMI ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Ether LMI ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


%ETHER_LMI_HA-2-GET_BUFFER : Ether LMI ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Ether LMI HA client failed to get buffer space for building chkpt message. Message cannot be sent to standby device. If a problem occurs, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


ETHER_PLATFORM_SW

%ETHER_PLATFORM_SW-3-DOT1AH_DEL_MAP_FAILED : Unable to remove 802.1ah mapping entry for B-MAC [enet], C-MAC [enet].
Explanation The Ethernet Software Platform was unable to remove an 802.1ah mapping entry from the tree of entries.
Recommended Action This error may be transient. If the error persists you may need to reload the router.


%ETHER_PLATFORM_SW-3-DOT1AH_CHNK_LCK_FAILED : Unable to lock memory while learning C-MAC to B-MAC mapping
Explanation The Ethernet Software Platform was unable to lock a particular piece of memory while attempting to learn a C-MAC to B-MAC mapping
Recommended Action This error may be transient. If the error persists you may need to reload the router.


%ETHER_PLATFORM_SW-3-DOT1AH_PROC_ENQ_FAILED : Unable to enqueue a request to learn a C-MAC to B-MAC mapping
Explanation An error occurred while trying to enqueue a request to learn a C-MAC to B-MAC mapping.
Recommended Action This error may be transient. If the error persists you may need to reload the router.


%ETHER_PLATFORM_SW-3-EFP_CANNOT_CLEAR_DIM : Unable to clear EFP's encapsulation data
Explanation An error occurred while trying to clear the encapsulation data for an EFP.
Recommended Action Enable debugging with 'debug ethernet service instace'. Retry the operation that caused the error to see if additional debugging messages are provided. If the error persists you may need to reload the router.


%ETHER_PLATFORM_SW-3-REWRITE_FAILED : Unable to apply rewrite to packet
Explanation An error occurred while trying to perform an ingress rewrite operation on a frame.
Recommended Action This error may be transient. If the error persists you may need to reload the router.


%ETHER_PLATFORM_SW-3-BD_NULL : Unable to get bridge-domain [dec] information for EFP [dec]
Explanation The software dataplane was unable to get the bridge-domain information for the EFP.
Recommended Action This error may be transient. If the error persists you may need to reload the router.


%ETHER_PLATFORM_SW-3-NO_PD_EFP : Unable to find software platform EFP information for EFP ID [dec]
Explanation The software dataplane was unable to get the platform dependent EFP information for the EFP with the given ID.
Recommended Action This error may indicate a bug in the software dataplane implementation. If the error occurs after a specific configuration was performed then precisely record those configuration steps. Contact your Cisco technical support representative and provide the gathered information.


ETHER_SERVICE

%ETHER_SERVICE-6-EVC_VLAN_NOT_CONFIGURED : VLANs [chars] not configured at [chars] but is in a CEVLAN/EVC map
Explanation VLANs part of the CEVLAN/EVC map for an EVC associated to an interface but the interface doesn't have those VLANs configured
Recommended Action Verify configurations of VLANs on the interface


%ETHER_SERVICE-6-EVC_STATUS_CHANGED : status of [chars] changed to [chars]
Explanation EVC status has changed
Recommended Action No Action


%ETHER_SERVICE-6-UPDOWN : Service instance [dec] on interface [chars] changed to [chars]
Explanation Service instance shutdown due to errdisable
Recommended Action No Action


%ETHER_SERVICE-6-ERR_DISABLED : [chars] - shutdown service instance [dec] at [chars]
Explanation Service instance shutdown due to errdisable
Recommended Action No Action


%ETHER_SERVICE-4-UNSUP_MIRPENABLE : %% Not supported since no ethernet mac-flush notification mirp command is configured.
Explanation no ethernet mac-flush notification mirp is configured.
Recommended Action Configure ethernet mac-flush notification mirp command.


%ETHER_SERVICE-3-EFP_NO_MEMORY : [chars] : memory allocation failed for [chars]
Explanation memory allocation failed
Recommended Action 'show proc mem' or 'show buffs' to check if memory or buffer is full. shutdown unused tasks or reset cards usually can recover those memory leak problem. Copy the error and send it to TAC if those actions does not help.


%ETHER_SERVICE-3-EFP_NULL_POINTER : [chars] : [chars] pointer is NULL
Explanation NULL pointer
Recommended Action Copy the error and send it to TAC


%ETHER_SERVICE-3-EFP_INVALID_TYPE : [chars] : [chars] is INVALID
Explanation invalid type
Recommended Action Copy the error and send it to TAC


%ETHER_SERVICE-3-ETHER_CHAN_SERV_INSTANCE_POLICY_REMOVED : [chars] service policy [chars] has been removed from service instance [dec] of ethernet channel [chars] due to failure to install the policy on member link [chars].
Explanation The member link does not support the service policy or installation failed due to resources limitation at the time.
Recommended Action Check for any error message that indicates incompatiblity between the policy and the member link. Remove the member link from the ethernet channel and reconfigure the policy on the service instance. If the problem persists, copy the error exactly as it appears and report it to your technical support representative.


%ETHER_SERVICE-3-EFP_DEBUG_INIT_FAILURE : The Ether Infra Trace and Debug Library Failed to initialize successfully due to error: [int]
Explanation All trace and debug may not work
Recommended Action No Action


ETHER_SERVICE_IPC

%ETHER_SERVICE_IPC-3-IPCPORT_CREATE : Unable to create IPC port ([chars]).
Explanation Ethernet Service was unable to create an IPC port
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-IPCPORT_REGISTER : Unable to register IPC port ([chars]).
Explanation Ethernet Service was unable to register an IPC port
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-IPCPORT_REMOVE : Unable to remove IPC port ([chars]).
Explanation Ethernet Service was unable to remove an IPC port
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-IPCPROCESSES : Unable to create IPC processes on ([chars]).
Explanation Ethernet Service was unable to create IPC processes
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-4-NOIPCPORT : IPC port is NULL, ([chars])
Explanation Ethernet Service cannot send the message as the IPC port information is NULL. This is a warning message, no action is required.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-4-NOMESSAGE : Message is NULL, ([chars])
Explanation Cannot send the message as the message is NULL. This is a warning message, no action is required
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-4-NOIPCDATA : IPC Message has no data area, ([chars])
Explanation Cannot find data area in an IPC message. This is a warning message, no action is required
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-IPCSESSION : Unable to open an IPC session for communicating with ([chars]). Error: [chars]
Explanation This is an internal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-NOIPCDESC : Unable to allocate IPC descriptor for Ethernet Service on ([chars]).
Explanation This is an internal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-NOMEM : Unable to allocate memory for Ethernet Service on ([chars]).
Explanation This is an internal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-IPC_TRANSMIT_FAILED : IPC message transmission failure ([chars])
Explanation An error was detected when transmitting an IPC message between Standby RP and SP. The failure most likely occurred because of a software error. The message output identifies the type of error that occurred.
Recommended Action This could be a transient error. If this error persists, copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-IPC_RESP_ERROR : IPC send response error ([chars])
Explanation An error was detected in the response for an IPC message that was transmitted to the peer.
Recommended Action This error could be transient. If this error persists, copy the error message exactly as it appears, and report it to your technical support representative.


%ETHER_SERVICE_IPC-3-RMI_FAILED : Ethernet Infra failed to register with the Resource Manager (RMI), [chars]
Explanation Ethernet Infra registers with the Resource Manager (RMI) to get status notifications about resources (such as IPC) and uses them to throttle the sending to messages to the peer. The Ethernet Infra was unable to register itself with RMI and hence cannot throttle the sending of any messages. The system may still operate normally. This error most likely occured because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ETHER_SERVICE_IPC-3-RMI_CALLBACK : Ethernet Infra encountered an error while processing a callback from the Resource Manager (RMI), [chars]
Explanation Ethernet Infra registers with the Resource Manager (RMI) to get status notifications about resources (such as IPC) and uses them to throttle the sending to messages to the peer. The Ethernet Infra encountered an error while processing a callback from RMI. This error most likely occured because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


ETH_SPA_GEN

%ETH_SPA_GEN-3-CU_SFP_NOT_SUPP : CU-SFP is not supported on SPA-2x1GE-V2 / SPA-2x1GE-SYNCE
Explanation CU-SFP is not supported on SPA-2x1GE-V2 / SPA-2x1GE-SYNCE
Recommended Action Use PHY based ports for CU Connections


%ETH_SPA_GEN-3-UNSUPPORTED_XCVR : Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2
Explanation Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2
Recommended Action Consult the documentation and ensure supported transceivers are plugged into the SPA


ETH_SPA_GILA_FUGU

%ETH_SPA_GILA_FUGU-3-SPI4_SYNC_FAIL : [chars] : Sync check failed in [chars] SPI4 interafce
Explanation Synchronization check failed in the Gila/Fugu SPI4 interafce
Recommended Action Try reseating the SPA. If the issue persists, contact Cisco Technical Assistance Center.


%ETH_SPA_GILA_FUGU-3-SPI4_RDOOF_ERR : [chars] : [chars] Rdata Out of Frame error
Explanation An internal SPI4 error (SPI4 Rdata Out of Frame error) occured in the SPA.
Recommended Action If the issue persists, open a case with the Cisco Technical Assistance Center.


%ETH_SPA_GILA_FUGU-3-SPI4_OVF_ERR : [chars] : [chars] Overflow Error
Explanation An internal SPI4 error (SPI4 Overflow Error) occured in the SPA.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-SPI4_MCALPRTY_ERR : [chars] : [chars] Calender memory Parity error
Explanation An internal SPI4 error (SPI4 calender memory parity error) occurred in the SPA.
Recommended Action If the issue persists, it may be a case of bad hardware. Please open a case with Cisco technical support personnel for further assistance.


%ETH_SPA_GILA_FUGU-3-SPI4_MCALRBPRTY_ERR : [chars] : [chars] Calender memory read back Parity error
Explanation An internal SPI4 error (SPI4 Calender memory read back parity error) occurred in the SPA.
Recommended Action Try reseating the SPA and if the issue persists, open a case with the Cisco Technical Assistance Center.


%ETH_SPA_GILA_FUGU-3-SPI4_MDATAPRTY_ERR : [chars] : [chars] Memory Parity error
Explanation An internal SPI4 error (SPI4 DATA FIFO Memory Parity error) occured in the SPA.
Recommended Action If the issue persists, open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-SPI4_MCNTPRTY_ERR : [chars] : [chars] Memory Parity error
Explanation An internal SPI4 error (SPI4 Control FIFO Memory Parity error) occurred in the SPA.
Recommended Action If the issue persists, open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-VLAN_TCAM_ERR : TCAM programming error at offset [dec]
Explanation An error was encountered when programming the VLAN TCAM. Two tcam entries are seen to have the same logical address, so traffic drop will be seen on these subinterfaces
Recommended Action Reload the Linecard. If the issue persists, please open a case with Cisco TAC for further assistance.


%ETH_SPA_GILA_FUGU-3-DATA_VER_MISMATCH : TCAM checkpointed data version [dec] differs from current version [dec].
Explanation During Minimal Disruptive Restart, version of checkpointed tcam data is found to be different from the data in the current version. The SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-HDR_VER_MISMATCH : TCAM checkpointed header version [dec] differs from current version [dec].
Explanation During Minimal Disruptive Restart, version of checkpointed tcam header is found to be different from the header in the current version. The SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-HDR_PARAMS_MISMATCH : TCAM checkpointed header values differs from values in current version.
Explanation During Minimal Disruptive Restart, values of fields in the checkpointed tcam header is found to be differnt from the values in the current version of IOS. The SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-ELT_NOT_IN_CUR_VER : The element at address [dec] in [chars] tcam is found missing during Minimal Disruptive Restart reconcilation.
Explanation During the reconcilation phase of Minimumal Disruptive Restart, an element was found to be present in the old IOS but not present in the new IOS image. This indicates that the config for this element was not played down from the RP during config-replay. This is an error condition, and the SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance


%ETH_SPA_GILA_FUGU-6-ELT_IS_NEW : The element at address [dec] in [chars] tcam is found to be new during Minimal Disruptive Restart reconcilation.
Explanation During the reconcilation phase of Minimumal Disruptive Restart, an element was found to be present in the new IOS but not present in the old IOS image. This is not an error condition, the SPA driver will program this new entry into the hardware.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance


%ETH_SPA_GILA_FUGU-3-HW_SW_MISMATCH : The hardware and software copies of the element at address [dec] in tcam [chars] do not match. This indicates reconcilation failure.
Explanation During reconcilation phase of Minimal Disruptive Restart, it is found that the software and hardware copies of an element in tcam do not match. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance


%ETH_SPA_GILA_FUGU-3-RECONFIG_FAILURE : Fugu reconfiguration failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu reconfiguration error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-TCAM_RECONFIG_FAILURE : Fugu TCAM reconfiguration failed for SPA in slot [int], bay [int] with error [dec], reconfig_needed [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu tcam reconfiguration error has occure. This indicates an error and SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-RESTART_FAILURE : Fugu restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_GILA_FUGU-3-TCAM_RESTART_FAILURE : TCAM restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu tcam restart has failed. This indicates an error and SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


ETH_SPA_MAC

%ETH_SPA_MAC-3-UNREC_ECC_ERR : [chars] : An unrecoverable ECC error occured in the MAC
Explanation An unrecoverable ECC error occured in the MAC.
Recommended Action Try to reload the SPA to recover from the failure. If the problem persist, contact Cisco Technical Assistance Center for assistance.


%ETH_SPA_MAC-3-SPI4_ERROR : [chars] : SPI4 Error occured in the MAC
Explanation SPI4 error occured in the MAC.
Recommended Action SPI error reported in the SPA. Try reseating the SPA if the error occurs multiple times. If you further need assistance please open a case with Cisco TAC at https://mycase.cloudapps.cisco.com/case


%ETH_SPA_MAC-3-SPI4_SINK_INIT_ERR : [chars] : Marvel spi4.1 sink init failed PL410 global status <lock> not set
Explanation An internal SPI4 error occurred in the SPA.
Recommended Action If the issue persists, return the SPA using the RMA process.


%ETH_SPA_MAC-3-RECONFIG_FAILURE : MAC reconfiguration failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, a mac reconfiguration error has occured.This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_MAC-3-PHY_RECONFIG_FAILURE : PHY reconfiguration failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart. This indicates an error and the SPA will be reset as normal and impact traffic.
Explanation
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_MAC-3-RESTART_FAILURE : MAC restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, mac restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_MAC-3-PHY_RESTART_FAILURE : PHY restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, phy restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_MAC-6-INTR_BURST : Interrupts from [chars] have crossed burst limit of [dec] in [dec] msec for port [dec]/[dec]/[dec]
Explanation Interrupts that have crossed the burst limit are detected by the SPA.
Recommended Action Check the interface configuration and receive signal characteristics. Also verify the XFP transceiver and receive signal path. Re-enable the interface after corrective action.


%ETH_SPA_MAC-3-INTR_MAX_BURST : Bursts of interrupts from [chars] have crossed maximum limit [dec] for port [dec]/[dec]/[dec]
Explanation Burst of interrupts that have crossed the maximum limit are detected by the SPA.
Recommended Action Check the interface configuration and receive signal characteristics. Also verify the XFP transceiver and receive signal path. Re-enable the interface after corrective action.


ETH_SPA_SERDES

%ETH_SPA_SERDES-3-RECONFIG_FAILURE : Serdes reconfiguration failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, serdes reconfiguration error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


%ETH_SPA_SERDES-3-RESTART_FAILURE : Serdes restart failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, serdes restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.


EVENT

%EVENT-3-INSERT_FAILURE : Failed to insert [chars]
Explanation The event process failed to insert the newly created row in its linked list data structure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%EVENT-3-NULL_STRUCT : Null pointer to the [chars] structure
Explanation The process was woken up with an element, which had a null pointer to the test structure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%EVENT-3-NULL_ELEMENT : Null pointer in the watched queue for [chars] test
Explanation The process was woken up with an NULL element
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


EVENTLIB through FEC_ISSU

EVENTLIB

%EVENTLIB-3-CPUHOG : [chars]: [int]ms, Traceback=[chars]
Explanation This error occurs when a particular event consumes an unfair share of the CPU that may degrade overall system response time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software process event command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVENTLIB-3-RUNHOG : [chars]: [int]ms, Traceback=[chars]
Explanation This error occurs when a particular event consumes an overall unfair share of the CPU that may degrade overall system response time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software process event command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVENTLIB-3-TIMEHOG : [chars]: [int]ms, Traceback=[chars]
Explanation This error occurs when a particular event takes an unusually long time to complete. This may affect overall system response time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software process event command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVENTLIB-3-HISTSUMM : dispatch start: [int]ms elapsed time: [int]ms detected hog: [int] set count: [int]
Explanation This event summary is part of a CPUHOG or TIMEHOG error, providing diagnostic details useful to engineering. Save this summary message along with the HOG error.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.


%EVENTLIB-3-HISTELEM : elem[[int]] event: [chars] [chars] set: [int]ms unset: [int]ms hog check: [dec] caller: [IPV6 address] app-info: [chars]
Explanation This event element is part of a CPUHOG or TIMEHOG error, providing diagnostic details useful to engineering. Save all element messages along with the HOG error.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.


%EVENTLIB-3-EVFDREAD : Event notification read failed with err [chars]
Explanation This occurs when we fail to read a thread notify event
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.


EVENT_TRACE

%EVENT_TRACE-6-ENABLE : Trace already enabled.
Explanation Specified event trace has already been enabled
Recommended Action This is a debug message only. No action is required.


%EVENT_TRACE-3-SIZE_ELEM : Size of trace element = [dec] is greater than size = [dec] allowed
Explanation The size of the specified individual trace entry is greater than the allowed size.
Recommended Action Reduce the individual trace entry size so as not to exceed the max while initializing the event trace


%EVENT_TRACE-3-NUM_ELEM : Number of trace element = [dec] is greater than number = [dec] allowed
Explanation The number of trace entries exceed the allowed amount
Recommended Action Reduce the number of trace entries


%EVENT_TRACE-3-NO_MEM : Not enough memory for [dec] trace elements.
Explanation The system memory is insufficient for the number of trace elements specified.
Recommended Action Reduce the size of the event trace


%EVENT_TRACE-3-NO_FILENAME : Dump file not specified.
Explanation No filename has been specified as output for the event trace.
Recommended Action You must specify the trace dump filename. To specify the trace dump filename, enter the monitor event-trace comp dump-file filename command in global configuration mode


%EVENT_TRACE-3-SIZE_FILENAME : Trace filename size = [dec] greater than size = [dec] allowed
Explanation The length of the specified Event Trace filename exceeds the allowed.
Recommended Action Shorten the filename.


%EVENT_TRACE-3-OPEN_FILE : Couldn't open [chars]...
Explanation The Event Trace subsystem could not open a file for the specified event trace dump.
Recommended Action If a file by the same name already exists, rename the dump file or remove the existing file from the file system.


%EVENT_TRACE-3-WRITE_FILE : Error writing to file [chars]
Explanation Event trace is not able to write to the specified filesystem
Recommended Action The filesystem might not be available. Try changing the destination filesystem and dumping there. If none work, copy the error message exactly as it and call your Cisco technical support representative


%EVENT_TRACE-3-CLOSE_FILE : Error closing file [chars]
Explanation The Event Trace subsystem can not close the specified file
Recommended Action No action required. This will not affect system functionality


%EVENT_TRACE-6-NO_FORMATTER : [chars]: no formatter provided, binary dumping.
Explanation No formatter function was provided during the initialization of the specified event trace.
Recommended Action No action is required.


%EVENT_TRACE-3-RESIZE : Enable trace before resizing
Explanation The specified event trace must be enabled before resizing occurs.
Recommended Action Enable the specified event trace.


%EVENT_TRACE-3-OPEN : [chars]: Trace failed to open
Explanation Initialization of the specified event trace has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVENT_TRACE-3-CONTINUOUS : Enable trace before setting continuous display
Explanation The specified event trace must be enabled before continuous display could occurs.
Recommended Action Enable the specified event trace.


%EVENT_TRACE-3-NO_TRACE_NAME : Invalid trace name [chars]
Explanation There is no trace buffer configured by the name entered.
Recommended Action Check whether there is an event trace buffer configured by the name entered and then enter the correct trace buffer name.


%EVENT_TRACE-3-GROUP_ID : Duplicate registration of group-id [dec]
Explanation Software subsystem is trying to register a group id for event trace which has already been used by another subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


EVTMON_PROXY

%EVTMON_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVTMON_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVTMON_PROXY-4-PROXY_IPC_EVTMON_FEAT_UPDATE_FAILED : feature user failed to [chars] because of [chars]
Explanation Event monitor feature user failed to attach or detach.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVTMON_PROXY-4-PROXY_IPC_EVTMON_REC_UPDATE_FAILED : event record update failed
Explanation Event monitor failed to attach or detach event record.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


EVUTIL

%EVUTIL-6-PREREQUISITE : Preferred library is absent
Explanation Eventlib has detected that a preferred library is missing from the process.
Recommended Action This is an informational message.


%EVUTIL-3-PREREQUISITE_INIT : A preferred library has failed to initialize: [chars]
Explanation Eventlib has detected that a preferred library which provides infrastructure services has failed to fully initialize.
Recommended Action Review the process logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%EVUTIL-3-PERMISSION : Operation not permitted for pid [dec] tid [dec]
Explanation Eventlib has detected that a process has attempted to invoke an API that is listed as having a level of permission.
Recommended Action Review the process logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


EXTASSIGNER

%EXTASSIGNER-3-NOCB : Failed to find the skinnyCB
Explanation
Recommended Action


%EXTASSIGNER-3-NOACTPHONE : Failed to find the calling phone
Explanation
Recommended Action


%EXTASSIGNER-3-NOMEM : Failed to malloc
Explanation
Recommended Action


%EXTASSIGNER-3-ERRTAG : Invalid tag([dec])
Explanation
Recommended Action


%EXTASSIGNER-3-NULLPTR : Null pointer ([chars]:[dec])
Explanation
Recommended Action


%EXTASSIGNER-3-ERRSYNC : Failed to sync tag([dec]) to standby CME
Explanation
Recommended Action


%EXTASSIGNER-3-ERRSYNC2 : Failed to sync re-assign tag ([dec]) for [dec] to standby CME
Explanation
Recommended Action


%EXTASSIGNER-6-ASSIGNED : Extension assignment successful for phone:SEP[chars]. New pool([dec]). Old pool([dec]).
Explanation Successfully assigned the pool
Recommended Action No action is required.


%EXTASSIGNER-6-UNASSIGNED : Extension unassignment successful for phone:SEP[chars]. Unassigned pool([dec]).
Explanation Successfully unassigned the pool
Recommended Action No action is required.


EZMAN_CLIENT

%EZMAN_CLIENT-5-EZ_CLIENT_VLAN_FULL : TCAM Full VLAN is not Able to add
Explanation Rx Sync Failed for Interlaken, Status Timer Expired. So, Resetting the Rx Interlaken Core
Recommended Action No user action is required.


%EZMAN_CLIENT-3-OBJECT_FAIL : Failed to bringup [chars]. Failure reason is [chars]
Explanation Bringup of object(NP/Bay/Interface) has failed in EZMAN. This can be due to any hardware/software failures and can be a serious error
Recommended Action Restart the Linecard.


%EZMAN_CLIENT-3-ECC_SINGLE_BIT_ERROR : Single bit ECC error
Explanation ECC error observed on the NP device.Reset the NP Device.
Recommended Action This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced.


%EZMAN_CLIENT-2-ECC_DOUBLE_BIT_ERROR : Double bit ECC errors observed. MIP100 is going to be reloaded to recover
Explanation ECC error observed on the NP device.Reset the NP Device.
Recommended Action This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced.


EZMAN_INFRA

%EZMAN_INFRA-3-PLATFORM_ID_ERR : Invalid HW Part number([dec]) and HW Revision([dec])
Explanation HW Part number and revision read from the IDPROM are not showing up expected values which means the IDPROM is either corrupted or incorrectly programmed.
Recommended Action Possible Hardware issue. Change the hardware.


EZMAN_RM

%EZMAN_RM-3-SERDES_AUTOTUNE_FAIL : Serdes Autotune [chars] on lane [dec]
Explanation NP5 Serdes RX is unable to autotune to the peer device's TX. This is a physical layer issue between NP5 and peer device.
Recommended Action OIR the Host-card if possible.


FARM_DSPRM

%FARM_DSPRM-4-NOC5510WARN : dsp service dspfarm can not be configured for this card type.
Explanation There is C549 NM-HDV card configured for dspfarm service. Only one dspfarm card type is allowed.
Recommended Action If C5510 card type dspfarm is desired then remove C549 NM-HDV dspfarm service and reconfigure dspfarm service for this card.


%FARM_DSPRM-6-CALLDROPINFO : dspfarm active calls on this card dsp [dec] channel [dec] will be dropped.
Explanation The card has been removed. Dspfarm active calls on this card will be dropped.
Recommended Action No action is required.


%FARM_DSPRM-6-CARDREMOVEINFO : dspfarm card slot [dec] is removed.
Explanation dspfarm card type is remvoed from the slot.
Recommended Action No action is required.


%FARM_DSPRM-6-CARDINSERTINFO : dspfarm card slot [dec] is inserted.
Explanation dspfarm card type is inserted into the slot.
Recommended Action No action is required.


FEC_ISSU

%FEC_ISSU-3-INIT : FEC ISSU client initialization failed at [chars], error [chars]
Explanation FEC ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FEC_ISSU-3-TRANSFORM : FEC ISSU client [chars] transform failed, error [chars]
Explanation FEC ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message can not be applied on the standby unit. In both cases the FEC state will not be indentical with the active unit.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu session <client_id> and show issu negotiated version <session_id>)


%FEC_ISSU-3-MSG_NOT_OK : FEC ISSU client message [dec] is not compatible
Explanation FEC ISSU client received an incompatible message from the peer unit. Since the message is not compatible it can be processed by this unit
Recommended Action LOG_STD_SH_CMD_ACTION(show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%FEC_ISSU-3-MSG_SIZE : FEC ISSU client failed to get the message size for message [dec]
Explanation FEC ISSU client failed to calculate message size for the message specified. The OIR ISSU client will not be able to send message to the standby unit.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%FEC_ISSU-3-SESSION : FEC ISSU client [chars]
Explanation FEC ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%FEC_ISSU-3-SESSION_UNREGISTRY : FEC ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The FEC ISSU client failed to unregister session information.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%FEC_ISSU-3-SEND_FAILED : FEC ISSU client failed to send a negotiation message, error [dec]
Explanation FEC ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION(show logging and show checkpoint client)


%FEC_ISSU-3-BUFFER : FEC ISSU client failed to get buffer for message, error [dec]
Explanation FEC ISSU client failed to get buffer for building a negotiation message. Hence, it can send the negotiation message to the standby unit. When there is a problem in the negotiaiton the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION(show logging and show checkpoint client)


%FEC_ISSU-3-CAPABILITY : FEC ISSU client [chars]
Explanation FEC SWITCH ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch between the client capability between the active and standby unit.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%FEC_ISSU-3-POLICY : FEC ISSU client message type [dec] is [chars]
Explanation FEC ISSU client received an message type which it does not support. The policy is applied to make the session compatible.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu session <client_id>)


FED through FED_QOS_ERRMSG

FED

%FED-2-INIT_FAILED : Module [chars] failed initialization[chars]
Explanation The specified module failed initialization. The switch will reload.
Recommended Action No action is required


%FED-0-HWSTALL : ASIC [dec] CORE [dec] Packet Buffer Complex Stalled. Switch will be reloaded
Explanation The specified asic/core packet buffer complex stalled. This is a critical error. This switch will reload. If there is a redundant switch, switch over will happen
Recommended Action No action is required


FED_FNF_ERRMSG

%FED_FNF_ERRMSG-6-UNSUPPORTED : [chars] is unsupported
Explanation The requested configuration is not supported.
Recommended Action Please do not use the current configuration.


%FED_FNF_ERRMSG-6-NOTALLOWED : [chars] is not allowed.
Explanation The requested configuration is not allowed.
Recommended Action Please try to modify your configuration.


%FED_FNF_ERRMSG-3-WDAVCATTACHERROR : Unable to attach flow monitor or IP NBAR to interface [chars]. Flow monitor and IP NBAR are not allowed on the same interface.
Explanation The requested configuration is not allowed.
Recommended Action Please try to modify your configuration.


%FED_FNF_ERRMSG-3-SGTCATTACHERROR : Detach the existing [chars] before attaching [chars] to interface [chars]. These features cannot co-exist.
Explanation The requested configuration is not allowed.
Recommended Action Please try to modify your configuration.


%FED_FNF_ERRMSG-3-ATTACHERROR : Failed to attach flow monitor to interface [chars].
Explanation An error occurs when attaching the flow monitor to the interface.
Recommended Action Find out more about the error by using show mgmt-infra trace messages fed-fnf-config-error switch number command


%FED_FNF_ERRMSG-3-DETACHERROR : Failed to detach flow monitor from interface [chars]
Explanation Error occurs when detaching the flow monitor from the interface.
Recommended Action Find out more about the error by using show mgmt-infra trace messages fed-fnf-config-error switch number command


FED_IPC_MSG

%FED_IPC_MSG-5-FAST_RELOAD_COMPLETE : Fast reload operation complete
Explanation This is used to indicate that the fast reload is complete.
Recommended Action No action needed. This is not an error.


FED_L2M_ERRMSG

%FED_L2M_ERRMSG-3-RSRC_ERR : Failed to allocate hardware resource for [chars]
Explanation Hardware resource allocation has failed and the entry will not be programmed.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


FED_L3M_ERRMSG

%FED_L3M_ERRMSG-3-RSRC_ERR : Failed to allocate hardware resource for [chars] - rc:[chars]
Explanation Hardware resource allocation has failed and the entry will not be programmed.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


FED_L3_ERRMSG

%FED_L3_ERRMSG-3-ecr_err : Platform unicast routing ecr module encountered [chars] error in FED
Explanation An error occurred in platform ecr code.
Recommended Action Find out more about this error by using the show platform ipunicast ecr commands.


%FED_L3_ERRMSG-3-fib_err : Platform unicast routing fib module encountered [chars] error in FED
Explanation An error occurred in platform fib code.
Recommended Action Find out more about this error by using the show platform ipunicast route commands.


%FED_L3_ERRMSG-3-pbr_err : Platform unicast routing pbr module encountered [chars] error in FED
Explanation An error occurred in platform pbr code.
Recommended Action Find out more about this error by using the show platform ipunicast policy commands


%FED_L3_ERRMSG-3-wccp_err : Platform unicast routing wccp module encountered [chars] error in FED
Explanation An error occurred in platform wccp code.
Recommended Action Find out more about this error by using the show platform ipunicast wccp commands.


%FED_L3_ERRMSG-3-RSRC_ERR : Failed to allocate hardware resource for [chars] - rc:[dec]
Explanation Hardware resource allocation has failed and the entry will not be programmed.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_L3_ERRMSG-3-mpls_recursive_label_err : Unsupported recursive MPLS label for local_label [int] [chars]
Explanation The specified MPLS local label is recursive and is not yet supported.
Recommended Action Find out more about this error by using the show commands for the specified local_label and modify the config using LDP filters to remove recursive labels.


%FED_L3_ERRMSG-3-UNSUPPORTED_CMD : [chars] is not supported on the interface [chars]
Explanation The specified cli is not yet supported.
Recommended Action Find out more about this unsupported feature from the release documents and remove the command from the interface config mode


%FED_L3_ERRMSG-3-MAX_TUNNEL : The maximum number of Tunnel has been reached
Explanation Hardware resource allocation has failed and the entry will not be programmed.
Recommended Action New Tunnels will not be working as expected.


%FED_L3_ERRMSG-3-mpls_ecmp_modify_err : MPLS Load Balance modify is not supported [int]
Explanation Modification of an ECMP object with MPLS Adjacencies is not supported yet. It is not an expected event
Recommended Action Find out more about this error by using the show commands for the specified object and identify the possible trigger for the modify.


%FED_L3_ERRMSG-3-mpls_pause_create : Critical limit reached for MPLS [chars] resource. Create paused
Explanation The specified MPLS local label is recursive and is not yet supported.
Recommended Action Find out more about this error by using the show commands for the specified local_label and modify the config using LDP filters to remove recursive labels.


%FED_L3_ERRMSG-3-mpls_resume_create : Resuming create for MPLS [chars] resource.
Explanation The specified MPLS local label is recursive and is not yet supported.
Recommended Action Find out more about this error by using the show commands for the specified local_label and modify the config using LDP filters to remove recursive labels.


%FED_L3_ERRMSG-3-mpls_out_of_resource : Out of resource for MPLS [chars]. Failed to program [chars] in hardware
Explanation Running out of Hardware resource to support the scale of this MPLS feature.
Recommended Action Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls summary, tcam utiliztion and resource utilization


%FED_L3_ERRMSG-3-mpls_unsupported_feature : Unsupported feature. Failed to program [chars] in hardware
Explanation The feature is not yet supported.
Recommended Action Find out more about this unsupported feature from the release documents and remove the command from the interface config mode


%FED_L3_ERRMSG-3-intf_err : [chars] interface [chars]
Explanation Error in HW programming for Interface.
Recommended Action Find out more about this failure from ifm show outputs and debugs for the interface


FED_PM

%FED_PM-3-HW_ERROR : Port Manager error -[chars] hardware update failed.
Explanation An error occurred in Port Manager code.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_PM-3-RESRC_ERROR : Port Manager error -[chars] resource access failed.
Explanation An error occurred in Port Manager code.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_PM-3-FRU_TRANSCEIVER_TIMEOUT : Transceiver event handling for interface [chars] timed out. Remove and re-insert the FRU module containing this interface to recover.
Explanation Than handling onf a transceiver event took too long for the given interface.
Recommended Action Remove and re-insert the FRU module containing this interface. The system should recover from this failure condition after that.


%FED_PM-3-FRU_SWITCH_TIMEOUT : Transeiver update timed out. Remove and re-insert all FRUs in this switch to recover.
Explanation An FRU update event took too long to process on this switch. The FRUs on this switch may not be recoginized or function properly after this.
Recommended Action Remove and re-insert all FRUs on this switch. The system should recognize and process them correctly after that.


%FED_PM-3-FRU_TIMEOUT : FRU module [dec] bringup timed out. Remove and re-insert it to recover.
Explanation The given FRU module in the switch in question could not be recognized because it took too long do so.
Recommended Action Remove and re-insert the specified FRU module. The system should recognize it correctly after that.


FED_PTP_ERRMSG

%FED_PTP_ERRMSG-6-UNSUPPORTED : [chars] is unsupported
Explanation The requested configuration is not supported.
Recommended Action Please do not use the current configuration.


%FED_PTP_ERRMSG-6-NOTALLOWED : [chars] is not allowed.
Explanation The requested configuration is not allowed.
Recommended Action Please try to modify your configuration.


%FED_PTP_ERRMSG-3-ATTACHERROR : Failed to run PTP [chars].
Explanation An error occurs when running PTP.
Recommended Action Find out more about the error by using show mgmt-infra trace messages fed-ptp-config-error switch number command


%FED_PTP_ERRMSG-3-DETACHERROR : Failed to run PTP [chars]
Explanation Error occurs when running PTP.
Recommended Action Find out more about the error by using show mgmt-infra trace messages fed-ptp-config-error switch number command


FED_PUNJECT

%FED_PUNJECT-6-PKT_CAPTURE_FULL : Punject pkt capture buffer is full. Use show command to display the punted packets.
Explanation All the available punt capture buffers have been written with punted packets.
Recommended Action No action is needed.


FED_QOS_ERRMSG

%FED_QOS_ERRMSG-3-TABLEMAP_INIT_ERROR : Failed to initialize [chars].
Explanation An error occurred during table-map initialization.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-3-TABLEMAP_INGRESS_HW_ERROR : Failed to [chars] for [chars]: code [dec].
Explanation An error occurred when programming ingress table-map to hardware.
Recommended Action failed actionFind out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-3-TABLEMAP_EGRESS_HW_ERROR : Failed to [chars] for [chars]: code [dec].
Explanation An error occurred when programming egress table-map to hardware.
Recommended Action failed actionFind out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-4-TABLEMAP_OVERFLOW : Failed to attach [chars]. No more table-maps are available.
Explanation The system supports up to 16 table-maps per direction. This limit has been reached.
Recommended Action failed actionUnconfigure some of the table-maps to make the resource available.


%FED_QOS_ERRMSG-3-LABEL_2_QUEUE_MAPPING_HW_ERROR : Failed to [chars] for [chars]: code [dec].
Explanation An error occurred in programming label to queue map.
Recommended Action failed actionFind out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-4-LABEL_2_QUEUE_MAPPING_OVERFLOW : Failed to [chars]. No more queue-maps are available.
Explanation The system supports up to 8 queue-maps. This limit has been reached.
Recommended Action failed actionUnconfigure some of the queuing policies to make the resource available.


%FED_QOS_ERRMSG-3-QUEUE_BUFFER_HW_ERROR : Failed to [chars] for [chars]: code [dec].
Explanation An error occurred when programming the queue buffer.
Recommended Action failed actionFind out more about the error by using the show tech-support priveleged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-3-QUEUE_SCHEDULER_HW_ERROR : Failed to [chars] for [chars]: code [dec].
Explanation An error occurred when programming the queue scheduler.
Recommended Action failed actionFind out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-3-AFD_QUEUE_HW_ERROR : Failed to program AFD [chars] virtual queue for [chars].
Explanation An error occurred in programming the Approximate Fair Dropping virtual queue.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-4-TCAM_OVERFLOW : Failed to program TCAM for policy-map [chars] on [chars].
Explanation The TCAM resources are exhausted.
Recommended Action Unconfigure features to make TCAM resources available.


%FED_QOS_ERRMSG-4-APPLICATION_ID_OVERFLOW : Failed to allocate application ID for policy-map [chars] on [chars].
Explanation The application IDs are exhausted.
Recommended Action Reduce the number of applications to make application ID available.


%FED_QOS_ERRMSG-4-POLICER_OVERFLOW : Failed to [chars] for [chars]. No policer resource is available.
Explanation The policer resource limit has been reached.
Recommended Action failed actionUnconfigure some policers to make the resource available.


%FED_QOS_ERRMSG-4-NETFLOW_TABLE_OVERFLOW : Failed to program netflow entries for policy-map [chars] for client mac:[chars] iifid:[hex]. No netflow resource is available.
Explanation The netflow resources are exhausted.
Recommended Action Unconfigure features to make the netflow resource available.


%FED_QOS_ERRMSG-3-NETFLOW_TABLE_HW_ERROR : Failed to program netflow entries for policy-map [chars] for client mac:[chars] iifid:[hex]. code:[dec].
Explanation An error occurred in programming netflow table.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-3-AFD_POLICER_HW_ERROR : Failed to [chars] for [chars].
Explanation An error occurred in programming the Approximate Fair Dropping policer.
Recommended Action failed actionFind out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-3-POLICER_HW_ERROR : Failed to [chars] for [chars]: code [dec].
Explanation An error occurred in programming the policer.
Recommended Action failed actionFind out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-4-POLICER_MAP_TABLE_OVERFLOW : Failed to [chars] for [chars]. No more policer map tables are available.
Explanation The ASIC supports up to 64 policer map tables. This limit has been reached.
Recommended Action failed actionUnconfigure some policer maps to make the resource available.


%FED_QOS_ERRMSG-3-POLICER_MAP_HW_ERROR : Failed to [chars] for [chars]: code [dec].
Explanation An error occurred in programming the policer map.
Recommended Action failed actionFind out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%FED_QOS_ERRMSG-4-OUTPUT_CLIENT_POLICY_ERROR : Unsupported output client policy([chars]) - range operators.
Explanation Unsupported policy.
Recommended Action Range operators are not supported in client output policy


%FED_QOS_ERRMSG-4-OUTPUT_ACS_CLIENT_POLICY_ERROR : Unsupported output client policy([chars]).
Explanation Unsupported policy.
Recommended Action Unsupported client output policy


%FED_QOS_ERRMSG-4-CONFIGURE_PORT_TYPE_HW_ERROR : Failed to configure port [chars] as [chars] port in hardare. rc:[dec].
Explanation The port could not be configured in hardware
Recommended Action Try to shutdown the port and then unshut the port


FED_SRVO_ERRMSG through FLEXDSPRM

FED_SRVO_ERRMSG

%FED_SRVO_ERRMSG-6-UNSUPPORTED : [chars] is unsupported
Explanation The requested configuration is not supported.
Recommended Action Please do not use the current configuration.


%FED_SRVO_ERRMSG-6-NOTALLOWED : [chars] is not allowed.
Explanation The requested configuration is not allowed.
Recommended Action Please try to modify your configuration.


%FED_SRVO_ERRMSG-3-ATTACHERROR : Failed to run SRVO [chars].
Explanation An error occurs when running SRVO.
Recommended Action Find out more about the error by using show mgmt-infra trace messages fed-srvo-config-error switch number command


%FED_SRVO_ERRMSG-3-DETACHERROR : Failed to run SRVO [chars]
Explanation Error occurs when running SRVO.
Recommended Action Find out more about the error by using show mgmt-infra trace messages fed-srvo-config-error switch number command


FED_STP_ERRMSG

%FED_STP_ERRMSG-3-MAX_INSTANCES : The maximum number of STP instances has been reached:[dec]
Explanation The maximum number of STP instances that can be programmed has been reached.
Recommended Action Delete or resolve loops manually for the vlans created further.


FED_VLAN_TRANSLATE_ERRMSG

%FED_VLAN_TRANSLATE_ERRMSG-6-UNSUPPORTED : [chars] is unsupported
Explanation The requested configuration is not supported.
Recommended Action Please do not use the current configuration.


%FED_VLAN_TRANSLATE_ERRMSG-6-NOTALLOWED : [chars] is not allowed.
Explanation The requested configuration is not allowed.
Recommended Action Please try to modify your configuration.


%FED_VLAN_TRANSLATE_ERRMSG-3-ATTACHERROR : Failed to run VLAN_TRANSLATE [chars].
Explanation An error occurs when running VLAN_TRANSLATE.
Recommended Action Find out more about the error by using show mgmt-infra \ trace messages fed-vlan_translate-config-error switch number \ command


%FED_VLAN_TRANSLATE_ERRMSG-3-DETACHERROR : Failed to run VLAN_TRANSLATE [chars]
Explanation Error occurs when running VLAN_TRANSLATE.
Recommended Action Find out more about the error by using show mgmt-infra \ trace messages fed-vlan_translate-config-error \ switch number command


FFP_HW_IRQ

%FFP_HW_IRQ-3-NON_FATAL_INTERRUPT : [int] errors in the last [int] seconds, MSGDEF_LIMIT_MEDIUM
Explanation Accumulation of Cavium hardware-generated error
Recommended Action LOG_STD_ACTION


%FFP_HW_IRQ-3-TOO_MANY_NON_FATAL_INTERRUPTS :
Explanation Aborting due to too many Cavium hardware-generated errors
Recommended Action LOG_STD_ACTION


FIB

%FIB-2-IDBQINIT : Error initializing CEF IDB queue
Explanation Initialization of the CEF IDB queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%FIB-2-LINECARDINIT : Error initializing CEF Linecard queue
Explanation Initialization of the CEF linecard queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%FIB-2-XDRINIT : Error initializing CEF xdr chunks
Explanation Initialization of the CEF xdr chunks could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%FIB-2-FIBFEATSESINIT : Error initializing CEF repop feature session queue
Explanation Initialization of a CEF feature session queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%FIB-2-DFIBSWITCH : Error trying to turn on Distributed CEF without CEF on
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-3-FIBXDRLEN : Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[dec]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-3-FIBBADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at [hex]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-4-FIBSPECIALPREFIX : Invalid Special Prefix Type. Type [dec]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-4-FIBEVENT : Invalid event. Type [chars], event [dec]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-4-FIBXDRINV : Invalid format. [chars] [chars] ([dec])
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-2-FIBDISABLE : Fatal error, slot [chars]: [chars]
Explanation An internal software error has occurred because of an IPC problem between the LC and the RP. CEF switching has been disabled on the specified slot.
Recommended Action Enter the clear cef linecard [slot no] command, then check the status of the line card by entering the show cef linecard command. If the status shows that the line card is still disabled, disable and re-enable DCEF and check the status of the line card again. LOG_STD_RECUR_ACTION


%FIB-3-INVALIDSTATE : Slot [chars] in invalid transition from [chars] to [chars]
Explanation An internal software error ocurred. Linecard is in incorrect state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-4-FIBLCTUNSEQ : [chars] Error Initializing/Updating Linecard Tunnel Configuration
Explanation Configuration of a Tunnel on this linecard may not have been successful because of an internal software error.
Recommended Action Reconfigure the Tunnel concerned. If problem persists copy the message exactly as it appears, and report it to your technical support representative.


%FIB-6-FIBLCTUNDELSEQ : Update received on a linecard for a deleted tunnel([chars]) - ignored.
Explanation An update was received on a linecard for a tunnel that has already been deleted and the update was ignored.
Recommended Action No action is required.


%FIB-4-FIBCBLK : Missing cef table for tableid [dec] during [chars] event
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-2-FIBDOWN : CEF has been disabled due to a low memory condition. It can be re-enabled by configuring ip cef [distributed]
Explanation CEF was disabled because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade the RP so that it has more DRAM.


%FIB-2-FIB_OVERLENGTH_XDR : Overlength CEF XDR message - len [dec] > [dec] from [chars]
Explanation An internal software error occurred preventing the sending of an CEF XDR message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-3-FIBSBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified CEF subblock data structure could not be accomplished.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-3-FIBSBNOFN : Missing [chars] subblock [chars] function for [chars]
Explanation Functions for distributing this subblock are missing from the image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-3-FIBPENDINGLIST : Error queueing interface [chars] to CEF pending event list.
Explanation Queueing an interface to the CEF pending up event list failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-3-MAC_ACCT : [chars]: [chars]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FIB-3-PREC_ACCT : [chars]: [chars]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FILESYS

%FILESYS-5-DEV : PCMCIA flash card [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action No action is required.


%FILESYS-5-IFLASH : Internal Flash [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action No action is required.


%FILESYS-5-UNKNDEV : Unknown device [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action No action is required.


%FILESYS-3-FLASH : [chars] [chars] error [dec]
Explanation A file system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FILESYS-4-RCSF : [chars] ([dec]) <[chars]>
Explanation A Running config sync file error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FILESYS-5-MISMATCH : [chars] device programming algorithm mismatch detected, reformat is recommended
Explanation The flash device programming algorithm written to the device when the flash was formatted is different from what the current running software detected. A reformat of the flash device will solve the problem.
Recommended Action No action is required.


%FILESYS-3-IPC : [chars] [chars]: IPC error [[chars]]
Explanation RFS operation failed due to an IPC error.
Recommended Action


%FILESYS-5-CFLASH : Compact flash card [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action


%FILESYS-4-CLPDINT : Management interrupts are [chars] for pcmcia device in socket [dec]. [chars]
Explanation A faulty PCMCIA flash device might be generating spurious insert or remove interrupts continiously. The pcmcia controller will be set temporarily to disable interrupt generation and will be reenabled after a few seconds. This is to avoid storming CPU with spurious interrupts. If the (alternate) pcmcia device is inserted while the interrupts are disabled, sometimes the device may not be readable. You have to remove and reinsert the pcmcia device once again.
Recommended Action Replace the pcmcia flash device with an alternate one


FILESYS_RFS

%FILESYS_RFS-3-IPC : [chars] [chars]: msg_type [[dec]] sub_type [[dec]]: IPC error [[chars]]
Explanation RFS operation failed due to an IPC error.
Recommended Action


%FILESYS_RFS-4-RFS_REQUEST_TIMEOUT : Timeout has occurred while executing the RFS request on file [chars] [[dec]].
Explanation A RFS request is sent to server from the client. While executing the request on the server side, timeout has occurred at the client side.
Recommended Action No action is required.


FILTER_BINARY_NOTIFICATION

%FILTER_BINARY_NOTIFICATION-5-MERGE_COMPLETED : Merged logs generation completed.
Explanation Notification to user that merged logs are generated
Recommended Action Go to bootflash and view the merged logs


FLASH_CHECK

%FLASH_CHECK-3-DISK_QUOTA : Flash disk quota exceeded [free space is [dec] kB] - Please clean up files on bootflash.
Explanation The remaining free space on the flash disk is below the recommended threshold of at least 30 percent of the installed RP memory. This limits the system from core files necessary to root cause critical system faults.
Recommended Action Please remove unneeded files from bootflash: device. Any core files under the bootflash:/core directory should be reported and then deleted.


FLEXDSPRM

%FLEXDSPRM-5-CB_UPDOWN : Channel Bank [chars] state is [chars]
Explanation Channel Bank status has been changed
Recommended Action See if the voice ports in the channel bank are UP


%FLEXDSPRM-5-OUT_OF_RESOURCES : [chars]
Explanation Flex DSPRM temporarily fail to allocate a DSP for this call. A oversubscription has happened and the current free DSP MIPS/Credits are not sufficient to admit a new call.
Recommended Action Check availability of router DSP resource and DSP sharing configurations


%FLEXDSPRM-6-DSP_USAGE : DSP [chars] usage has reached [dec]%%
Explanation Usage of DSP resources has reached a certain percentage.
Recommended Action Examine whether or not enough DSP resources are reserved.


%FLEXDSPRM-3-TDM_CONNECT : failed to connect voice-port ([dec]/[dec]/[dec]) to dsp_channel([dec]/[dec]/[dec])
Explanation TDM connection between Analog/VWIC and the DSP has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FLEXDSPRM-5-TDM_SLOT : voice channel is being shared from slot [dec]. Configure network-clock-participate slot [dec]
Explanation Configure network-clock-participate slot for sharing DSPs
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FLEXDSPRM-3-UNSUPPORTED_CODEC : codec [chars] is not supported on dsp [dec]/[dec]
Explanation Call failed due to the dsp does not support the codec.
Recommended Action Check dsp capability and make the call on supported dsp


FLEX_DNLD through FMANRP_MPLS

FLEX_DNLD

%FLEX_DNLD-1-NOPCIMEMORY : VPM ([dec]/[dec]), PCI memory unavailable.
Explanation The router or access server could not allocate memory for the descriptors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%FLEX_DNLD-1-INCORRECT_DSP_ID : AIM VOICE at slot [dec] receives data from incorrect DSP-ID [dec].
Explanation The DSP ID provided by FPGA for download is not valid.
Recommended Action Call your technical support representative for assistance.


%FLEX_DNLD-3-ERROR_FIRMWARE_DNLD : DSP firmware download fails for slot [dec] dsp_id [dec]
Explanation Error initializing the DSP with the application firmware.
Recommended Action Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance.


%FLEX_DNLD-3-NO_FIRMWARE_DNLD : No DSP firmware download invoked for slot [dec], no DSPs on the card
Explanation No DSP on the card.
Recommended Action Plug in DSP on the Network Module


%FLEX_DNLD-1-TOOBIG : [chars], packet(size [dec]) too big.
Explanation A packet greater than the 264 bytes received on this interface.
Recommended Action The system should recover. No action is required. If the problem reccurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.


%FLEX_DNLD-3-ERROR_ANALYZE : Error analyzing the device in slot [dec].
Explanation The Port module in this slot could not be recognized.
Recommended Action Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance.


%FLEX_DNLD-1-NO_RING_DESCRIPTORS : No more ring descriptors available on slot [dec] dsp [dec].
Explanation The dspfw dnld driver cannot queue messages upto the egress queue for FPGA to transmit.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Reset the DSP's on this port module.


FLOWSPEC

%FLOWSPEC-3-CLIENT_ALLOC : Failed to alloc ([int] hdr) + ([int] items)*([int] bytes) = ([int] total bytes) for '[chars]', errno [dec]:[chars].
Explanation The FlowSpec client infra has failed to allocate memory. This may be due to lowmemory conditions on this particular RP/LC, or this client may be using morememory than it is allowed.
Recommended Action Reduce system scale.


%FLOWSPEC-3-CLIENT_ENABLE : Failed to initialize '[chars]' when enabling FlowSpec feature, [hex]:[chars].
Explanation When 'flowspec' configuration is first added, the FlowSpec client infrainitializes in client processes, namely BGP. Something has failed in thisprocess any may prevent FlowSpec from functioning.
Recommended Action Remove and re-add 'flowspec' configuration. If the problem repeats, contactCisco support.


%FLOWSPEC-3-MGR_ALLOC : Failed to alloc ([int] hdr) + ([int] items)*([int] bytes) = ([int] total bytes) for '[chars]', errno [dec]:[chars].
Explanation The FlowSpec Manager process (flowspec_mgr) has failed to allocate memory. This may be due to low memory conditions on this particular RP/LC, or this process may be using more memory than it is allowed.
Recommended Action Reduce system scale.


%FLOWSPEC-3-MGR_CLASS_CREATE : Failed to create inline-class for flow [chars] with actions [chars] in table [chars], overall:[hex]:[chars], [hex]:[chars].
Explanation FlowSpec failed to create the inline-class representing the flow in the table (VRF+AFI). This will prevent the flow from functioning in this table.
Recommended Action Unconfigure and reconfigure local-install for this table. FlowSpec can further be entirely unconfigured and reconfigured. If the problem persists, contact Cisco support.


%FLOWSPEC-3-MGR_EVM : FlowSpec Manager failed to receive event from [chars] EVM, [hex]:[chars].
Explanation The event processing infra has returned a fatal error.
Recommended Action Allow FlowSpec Manager to restart. If the problem persists, contact Cisco support.


%FLOWSPEC-3-MGR_GEN_ERR : FlowSpec internal error: [chars], [hex]:[chars].
Explanation An internal software error occurred.
Recommended Action *SUPPORT*


%FLOWSPEC-3-MGR_INIT : FlowSpec Manager failed to initialize '[chars]', [hex]:[chars].
Explanation When 'flowspec' configuration is first added, the FlowSpec Manager (flowspec_mgr) process starts and initializes. Something has failed in this proceedure and may prevent FlowSpec from functioning.
Recommended Action Allow FlowSpec Manager to restart. You can further remove and re-add 'flowspec' configuration. If the problem persists, contact Cisco support.


%FLOWSPEC-3-MGR_LOCK : FlowSpec Manager lock operation [chars] failed, error %#d.
Explanation An internal lock has failed.
Recommended Action FlowSpec manager may be restarted, if it doesn't restart automatically. If the problem persists, contact Cisco support.


%FLOWSPEC-3-MGR_POLICY_ATTACH : Failed to attach policy-map [chars] for table [chars], [hex]:[chars].
Explanation FlowSpec failed to attach the policy-map for this table (VRF+AFI). This will prevent flows from functioning on this table.
Recommended Action Unconfigure and reconfigure local-install for this table. FlowSpec can further be entirely unconfigured and reconfigured. If the problem persists, contact Cisco support.


%FLOWSPEC-3-MGR_POLICY_CREATE : Failed to create policy-map [chars] for table [chars], [hex]:[chars].
Explanation FlowSpec failed to create the policy-map for this table (VRF+AFI). This will prevent flows from functioning on this table.
Recommended Action Unconfigure and reconfigure local-install for this table. FlowSpec can further be entirely unconfigured and reconfigured. If the problem persists, contact Cisco support.


%FLOWSPEC-3-MGR_POLICY_DELETE : Failed to delete policy-map [chars] handle %#llx for table [chars], [hex]:[chars].
Explanation FlowSpec failed to delete the policy-map for this table (VRF+AFI). This may leave the system in an inconsistent state for this table and prevent FlowSpec from recreating the table.
Recommended Action Unconfigure and reconfigure local-install for this table. FlowSpec can further be entirely unconfigured and reconfigured. If the problem persists, contact Cisco support.


FMANFP

%FMANFP-6-IPACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPV6ACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPV6ACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPV6ACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-FMANACLLOGMISSMSG : access-list logging datapath rate-limited or missed [int] packet[chars]
Explanation Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available.
Recommended Action No action is required.


%FMANFP-6-CRYPTO_DEVICE_REQUEST_COMPLETE : Crypto-device is ready to process packets
Explanation Crypto-device is load with new core based on user request. Now it is ready to process packets
Recommended Action No action is required.


%FMANFP-3-CRYPTO_DEVICE_REQUEST_FAILED : Crypto-device is busy processing last request. This request will be discarded
Explanation Crypto-device is still processing previous reload reqeust or still processing crypto feature packets. New request will not be applied
Recommended Action No action is required.


%FMANFP-6-CRYPTO_DEVICE_NOT_PRESENT : Hardware crypto-device is not present. Request aborted
Explanation Hardware crypto-device is not present on the system. User request doesn't apply or be executed. This may not be an error.
Recommended Action No action is required.


%FMANFP-3-LICENSE_THPUT_INVALID : Invalid throughput [int]kbps
Explanation The throughput value is invalid. The forwarding engine will not operate at the throughput value.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.


%FMANFP-3-CRYPTO_LICENSE_THPUT_THRESHOLD_EXCEED : Average crypto throughput rate exceeded [dec] percent of licensed crypto bandwidth of [int] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds
Explanation To monitor crypto throughput and, to generate notification/warning if the average throuput utilization over a longer time are approaching or exceeding the cypro licensed bandwidth
Recommended Action No action is required.


%FMANFP-3-CRYPTO_LICENSE_THPUT_MAX_APPROACHED : Average crypto throughput rate approached the licensed crypto bandwidth of [int] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds
Explanation To monitor crypto throughput and, to generate notification/warning if the average throuput utilization over a longer time are approaching or exceeding the cypro licensed bandwidth
Recommended Action No action is required.


%FMANFP-6-IPACCESSLOGSGP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' src-port='[int]' dest-ip='[chars]' dest-port='[int]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPACCESSLOGSGNP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[int]' src-ip='[chars]' dest-ip='[chars]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPACCESSLOGSGDP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' dest-ip='[chars]' type='[int]' code='[int]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPV6ACCESSLOGSGP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' src-port='[int]' dest-ip='[chars]' dest-port='[int]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPV6ACCESSLOGSGNP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[int]' src-ip='[chars]' dest-ip='[chars]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%FMANFP-6-IPV6ACCESSLOGSGDP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' dest-ip='[chars]' type='[int]' code='[int]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


FMANRP

%FMANRP-4-INVALID_CCE_POSITION : Invalid position '[dec]' prevented [chars]
Explanation A messaging error has occurred during service-policy modification and the configuration could not be downloaded properly
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.


%FMANRP-3-OBJ_DWNLD_TO_FP_FAILED : [chars] download to FP failed
Explanation An object has failed to download to the forwarding processor (FP)
Recommended Action Examine the process logs to identify the cause for object download failure


FMANRP_ACL

%FMANRP_ACL-4-NOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-NOSB : Subblock on interface [chars] ([hex]) is null
Explanation An unexpected condition has occurred which is due to the absence of a subblock structure on interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-NOACL : ACL is null
Explanation An unexpected condition has occurred which is due to the absence of an ACL structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-NOV4ACE : v4 ACE is null
Explanation An unexpected condition has occurred which is due to the absence of an v4 ACE structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-NOV6ACE : v6 ACE is null
Explanation An unexpected condition has occurred which is due to the absence of an v6 ACE structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipv6 access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-NOMACACE : mac ACE is null
Explanation An unexpected condition has occurred which is due to the absence of an mac ACE structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-INVALIDV4ACETYPE : v4 ACE type is invalid
Explanation An unexpected condition has occurred which is due to the type of v4 ACE created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-INVALIDV6OP : Operation is invalid
Explanation An unexpected condition has occurred which is due to the operation performed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipv6 access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-UPDV4STATSERR : Update v4 ACL statistics error
Explanation An unexpected condition has occurred when updating v4 ACL statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-UPDV6STATSERR : Update v6 ACL statistics error
Explanation An unexpected condition has occurred when updating v6 ACL statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipv6 access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-UPDMACSTATSERR : Update mac ACL statistics error
Explanation An unexpected condition has occurred when updating mac ACL statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show access-list command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-TMPLACLINITERR : Template ACL initialization error
Explanation An unexpected condition has occurred on template ACL initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show memory command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-TMPLACLNOMEMERR : Template ACL no memory error
Explanation An unexpected condition has occurred on template ACL processing
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show memory command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-4-TMPLACLDISABLEERR : Not enough resources to disable template ACL
Explanation Not enough resurces to store individual ACLs
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-list template summary command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_ACL-3-EXPOGACLLIMITERR : Expanded OGACL ([chars]) size ([dec]) exceeded MAX ACL limit ([dec])
Explanation Expanded OGACL size exceeded the maximum ACL limit. Command rejected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the Reduce # of ACEs in the ACL command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_DPSS

%FMANRP_DPSS-3-DPSSFOIPCALLOC : Failed to alloc IPC buffer for dpss feature object [hex] config message
Explanation This operation to allocate IPC buffer for dpss feature object configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSFOTDLMSGMARSHAL : Failed to copy dpss feature object config message to IPC buffer for fo_hdl [hex]
Explanation This operation to build a TDL message for dpss feature object configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSFOIOSDENQUEUE : Failed to enqueue dpss feature object [hex] config message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSFOTDLCREATE : Failed to create tdl msg for dpss feature object [hex] config message
Explanation This operation to create an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSFOTDLSET : Failed to set tdl msg detail for dpss feature object [hex] config message
Explanation This operation to set an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSGLOBALTDLCREATE : Failed to create tdl msg for dpss global config message
Explanation This operation to create an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSGLOBALTDLSET : Failed to set tdl msg detail for dpss global config message
Explanation This operation to set an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSGLOBALIPCALLOC : Failed to alloc IPC buffer for dpss global config message
Explanation This operation to allocate IPC buffer for dpss global configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSGLOBALTDLMSGMARSHAL : Failed to copy dpss global config message to IPC buffer
Explanation This operation to build a TDL message for dpss global configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_DPSS-3-DPSSGLOBALIOSDENQUEUE : Failed to enqueue dpss global config message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_EVPN

%FMANRP_EVPN-3-UNSPOP : Unsupport operation
Explanation An unexpected operation is get during EVPN configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_IPSEC

%FMANRP_IPSEC-6-HAPI_PCP_NACK : [chars]: PCP NACK (trans [hex], opcode [hex], errcode [hex]): crypto hardware configuration may be out of sync.
Explanation A failure has occured during security policy downloading in crypto hardware. The command is rejected.
Recommended Action The configuration may be ignorable or recovered automatically in crypto hardware. The session may still be functional but less than optimal performance. If you determine that the system is adversely affected then Embedded Services Processor (ESP) tracelog should be collected. LOG_STD_ACTION


%FMANRP_IPSEC-3-HAPI_PCP_UNEXP_REPLY : [chars]: PCP (trans [hex], opcode [hex]): unexpected reply from crypto hardware.
Explanation An unexpected internal software error. Engineering must be reported and investigate this occurrence.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.


FMANRP_MFR

%FMANRP_MFR-3-TDLFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process ([chars])
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_MFR-3-BNDLFAIL : Unable to [chars] bundle [chars]
Explanation An unexpected condition has occurred at Bundle configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_MFR-3-BLFAIL : Unable to [chars] link [chars] [chars]
Explanation An unexpected condition has occurred at Bundle link configuration %s
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_MFR-3-BLCFGFAIL : Unable to [chars] link [chars] [chars]
Explanation An unexpected condition has occurred at Bundle link configuration %s
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_MPLS

%FMANRP_MPLS-3-NOOBJ : Object entry is null
Explanation An unexpected condition has occurred which is due to the absence of an object entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show mpls command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_MPLS-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_MPLS-3-UNSPTYPE : Not supported bundle type [dec]
Explanation An unexpected condition has occurred which is due to an operation request to an unsupported bundle oce type is received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_NAT through FME_DP

FMANRP_NAT

%FMANRP_NAT-4-NOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-IFTDLMSGMARSHAL : Failed to copy interface config essage to IPC buffer for Interface [chars] ([hex]), domain [chars], operation [chars]
Explanation This operation to build a TDL message for interface configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-NONATSERVICE : Service structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT service structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-SERTDLMSGMARSHAL : Failed to copy service config message to IPC buffer for application type [dec], protocol type [dec], port [dec]
Explanation This operation to build a TDL message for service configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-SERVICERM : Failed to delete NAT services for appl type [chars], protocol [chars], port [dec]
Explanation An unexpected condition has occurred which is due to the failure to remove data structures for NAT special services.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-NOPOOL : Pool structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT pool structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-NOMAPPING : A mapping structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT mapping structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-BADACTION : Invalid action [dec] for NAT configuration
Explanation An unexpected condition has occurred which is invalid action for a NAT configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-POOLTDLMSGMARSHAL : Failed to copy pool config message to IPC buffer for pool [chars] (id [dec])
Explanation This operation to build a TDL message for pool configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-MAPPINGTDLMSGMARSHAL : Failed to copy mapping config message to IPC buffer for mapping id [dec] (vrf table id [dec])
Explanation This operation to build a TDL message for mapping configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-IFADDRTDLMSGMARSHAL : Failed to copy interface address change message to IPC buffer for interface [chars], new address [IP_address]
Explanation This operation to build a TDL message for NAT interface address configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-VRFDELTDLMSGMARSHAL : Failed to copy VRF delete message to IPC buffer for vrf table id [dec]
Explanation This operation to build a TDL message for vrf deletion configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-TIMEOUTTDLMSGMARSHAL : Failed to copy timeout config message to IPC buffer for timeout type [dec]
Explanation This operation to build a TDL message for timeout configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-NORANGE : Pool address range structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT pool address range structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-RANGETDLMSGMARSHAL : Failed to copy pool address range config message to IPC buffer for pool [chars], range start [IP_address], range end [IP_address]
Explanation This operation to build a TDL message for address range configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-PORTLISTTDLMSGMARSHAL : Failed to copy portlist config message to IPC buffer for addr [IP_address], proto [dec], start_port [dec], end_port [dec]
Explanation This operation to build a TDL message for portlist add/delete has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-NOACL : Access list is null
Explanation An unexpected condition has occurred which is due to the absence of an access list structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-MAXENTRYTDLMSGMARSHAL : Failed to copy max entry config message to IPC buffer for type [chars], entry data [hex], max_limit [dec]
Explanation This operation to build a TDL message for max entry add/delete has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-STATSUPDTDL : Failed to update NAT [chars] statistics
Explanation An unexpected condition has occurred when updating statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-IPALIASTDL : Error with ipalias message received from data path
Explanation An unexpected condition has occurred with received ipalias message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-IPALIASTYPE : Received ipalias message from data path with unsupported address type [dec]
Explanation An unexpected condition has occurred with received ipalias message from data path with unsupported address type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-IPSTATICROUTETDL : Error with static ip route message received from data path
Explanation An unexpected condition has occurred with received static ip route message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-IPSTATICROUTETYPE : Received ip static route message from data path with unsupported address type
Explanation An unexpected condition has occurred with received static ip route message from data path with unsupported address type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-PORTLISTTDL : Error with portlist allocation request message received from data path
Explanation An unexpected condition has occurred with received portlist allocation request message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-PORTLISTTYPE : Address type [dec] for global address in the portlist allocation request is not supported
Explanation An unexpected address type has occurred with received portlist allocation request message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-PORTLISTPROTO : Protocol type [dec] for global addr [IP_address] in the portlist allocation request is not supported
Explanation An unexpected protocol type has occurred with received portlist allocation request message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-DEBUGTDLMSGMARSHAL : Failed to copy debug NAT request message to IPC buffer
Explanation This operation to build a TDL message for debug NAT command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-IOSDENQUEUE : Failed to enqueue NAT [chars] message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-AVLTREEWALK : Failed to walk NAT [chars] database for [chars]
Explanation This operation to perform stale processing has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-AVLDELETE : Failed to delete node from NAT [chars] database for [IP_address]
Explanation This operation to perform delete processing has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-WLANSESSTDL : Error with WLAN session message received from data path
Explanation An unexpected condition has occurred with received WLAN session message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-WLANSESSTYPE : Received WLAN session message from data path with unsupported address type [dec]
Explanation An unexpected condition has occurred with received WLAN session message from data path with unsupported address type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-WLANSESSIDB : Received WLAN session message from data path with nil input interface for inside local host [IP_address]
Explanation An unexpected condition has occurred with received WLAN session message from data path with nil input interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-NOLOGGINGPARAM : Highspeed logging structure is nil
Explanation An unexpected condition has occurred which is due to the absence of a logging parameter structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show running command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-LOGGING_PARAM : Highspeed logging export [chars] [int]nsupported
Explanation An unsupported exporting paremeter for highspeed logging on data path is received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show running command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-4-NOREPLICATEPARAM : Session replication structure is nil
Explanation An unexpected condition has occurred which is due to the absence of a session replication parameter structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show running command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-MIBEVENT : Failed to get NAT MIB response message: [chars]
Explanation An unsupported error occured with waiting for NAT MIB respsonse message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-INVALID_ADDRESS : Received an invalid address [IP_address]
Explanation An unsupported address for the given config was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-MSGALLOCERR : Failed to allocate message
Explanation When attempting to send message to dataplane, there was not enough memory to allocate the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NAT-3-NATSETTDLMSGFAIL : When download [chars], failed to set a field in message
Explanation sotware error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_NETFLOW

%FMANRP_NETFLOW-3-CACHETDLMSGMARSHAL : Failed to copy cache config message to IPC buffer for cache type [dec]
Explanation The operation of building a TDL message for cache configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-AGGRCACHENULL : The pointer for aggregation cache type [dec] is NULL
Explanation An unexpected condition has occurred which is due to the absence of an aggregation cache data structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip cache flow command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-UNKNOWNCACHETYPE : Unknown cache type [dec] received
Explanation The cache configuration command has failed due to unknown cache scheme type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-UNKNOWNCACHECMD : Unknown aggregation cache command [dec] received
Explanation The aggregation cache configuration command has failed due to unknown command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-4-NOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-4-NOFIBIDB : fibdb for interface [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a fibidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-IFFLOWTDLMSGMARSHAL : Failed to copy interface flow config message to IPC buffer for [chars]
Explanation The operation of building a TDL message for interface flow configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-NOSAMPLERNAME : Sampler-map name is null
Explanation An unexpected condition has occurred which is due to the absence of a sampler-map name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show sampler command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-NOSAMPLER : Sampler for sampler-map name [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a sampler-map structure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show sampler command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-SAMPLERTDLMSGMARSHAL : Failed to copy sampler-map config message to IPC buffer for [chars]
Explanation The operation of building a TDL message for sampler-map configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-EXPORTERTDLMSGMARSHAL : Failed to copy exporter config message to IPC buffer for cache type [dec]
Explanation The operation of building a TDL message for exporter configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-4-EXPORTERVERSION : Failed to change default exporter version to [dec]
Explanation The operation of changing the default exporter version has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip flow export command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-CLRSTATSTDLMSGMARSHAL : Failed to copy clear statistics message to IPC buffer
Explanation The operation of building a TDL message for clearing statistics in the data path has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-STATSUPDTDL : Failed to update netflow [chars] statistics
Explanation An unexpected condition has occurred when updating statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-INVALIDFLOWDEFCPP : CPP Flow definition can not be created [int]
Explanation The operation of building a flow definition using flow fields received from CPP has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-EXPORTERSRCIFINVALID : Management interface ([chars]) cannot be used as source for an exporter
Explanation Exporter configuration failed because the management interface cannot be configured as source interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_NETFLOW-3-EXPORTERVRFINVALID : Management vrf ([chars]) cannot be used as exporter destination
Explanation Exporter configuration failed because management vrf cannot be used as exporter destination
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_PBR

%FMANRP_PBR-3-RTMAPNULL : The route-map structure for [chars] is NULL
Explanation An unexpected condition has occurred due to the absence of an internal route-map data structure.
Recommended Action show route-map


%FMANRP_PBR-3-RTMAP_NAME_NULL : The route-map name for [chars] is NULL
Explanation An unexpected condition has occurred due to the absence of an internal route-map data structure.
Recommended Action show route-map


%FMANRP_PBR-3-INVALIDIF : The interface specified for '[chars]' is not valid
Explanation An non-existent interface is specified for the policy based routing route-map operation specified in the message.
Recommended Action show interface


%FMANRP_PBR-3-UNSUPPORTED_RMAP : Route-map [chars] has unsupported options for Policy-Based Routing. It has been removed from the interface, if applied.
Explanation The route-map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation.
Recommended Action Reconfigure the route-map. Use only 'permit' entries and 'set ip next-hop' action in the route-map.


%FMANRP_PBR-3-UNSUPPORTED_RMAP_COMMAND : This Policy-Based Routing command is not supported on this platform. Use the no form of this command to remove it from configurations
Explanation Policy-Based Routing is not supported on this platform
Recommended Action Remove this command


FMANRP_PFR

%FMANRP_PFR-4-NULLINPUT : NULL input, [chars]
Explanation An unexpected condition has occurred which is due to the NULL value of the input parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show oer border command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_PFR-4-NOINTF : PfR Interface [chars] not exist, can't be [chars]
Explanation An unexpected condition has occurred which is due to the absence of MCP PfR interface info.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show oer border command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_PFR-4-UNSUPPORTED : Unsupported action, [chars]
Explanation An unexpected condition has occurred which is due to and unsupported action being executed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show oer border command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_QOS

%FMANRP_QOS-3-ACTNOCLASSMAP : Class-map information not found
Explanation An unexpected condition has occured when trying to determine class-map information for one of the classes in a policy-map.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-ACTNOPOLICYMAP : Policy-map information not found
Explanation An unexpected condition has occured when trying to determine policy-map information for one of the service policies attached to an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSTDLMARSHAL : Failed to copy more than [dec] bytes of message [chars], length [dec] into IPC buffer
Explanation An internal error occured when trying to build an IPC message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSAPIPARAM : Internal QOS API error.
Explanation An internal API error occured. QOS configuration may be limited.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSIDBSP : Service policy [[chars]] installation error: invalid interface type [dec]
Explanation An invalid interface type was encountered when trying to configure a service policy. This service policy could not be installed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSGIDBSP : Service policy [[chars]] installation error: invalid interface type [dec]
Explanation An invalid interface type was encountered when trying to configure a service policy. This service policy could not be installed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-QOSSTACK : Failed to install all classes for policymap [chars], excessive stack usage
Explanation An operation to configure the classes within a policymap has failed due to a resource issue. QoS configuration for this policymap is unlikely to work.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSCLASSDEL : Error trying to remove class [chars] from policymap [chars]
Explanation An operation to remove a class from a policy has failed due to an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-6-QOSCLASSEXIST : class [chars] (id [int]) in policymap [chars] (id [int]) already exists
Explanation This is an informational message and no action is required.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-NOPOLICERSTATS : policer stats entry not found for class [int].[int], target [int]
Explanation An internal error occured when looking up policer statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-NOACCOUNTSTATS : account stats entry not found for class [int].[int], target [int]
Explanation An internal error occured when looking up account statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-NOSETSTATS : set stats entry not found for class [int].[int], target [int]
Explanation An internal error occured when looking up set statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show policy-map interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-QIDGENFAIL : qid generation failed, reverting to default
Explanation An internal error occured during platform qos initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-QOSUBR : qos can not be attached to the target with UBR configured
Explanation An error occured to attach qos to ATM VC/VP target with UBR configured
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-NOFAIRQONVC : fair-queue can not be configured on the parent queue of an ATM VC, use child queue instead
Explanation Configuring fair-queue on the parent queue of an ATM VC is not supported
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-CLMODIFYFAIL : classmap [chars] is currently used by policymap, please remove policymap from all targets before the modification
Explanation An internal error occured when classmap being modified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-CLPOLFAIL : No support for client policy with policing in class-default and marking in custom class
Explanation An internal error occured during installing qos policy.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-MPOLDMVPNGRE : Only Shape and/or BRR is allowed on the QoS policy on GRE tunnel on MPoL hierarchy
Explanation An error occurred during MPoL check between DMVPN and GRE tunnel QoS policy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSTMPLCREATEFAIL : QoS template interface creation failed for policy [chars]: [chars]
Explanation An error occured during template interface creation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSTMPLDELETEFAIL : QoS template interface deletion failed for policy [chars]: [chars]
Explanation An error occured during template interface deletion
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSTMPLNONEXIST : QoS template does not exist in [chars] for policymap [chars]
Explanation QoS template information does not exist
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QOSTMPLDBERROR : Failed to [chars] record for policymap [chars], err [chars]
Explanation Database operation failed for record of the policymap
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-PRILEVELSUPPORT : Priority with level 3 is not supported. Service-policy : [chars]
Explanation Priority level 3 support is only for AVB policy. Hence configuration is rejected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-MARKDOWNCHECK : Only markdown with a table-map is supported.
Explanation Error occured while performing exceed action check on the policy attached
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-CONFACTCHECK : Conform-action in a policer can only be transmit. Policy Rejected.
Explanation Error occured while performing conform action check on the policer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-SHAPEBWSUPPORT : Shape and bandwidth in the same class is unsupported. Policy Rejected. Service-policy : [chars]
Explanation Error occured while performing qos policy check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-QBUFFERSCHECK : Sum of configured qbuffer ratios should be less than 100. Configuration not accepted. Service-policy : [chars] Info : classes for which qbuffer ratio is not configured is given a buffer ratio 1
Explanation Error occured while performing queue buffers policy install check. Wrong configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-HWIDBCHECK : Configuring service-policy on interface [chars] is not allowed
Explanation Error occured while attaching policy on gigethernet0/0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-HIERPOLICYCHECK : Hierarchical Policy must have child under all user defined classes for wired ports. Service-policy : [chars]
Explanation Error occured while attaching a hierarchical policy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-3-CHILDPOLICYCHECK : Only 2 level policy is supported. Service-policy : [chars]
Explanation Error occured while attaching a hierarchical policy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-COPPMODIFY : Police rate modification for COPP system class ([chars]) is discouraged. User can go to default rate by running 'cpp system-default' CLI.
Explanation User modified police rate for COPP system classes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_QOS-4-COPPMODRANGE : Police rate modification for COPP system class ([chars]) is out-of-range. User can go to default rate by running 'cpp system-default' CLI.
Explanation User modified police rate for COPP system classes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_SC

%FMANRP_SC-3-SCTXTDLMSGMARSHAL : Failed to copy service context config message to IPC buffer for sctx_name id [dec]
Explanation This operation to build a TDL message for service context configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SC-3-DBGTDLMSGMARSHAL : Failed to copy debug SC request message to IPC buffer
Explanation This operation to build a TDL message for debug SC command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SC-3-SCIOSDENQUEUE : Failed to enqueue SC [chars] message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SC-3-INTFTDLMSGMARSHAL : Failed to copy interface config message to IPC buffer for Interface [chars] ([hex]), operation [chars]
Explanation This operation to build a TDL message for interface configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SC-4-SCNOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SC-4-NOSERVICECTX : A mapping structure is null
Explanation An unexpected condition has occurred which is due to the absence of a SC mapping structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SC-4-SCBADACTION : Invalid action [dec] for SC configuration
Explanation An unexpected condition has occurred which is invalid action for a SC configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


FMANRP_SSLVPN

%FMANRP_SSLVPN-3-STATSCLEARERR : Unable to send clear WEB VPN context stats message. [chars] ([dec])
Explanation This operation to build a TDL messages for WEB VPN context stats clearing has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-STATSGUPDERR : Update WEB VPN context stats error. [chars] ([dec])
Explanation An unexpected condition has occurred when updating global sslvpn statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-STATSWVUPDERR : [chars]: [chars]
Explanation An unexpected condition has occurred when updating ssl web vpn context statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-CFGSTATUSERR : [chars]: [chars]
Explanation An unexpected condition has occurred when got status of configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-GWERR : Failed [chars]: [chars]
Explanation An unexpected condition has occurred in configuration processing causing configuration failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-VWCONFERR : Failed [chars]: [chars]
Explanation An unexpected condition has occurred during WebVPN Context configuration causing failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-PKIERR : Failed [chars]: [chars]
Explanation An unexpected condition has occurred in configuration processing causing configuration failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-AAATDLERR : [chars][chars]. [chars]
Explanation An unexpected condition has occurred in processing AAA request/reply message causing AAA handling failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-4-AAAFRIPWARN : [chars]Invalid framed ip address [IP_address] received from AAA. Not sending user config
Explanation Wrong AAA server config.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-RRITDLERR : [chars][chars]. [chars]
Explanation An unexpected condition has occurred in processing of SSLVPN route inject/remove message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-RRICHUNKERR : [chars]
Explanation Error has occurred when requested memory for SSLVPN route handling
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FMANRP_SSLVPN-3-CONDDEBERR : [chars]. [chars]
Explanation An unexpected condition has occurred in processing conditional debug message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FMD

%FMD-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper FMD software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%FMD-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper FMD software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck binding that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%FMD-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the FMD feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the FMD feature will not function. LOG_STD_ACTION


FME

%FME-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper FME software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%FME-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper FME software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%FME-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the FME feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the FME feature will not function. LOG_STD_ACTION


FME_DP

%FME_DP-3-DEBUG_REG_FAILED : Flow Metric Engine fails to registrate with Conditional Debugging.
Explanation Flow Metric Engine fails to registrate with Conditional Debugging infra.
Recommended Action LOG_STD_ACTION


FMFP through FRAG

FMFP

%FMFP-3-INTERFACE_OBJECT_NOT_FOUND : Interface object lookup by [chars] not found for interface [int]
Explanation The desired interface object was not found.
Recommended Action Examine the interface state in the operating system, route processor (RP) and forwarding processor (FP) forwarding manager logs.


%FMFP-3-OBJ_DWNLD_TO_DP_FAILED : [chars] download to DP failed
Explanation An object has failed to download to the data plane
Recommended Action Examine the list of error objects in the forwarding processor (FP) forwarding manager asynchronous object logs.


%FMFP-3-OBJ_DWNLD_TO_DP_STUCK : AOM download to Data Plane is stuck for more than [int] seconds [chars]
Explanation An object download from FMAN-FP to lower layer has taken long time. It can be caused by incomplete configuration or software defects
Recommended Action Run show platform software object-manager fp [active|standby] [pending-issue-update|pending-issue-batch] sorted <min_pending_time> to see the sorted list of update/batch/ command in pending state for more than the min_pending_time. For incomplete configuration, use show platform platform software object fp [active|standby] resolve to see if there is any resolve object


%FMFP-6-OBJ_DWNLD_TO_DP_RESUME : AOM download of objects to Data Plane is back to normal
Explanation An object download from FMAN-FP to lower layer has finished after a temporary stuck. It can be caused by incomplete configuration or software defects
Recommended Action check if there is any functional impact after recovery


%FMFP-3-OBJ_ACK_FROM_DP_STUCK : AOM ack download to Data Plane is stuck for more than [int] seconds [chars]
Explanation An object ack from lower layer to FMAN-FP has taken long time. It can be caused by incomplete configuration or software defects
Recommended Action Run show platform software object-manager fp [active|standby] [pending-ack-update| pending-ack-batch|pending-ack-commands] sorted <min_pending_time> to see the sorted list of update/ batch/command in pending state for more than the min_pending_time. For incomplete configuration, use show platform platform software object fp [active|standby] resolve to see if there is any resolve object


%FMFP-6-OBJ_ACK_FROM_DP_RESUME : AOM ack of objects to Data Plane is back to normal
Explanation An object ack from lower layer to FMAN-FP has finished after a temporary stuck. It can be caused by incomplete configuration or software defects
Recommended Action check if there is any functional impact after recovery


%FMFP-3-DP_NOMEM : DP not enough memory. [chars]
Explanation An object download to DP failed because the memory of DP is not enough.
Recommended Action Run show platform resource to see the memory usage


FMFP_ACL

%FMFP_ACL-3-ACL_OBJECT_DOWNLOAD : [chars][chars] fail to download because [chars].
Explanation The access control list (ACL) object has failed to download. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant object download states. Remove the ACL attachment to the interface or delete the ACL. Reboot the forwarding processor (FP).


%FMFP_ACL-3-ACL_LIMIT_EXCEEDED : ACL [chars] exceeded limitation of [int] ACEs per ACL
Explanation A software limitation has been exceeded.
Recommended Action Reduce the access control list (ACL) configuration. A reboot of the forwarding processor (FP) is recommended.


%FMFP_ACL-3-ACL_PROTOCOL_CHECK : ACL [chars] protocol does not match what was previously configured
Explanation The error occurs for one of two reasons. An access control list (ACL) reference was made to an ACL of a different protocol or an ACL was added or edited when there were similarly named ACL references of a different protocol
Recommended Action Remove the conflicting ACL or the conflicting ACL references.


%FMFP_ACL-3-ACL_MODIFY_FAILED : ACL:[chars] modification through object group edit failed
Explanation Object-group used in the ACL was modified. Those changes could not be accommodated in the ACL
Recommended Action Fix the object-group changes. Delete ACL and reconfigure it


%FMFP_ACL-3-SGACL_OBJECT_DOWNLOAD : SGACL Cell ([dec] [dec]) policy [chars] fail to download because [chars].
Explanation The SGACL policy has failed to download. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant object download states. Remove the SGACL policy for that cell, correct the error and reconfigure it


FMFP_CXSC

%FMFP_CXSC-3-CXSC_INITIALIZATION : [chars] Returned: [chars]
Explanation The CXSC INITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC.


%FMFP_CXSC-3-CXSC_DEINITIALIZATION : [chars] Returned: [chars]
Explanation The CXSC DEINITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC.


%FMFP_CXSC-3-CXSC_DOMAIN_CONFIG : [chars] Returned: [chars]
Explanation The CXSC DOMAIN CONFIG DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC.


%FMFP_CXSC-3-CXSC_POLICY_DOWNLOAD : [chars] Returned: [chars]
Explanation The CXSC POLICY DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows same results then please contact TAC.


%FMFP_CXSC-6-CXSC_POLICY_DOWNLOAD_SUCCESS : New policy version: [int] has now been installed and is active
Explanation The CXSC POLICY DOWNLOAD of the numbered version has succeeded.
Recommended Action This an informational message only, no action is required. Note that policy version is not monotonically increasing so there is nothing to be concerned about if the current installed policy version is less than the previous installed policy version.


FMFP_QOS

%FMFP_QOS-6-QOS_STATS_STALLED : statistics stalled
Explanation QoS statistics are temporarily stalled. This is an informational message.
Recommended Action No action is required.


%FMFP_QOS-6-QOS_STATS_PROGRESS : statistics are progressing
Explanation QoS statistics are now progressing normally. This is an informational message.
Recommended Action No action is required.


FMFP_URPF

%FMFP_URPF-3-OBJECT_DOWNLOAD : Unicast RPF [chars] on inteface [chars] fail to download because [chars].
Explanation The unicast reverse path forwarding (URPF) operation failed to download. This can be caused by a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant download states.Remove the uRPF feature enabled on any interface. Reboot the forwarding processor (FP).


%FMFP_URPF-3-LIST_DOWNLOAD : Unicast RPF list [chars] for list [int] fail to download because [chars].
Explanation The unicast reverse path forwarding (URPF) list failed to download. This can be caused by a hardware or software resource limitation or software defect.
Recommended Action Check the logs for information on the relevant download states.Reboot the forwarding processor (FP).


FNF

%FNF-6-AGER_OVERRIDE : Flow [chars] time modified by [chars] to [dec]
Explanation The aging timer has been modified and may be different from configured value.
Recommended Action No action is required.


%FNF-6-ERROR : FNF error: [chars]
Explanation An FNF error occurred.
Recommended Action For more information, repeat the action with FNF debugging enabled.


%FNF-6-CONFIGURATION : Invalid FNF configuration: [chars]
Explanation An invalid FNF configuration was detected.
Recommended Action Review the FNF configuration before repeating the action.


%FNF-3-LC_STATUS : Flow monitor [chars] can not be added to [chars], rejected on module [chars] : [chars]
Explanation The flow monitor has been rejected on the specified module. It will have been removed from the RP configuration too. This can happen for example when a monitor is removed and added again immediately before the tidy has been completed, or in the case where a flow monitor is waiting at automore when the monitor is removed from the interface then reapplied
Recommended Action Check the configuration of the Flow Monitor that was applied for errors. If the rejection was due to the LC not having finished cleaning up after a previous removal of a Flow Monitor, wait until the cleaning up has finished then reapply the config.


%FNF-3-PROVISIONING : [chars] failed to provision '[chars] flow monitor [chars] [chars]' on [chars]: [chars]
Explanation The attachment of the Flow Monitor to has had a problem on the device identified. It may be working on other devices, and the configuration is retained.
Recommended Action Check the device identified is working as expected and that it can support the configuration of the Flow Monitor to the chosen attachment point.


%FNF-3-KEY_SIZE_INVALID : Unexpected key fields size: [dec], MSGDEF_LIMIT_SLOW
Explanation Netflow attempted to install a flow with an invalid key fields size.
Recommended Action LOG_STD_ACTION


%FNF-4-FREE_LIST_EMPTY : Monitor: [hex], MSGDEF_LIMIT_MEDIUM
Explanation Netflow attempted to install a flow but no free flow records were available.
Recommended Action LOG_STD_ACTION


%FNF-3-FREE_LIST_ADD : Failed for record: [hex], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to return a record to the free list.
Recommended Action LOG_STD_ACTION


%FNF-3-CLEANUP_ENTRY : Failed, MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to clean up a record for reuse.
Recommended Action LOG_STD_ACTION


%FNF-3-UNSUPPORTED_PROT : [chars], MSGDEF_LIMIT_MEDIUM
Explanation This protocol is unsupported.
Recommended Action LOG_STD_ACTION


%FNF-3-INVALID_CMD : Flow builder encountered an invalid command: [dec]., MSGDEF_LIMIT_MEDIUM
Explanation Flow builder doesn't support the command encountered in the instruction stream.
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_UNSUPPORTED_AGG_FMT : Format: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow doesn't support this aggregation type.
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_UNSUPPORTED_EXP_FMT : Format: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow doesn't support this export format.
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_UNSUPPORTED_OPTION : Option: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow doesn't support this export option.
Recommended Action LOG_STD_ACTION


%FNF-3-IPFIX_UNSUPPORTED_MON_TYPE : Monitor type: [dec], MSGDEF_LIMIT_MEDIUM
Explanation IPFIX doesn't support this monitor type.
Recommended Action LOG_STD_ACTION


%FNF-3-REFCNT_TIMEOUT : never reached 0 for entry [hex], MSGDEF_LIMIT_SLOW
Explanation Netflow timed out waiting for an flow cache entries refcnt. to hit 0. The entry was forced out
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_UNSUPPORTED_MMA_FIELD : MMA global ID [dec] (Netflow field [dec]) is not supported by MMA, MSGDEF_LIMIT_SLOW
Explanation Netflow field that is marked as MMA (Metric Mediation Agent) controlled field is not supported by MMA
Recommended Action LOG_STD_ACTION


%FNF-3-REFCNT_UNDERFLOW : refcnt underflow for entry [hex], MSGDEF_LIMIT_SLOW
Explanation Netflow error caused flow cache entry reference count to go negative. The decrement was rescinded
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_FIELD_LIST_VAR_INVALID : Unknown field variety [dec] for field_id [dec], MSGDEF_LIMIT_MEDIUM
Explanation Internal error, Netflow field list entry mapped to unknown field variety
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_FIELD_UNEXPECTED_SIZE : Unexpected size for field_id [dec], expected [dec]/got [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow specified unexpected size for field_id
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_FIELD_LIST_TS_CNT_KEY : Field_id [dec] must be non-key, MSGDEF_LIMIT_MEDIUM
Explanation Netflow Field list specified timestamp/counter field as a key field, which is not supported
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_FIELD_LIST_TOO_LARGE : Field_list too large, max [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow field list contains too many fields. At most 32 fields are supported, including any hidden fields automatically added as necessary for record keeping
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_FREC_LAYOUT_TOO_LARGE : Flow record layout too large, max [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow field list results in a flow record layout which is too large. At most 128 bytes of flow record data is supported, including any padding, and any hidden fields automatically added as necessary for record keeping
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_FIELD_LIST_MEM_INSUFFICIENT : Insufficient memory [dec] for field_list, MSGDEF_LIMIT_MEDIUM
Explanation Internal error, netflow client provided insufficient memory to process a field list
Recommended Action LOG_STD_ACTION


%FNF-3-INVALID_FO : FNF FO is not valid, MSGDEF_LIMIT_MEDIUM
Explanation FNF feature object is not valid.
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_CWALK_FLEXIBLE_UNEXPECTED_LAYOUT : Failed copy to CLI buffer , PI will receive zero buffer, MSGDEF_LIMIT_MEDIUM
Explanation Failed copy to CLI buffer during the walk process ,fill the buffer with 0
Recommended Action LOG_STD_ACTION


%FNF-6-DYNAMIC_MONITORS_OVER_SUBSCRIPTION : Interface [chars] (dir=[chars]): the number of monitors that should run on the packet([dec]) exceeds QFP limit([dec]), [dec] monitor[chars] won't run, MSGDEF_LIMIT_GLACIAL
Explanation QFP maximum supported number of monitors per packet was exceeded. As a result the excess number of monitors will not run on the packet. Static monitors always take priority over policy-map monitors.
Recommended Action LOG_STD_DBG_ACTION


%FNF-6-SYNC_CACHE_TOO_MANY_RECS_FOR_INTERVAL : For synchronized cache the number of records is larger than can be exported in configured interval., MSGDEF_LIMIT_MEDIUM
Explanation The number of records is too large for the configured interval. As a result some records may not be exported in a timely manner. Consider reducing cache size or increasing interval length.
Recommended Action LOG_STD_DBG_ACTION


%FNF-3-DEBUG_REG_FAILED : FNF fails to registrate with Conditional Debugging.
Explanation FNF fails to registrate with Conditional Debugging infra.
Recommended Action LOG_STD_ACTION


%FNF-3-CFT_REG_FAILED : FNF fails to connect to CFT infra.
Explanation FNF fails to connect to CFT infra.
Recommended Action LOG_STD_ACTION


%FNF-3-FNF_EXPORT_BUILD_TYPE_FAILED : Format: [dec], MSGDEF_LIMIT_MEDIUM
Explanation FNF Exporter build failed. unknown type.
Recommended Action


FNF_PROXY

%FNF_PROXY-3-IPC_UNHANDLED : type [dec]
Explanation An unknown message was received by the Netflow Client Proxy.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-MON_CACHE_FREE_LIST_INIT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to initialize the free list.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-MON_CACHE_FREE_LIST_POOL_ADD : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to populate the free list.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-MON_CACHE_AGER_INIT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to initialize the ager.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-MON_CACHE_AGER_SHUT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to shutdown the ager.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-MON_CACHE_FORCE_FLUSH : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to force a cache flush.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EXPORTER_INIT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to initialize the exporter.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EXPORTER_SHUT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to shutdown the exporter.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EXPORTER_OPTION_TEMPLATE_BIND : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to bind an option template.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EXPORTER_OPTION_TEMPLATE_UNBIND : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to unbind an option template.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EXPORTER_OPTION_TIMER_START : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to start an option timer.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EXPORTER_OPTION_TIMER_STOP : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to stop an option timer.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EXPORTER_FORCE_TEMPLATE_REFRESH : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to force a template refresh for an exporter.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-FLOW_CACHE_WALK : Failed for session: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a flow cache walk request.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-OBJ_MODIFY : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process an object modify request.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-STATS : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a stats request.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-EVAL_FREC_FIELD_LIST : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process an evaluate flow record field list request.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-PROCESS_FREC_FIELD_LIST : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a process flow record field list request.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-FLOW_CACHE_WALK_FLEXIBLE : Failed for session: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a flow cache walk/flexible request.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED :
Explanation Allocation of IPC packet failed.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-PROXY_IPC_SEND_FAILED : [dec]
Explanation Could not send IPC reply for proxy request.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-MON_CACHE_CLEAN : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to perform cache cleanup.
Recommended Action LOG_STD_ACTION


%FNF_PROXY-3-FNF_CWALK_TOP_TALKERS_INVALID_SORT : This field can't be used for sort, MSGDEF_LIMIT_MEDIUM
Explanation Show Top Talkers command contains sort field specification that is not supported.
Recommended Action LOG_STD_ACTION


FPD_MGMT

%FPD_MGMT-6-BUNDLE_DOWNLOAD : Downloading FPD image bundle for [chars] card in [chars] ...
Explanation The system is downloading the field programmable device image bundle to the system main memory.
Recommended Action No action is required.


%FPD_MGMT-6-UPGRADE_TIME : Estimated total FPD image upgrade time for [chars] card in [chars] = %TS.
Explanation The estimated total time for all FPD images to be upgraded is displayed for the indicated card.
Recommended Action No action is required.


%FPD_MGMT-6-UPGRADE_START : [chars] (FPD ID=[int]) image upgrade in progress for [chars] card in [chars]. Updating to version [int].[int]. PLEASE DO NOT INTERRUPT DURING THE UPGRADE PROCESS (estimated upgrade completion time = %TS) ... FPD upgrade in progress on hardware, reload/configuration change on those hardware is not recommended as it might cause HW programming failure and result in RMA of the hardware.
Explanation The FPD image upgrade process has started. Do not interrupt the upgrade operation as any interruption could render the target card unusable. Avoid actions like removing the target card from the system, powering off the system, or using commands that can power-cycle the target card during the upgrade process.
Recommended Action No action is required.


%FPD_MGMT-6-UPGRADE_PASSED : [chars] (FPD ID=[int]) image in the [chars] card in [chars] has been successfully updated from version [chars] to version [int].[int]. Upgrading time = %lTE
Explanation The FPD image upgrade process has completed successfully for the indicated device.
Recommended Action No action is required.


%FPD_MGMT-6-OVERALL_UPGRADE : All the attempts to upgrade the required FPD images have been completed for [chars] card in [chars]. Number of successful/failure upgrade(s): [int]/[int].
Explanation All the FPD image upgrades have completed for the indicated card.
Recommended Action No action is required.


%FPD_MGMT-6-UPGRADE_RETRY : Attempting to recover from the failed upgrades ...
Explanation Because of an image upgrade failure, the system will attempt again the upgrade operation for the same FPD image.
Recommended Action No action is required.


%FPD_MGMT-6-PENDING_UPGRADE : [int] more FPD image upgrade operation will be required on [chars] in [chars] after additional power-cycle operation on the target card.
Explanation All upgrade operations have not completed, and additional power-cycle operations are required before the upgraded or new FPD image will be applied to the system configuration. The message text indicates the number of pending upgrade operations that will be performed. More than one power-cycle operation might be required to complete the overall upgrade process.
Recommended Action No action is required.


%FPD_MGMT-5-UPGRADE_ATTEMPT : Attempting to automatically upgrade the FPD image(s) for [chars] card in [chars]. Use 'show upgrade fpd progress' command to view the upgrade progress ...
Explanation The automatic FPD image upgrade feature is enabled with the upgrade fpd auto global configuration command. The system is currently upgrading an incompatible image version automatically.
Recommended Action No action is required. The upgrade process can take a long time.The FPD_MGMT-6-UPGRADE_TIME message gives an estimate of the total upgrade time


%FPD_MGMT-5-CARD_POWER_CYCLE : [chars] card in [chars] is being power cycled for the FPD image upgrade to take effect.
Explanation The indicated card is being power cycled after the FPD image upgrade. This action allows the target card to be operational with the new upgraded FPD image or images.
Recommended Action No action is required.


%FPD_MGMT-5-POST_UPGRADE_REMINDER : [chars] card in [chars] will require a [chars] for the FPD image upgrade to take effect.
Explanation The indicated card will require manual intervention after the FPD image upgrade. The specified operation is required for the upgraded FPD image to take effect.
Recommended Action No action is required.


%FPD_MGMT-4-BYPASS_AUTO_UPGRADE : The automatic FPD image upgrade feature is not enabled, bypassing the image upgrade for [chars] card in [chars].
Explanation The automatic FPD image upgrade feature is not enabled. The incompatible image will not be automatically upgraded. The card will be disabled until the image is upgraded to a compatible version.
Recommended Action Enable the automatic FPD image upgrade with the upgrade fpd auto global configuration command or use the upgrade hw-module privileged EXEC command for a manual upgrade operation. For more information about these commands, refer to the FPD_DOCUMENT_NAME .


%FPD_MGMT-4-UPGRADE_EXIT : Unexpected exit of FPD image upgrade operation for [chars] card in [chars].
Explanation The FPD image upgrade operation was interrupted by the physical removal of the card from the system or by the use of other commands that have interrupted the normal operation of the target card. The partial upgrade operation might have left the card unusable because of corrupted FPD images.
Recommended Action If the card does not come up after reinserting into the system, then perform the recovery upgrade operation by using the upgrade hw-module privileged EXEC command. With this command the system will attempt the reprogramming of the image to recover from the previous partial upgrade operation. For more information about performing a recovery upgrade operation, refer to the FPD_DOCUMENT_NAME .


%FPD_MGMT-4-VERSION_CHECK_ABORTED : FPD image version check operation has been aborted for [chars] card in [chars] because manual upgrade has already being started.
Explanation The FPD image version check operation required for the automatic upgrade feature is not being performed for the indicated card because the upgrade hw-module privileged EXEC command has already being executed. These two operations cannot be performed at the same time.
Recommended Action If an automatic upgrade operation is required, do not enter the upgrade hw-module privileged EXEC command for the manual upgrade while the target card is initializing. Enter the show hw-module subslot fpd command and ensure that the target card is displayed in the command output before proceeding with the manual upgrade.


%FPD_MGMT-4-CFG_NOT_SYNCED : Failed to sync [chars] command to standby: [chars]
Explanation A FPD configuration command failed to get synced to standby RP due to the indicated error condition. Usually this can happen if the standby RP hardware doesn't support the type of filesystem supported on the active one.
Recommended Action Configure again the command with a filesystem that is supported on both standby and active RP. To find out if a specific filesystem is also supported on standby RP, the dir ? command can be used to display a list of filesytem supported on both standby and active RP.


%FPD_MGMT-3-INVALID_IMG_VER : Invalid [chars] (FPD ID=[int]) image version detected for [chars] card in [chars].
Explanation The indicated field programmable device contains an invalid version for the FPD image, because the system was not able to extract this information from the indicated card. A failed upgrade attempt might have corrupted the FPD image identification on the device.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.


%FPD_MGMT-3-IMG_VER_NOT_FOUND : FPD image version information is not available for [chars] card in [chars]. All the FPD images will be upgraded to recover from this error.
Explanation The FPD image version information for the indicated card is not available because the system was not able to extract this information for all the FPDs in the card. This could be the result of a corrupted FPD image from a power failure.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.


%FPD_MGMT-3-INCOMP_IMG_VER : Incompatible [chars] (FPD ID=[int]) image version detected for [chars] card in [chars]. Detected version = [int].[int], minimum required version = [int].[int]. Current HW version = [int].[int].
Explanation An incompatible FPD image version has been detected. The FPD image needs to be upgraded either automatically, or manually, to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, then the card will be disabled.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.


%FPD_MGMT-3-MAJOR_VER_MISMATCH : Major image version mismatch detected with [chars] (FPD ID=[int]) for [chars] card in [chars]. Image will need to be [chars] from version [int].[int] to at least a minimum version of [int].[int]. Current HW version = [int].[int].
Explanation A major image version mismatch has been detected. This incompatibility will need to be resolved by doing an upgrade or downgrade operation either automatically, or manually, to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, then the card will be disabled.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.


%FPD_MGMT-3-OPEN_FAILED : Failed to open [chars] ([chars]). Please make sure that the required file is in a valid path.
Explanation The system cannot access the required file from the indicated URL.
Recommended Action Make sure that the indicated URL is a valid path, and the system has access to the filesystem where the file has been placed.


%FPD_MGMT-3-OUT_OF_MEMORY : Could not allocate the required [dec] bytes of memory.
Explanation The system does not have enough free main memory to download the bundle file.
Recommended Action Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note.If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Use the show memory command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, copy the error message exactly as it appears on the console and gather the output of the show tech-support command and contact your technical support representative with this information.


%FPD_MGMT-3-READ_ERROR : Could not read the [chars] file.
Explanation The system cannot read the required file from the indicated URL.
Recommended Action Make sure that the indicated URL is a valid path, and the system has access to the filesystem where the file has been placed.


%FPD_MGMT-3-BNDL_WRONG_MAGIC_NUM : The [chars] file contains a wrong magic number for the image bundle: [hex] (expected [hex]). Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the target card or the file could be corrupted.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-BNDL_WRONG_HDR_LEN : The [chars] file contains wrong header length for the image bundle: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the target card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-BNDL_WRONG_SIZE : The [chars] file contains incorrect image bundle size: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the target card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-BNDL_CRC_CHECK_FAIL : The [chars] file contains a corrupted image bundle - CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The file failed the CRC checking process. This failure indicates a corrupt FPD image bundle or package file.
Recommended Action Try to download again the required package from the Cisco Software Center website as the indicated one might be corrupted. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd , show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-BNDL_CARD_TYPE_MISMATCH : The [chars] file does not contain the card type ([hex]) in the image bundle to indicate the support of the target card. Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The image bundle in the indicated file does not contain a correct card type value for the target card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-BNDL_NAME_PREFIX_MISMATCH : The [chars] file contains a bundle name prefix ([chars]) that does not match with the expected value of [chars] for the image bundle. Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The content of the selected FPD image bundle does not match its filename.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-INCOMP_BNDL_VER : The selected [chars] file contain an image bundle that has a version number that is incompatible for this IOS release - [chars]. Selected version = [int].[int], minimum compatible version = [int].[int]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. The SPA type is [chars].
Explanation The version of the selected FPD image bundle does not contain a valid version number that is compatible for the IOS release. The major version number should be the same and the minor version number should be at least equal to the minimal required version.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-MISSING_IMAGE : Could not find the required [chars] image (FPD ID=[int] and FPD version=[int].[int] compatible with HW version=[int].[int]) from the [chars]-fpd.bndl bundle in [chars] file. Please make sure that this is a valid FPD image [chars] file for [chars] card in [chars].
Explanation The indicated FPD image bundle or package file might not be the correct one. IF this is a FPD image package file, then an incompatible package file might have been renamed with a filename that matched with the one that the system is expecting for this Cisco IOS software release. You should never rename an FPD image package file name.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-WRONG_IMG_MAJOR_VER : The selected FPD image for upgrade contains wrong FPD image major version number = '[int]' (expected number = '[int]') for [chars] (FPD ID [int]). Please make sure that the file being used for upgrade is a valid FPD image [chars] for card in [chars].
Explanation The file used for upgrade might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-WRONG_IMG_MAGIC_NUM : The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong magic number: [hex] (expected [hex]). Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-WRONG_IMG_HDR_LEN : The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong header length: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-WRONG_IMG_DATA_LEN : The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong data length: total data length (with padding) = [int] bytes, data length = [int] bytes. Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-IMG_CRC_CHECK_FAILED : The FPD image for [chars] (FPD ID [int]) in [chars] file is corrupted - CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The image failed the CRC checking process, this indicates a corrupt FPD image bundle or package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-FPD_UPGRADE_FAILED : [chars] (FPD ID=[int]) image upgrade for [chars] card in [chars] has FAILED.
Explanation The FPD image upgrade process has failed for the indicated device.
Recommended Action Retry the upgrade operation again. If the affected card remains disabled by the system after attempts to retry the upgrade, then copy the error message exactly as it appears and gather the output of show hw-module subslot fpd and contact your technical support representative with the gathered information.


%FPD_MGMT-3-FPD_UPGRADE_CANCELED : Rest of the FPD upgrade sequence for [chars] card in [chars] has been canceled due to upgrade failure with [chars] (FPD ID=[int]) image.
Explanation The FPD image upgrade process for additional FPD images has been canceled due to upgrade error in the indicated device.
Recommended Action Retry the upgrade operation again. If the affected card remains disabled by the system after attempts to retry the upgrade, then copy the error message exactly as it appears and gather the output of show hw-module subslot fpd and contact your technical support representative with the gathered information.


%FPD_MGMT-3-SEND_IMG_FAILED : [chars] (FPD ID=[int]) image for [chars] card in [chars] has failed to be sent for upgrade operation - [chars]
Explanation The FPD image was not able to be sent for the upgrade operation. The system might be too busy to handle this operation. The affected card will be disabled by this failure.
Recommended Action Wait until the system load is lower to try again with the manual upgrade procedure by using the upgrade hw-module privileged EXEC command. If the symptom persists, copy the error message exactly as it appears and gather the output of the show tech-support command and contact your technical support representative with the gathered information.


%FPD_MGMT-3-IMG_DATA_UNCOMPRESS_ERROR : Could not uncompress [chars] FPD image for [chars] in [chars].
Explanation An error has been detected during the uncompress operation of the compressed FPD image data.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-BUNDLE_EXTRACT_ERROR : Cannot extract the [chars] bundle from [chars] - [chars]
Explanation Bundle file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-PKG_VER_FILE_EXTRACT_ERROR : Cannot extract the [chars] version file from [chars] - [chars]
Explanation Package version file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-INVALID_PKG_FILE : The indicated file ([chars]) is not a valid FPD image package file - [chars]
Explanation The file format does not appear to be a valid FPD image package.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-INVALID_PKG_FILE_SIZE : The indicated file ([chars]) does not have a valid FPD image package file size, minimum size = [dec] bytes.
Explanation The file size of the indicated FPD image package does not meet the required minimum size. The file is too small to be a valid FPD image package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-READ_BNDL_HDR_ERROR : Failed to read the FPD bundle header from [chars] file.
Explanation The indicated file might not be a valid FPD image bundle or package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-INVALID_IMAGE_SIZE : The [chars] FPD image from [chars] file does not have a valid image size: expected size = [dec] bytes, actual size = [dec] bytes.
Explanation The size of the indicated FPD image does not have the expected size. The FPD image bundle or package might not be a valid file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the show hw-module subslot fpd, show upgrade fpd table and show upgrade fpd file fpd-pkg-url commands, then contact your technical support representative with the gathered information.


%FPD_MGMT-3-MISSING_DEV_INFO : Could not find [chars] (FPD ID=[int]) in the list of FPD IDs populated for [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-MISSING_BUNDLE_ENTRY : Failed to find a matching entry in the programmable device bundle information table for [chars] in [chars]. Card type or HW version ([int].[int]) might not have FPD support.
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-CLOSE_FAILED : Failed to close [chars] file.
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-UNKNOWN_BNDL_HDR_FORMAT : Unknown header format version: [hex]
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-INVALID_UPGRADE_RESULT : Invalid upgrade result '[int]' received for the FPD image upgrade of [chars] (FPD ID=[int]) for [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-TOO_MANY_FPD_ENTRIES : Too many FPD entries for the FPD Bundle Info Table. Required number of entries = [int], maximum number of entries allowed = [int].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-DUPLICATE_UPGRADE_RESULT : Upgrade result already received for the FPD image upgrade of FPD ID [int] for [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-UPGRADE_LIST_FULL : Could not add a new entry in the FPD Management Upgrade List. No upgrade will be performed for the [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-SW_ERROR : NULL
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-IPC_FAILED : Failed to send IPC message to [chars] in [chars] - [chars]
Explanation The system failed to send a message via IPC to the indicated card. The cause of the specific IPC failure is inicated in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FPD_MGMT-3-PKG_FILE_SEARCH_FAILED : FPD image package ([chars]) cannot be found in system's flash card or disk to do FPD upgrade.
Explanation By default, if the upgrade fpd path fpd-pkg-url global configuration command is not configured, then the system will try to locate the required FPD image package file from removable flash cards or disks that are accessible by the system for FPD upgrade. This message indicates that the system could not find the package file.
Recommended Action Make sure that the indicated FPD image package file is copied into a flash card or disk that is accessible by the system, then restart the FPD upgrade by reinsertion of the target card to the system or use of a system command to reload or power-cycle the target card.


%FPD_MGMT-3-CARD_DISABLED : [chars] card in [chars] is being disabled because of an incompatible FPD image version. Note that the [chars] package will be required if you want to perform the upgrade operation.
Explanation The indicated card contains an incompatible FPD image version, and is being disabled to avoid operational problems with the existing Cisco IOS software. This can happen if the automatic upgrade feature has not been enabled with the upgrade fpd auto global configuration command or if the automatic upgrade operation failed to perform the required upgrade or because it could not find the necessary FPD image package file. The incompatible image will need to be upgraded in order for the system to enable the card.
Recommended Action The FPD image upgrade can be performed automatically by making sure that the automatic upgrade feature is enabled with the upgrade fpd auto global configuration command and the necessary FPD image package file is located in the system's default filesystem (e.g. disk0:) or in a location indicated by the upgrade fpd path directory-url global configuration command. When the automatic upgrade feature is enabled, then the upgrade is triggered by the reinsertion of the card to the system or the use of a system command to reload or power-cycle the target card. Another way to perform the upgrade is through the use of the upgrade hw-module privileged EXEC command. For more information about these commands, refer to the FPD_DOCUMENT_NAME .


%FPD_MGMT-3-PKG_VER_MISMATCH_NOTE : The FPD image package being used ([chars]) is not the right version for this IOS version (it appears that a '[chars]' package was renamed to '[chars]'). An attempt to find the required FPD image will still be performed with this package.
Explanation The indicated FPD image package that is being used in FPD automatic upgrade does not contain the correct version information for the IOS version that is running in the system. This condition can occur if a different version of the FPD image package was renamed to match the filename that the IOS image is expecting to use. The upgrade operation will still be performed by trying to find the required FPD image from the renamed package file.
Recommended Action If the upgrade operation fails because the required FPD image cannot be found with the renamed FPD image package, replace the wrong package file with a valid one and perform the upgrade operation again.


%FPD_MGMT-3-INVALID_IMG_FORMAT : Invalid image format '[chars]' detected for FPD ID=[int].
Explanation The selected FPD image to upgrade the indicated field programmable device does not have the right image format that can be used by the system to perform the upgrade operation.
Recommended Action Please check if the FPD image package used in the upgrade is for the correct platform. This can be checked by using the show upgrade fpd package default privileged EXEC command.


%FPD_MGMT-2-CREATE_FAIL : Couldn't create [chars].
Explanation The system does not have enough free main memory to create the specified resource.
Recommended Action Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note.If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Use the show memory command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, copy the error message exactly as it appears on the console and gather the output of the show tech-support command and contact your technical support representative with this information.


FR

%FR-5-DLCICHANGE : Interface [chars] - DLCI [dec] state changed to [chars]
Explanation The state of the Frame Relay PVC specified by the DLCI changed.
Recommended Action Notification message only. No action required.


%FR-3-BQ_ENQ_ERR : fr_oqueue: Invalid datagramstart [hex] [hex], pak dropped
Explanation A broadcast packet was detected in the Frame Relay output queue that contained an invalid datagram header. The packet has been dropped.
Recommended Action If the router or some features are not operational due to this condition, attempt to disable the Frame Relay broadcast queue by entering the no frame-relay broadcast-queue command in interface configuration mode for a immediate workaround. And LOG_STD_ACTION


%FR-3-BQ_DEQ_ERR : fr_bq_proc: unknown packet on broadcast queue, packet dropped!
Explanation Invalid packet on FR broadcast queue, packet dropped!
Recommended Action If the router or some features are not operational due to this condition, attempt to disable the Frame Relay broadcast queue by entering the no frame-relay broadcast-queue command in interface configuration mode for a immediate workaround. And LOG_STD_ACTION


%FR-3-BQ_DEQ_PTR : fr_br_proc: hdr-[hex] size-[dec] dlci-[hex] [hex] [hex]
Explanation The Frame Relay broadcast queue contains a datagram that is invalid. The packet has been dropped.
Recommended Action Inform Cisco technical support representative


%FR-4-DLCIDELETE : Interface [chars] - DLCI [dec] - PVC use count [dec]
Explanation Trying to remove PVC DLCI while it is still being used.
Recommended Action If this error can be easily recreated, enter the debug frame-relay event command and recreate the condition that caused this error. Copy all the debug messages text and the system message text exactly as it appears on the console or in the system log, enter the show tech-support command, contact your Cisco technical support representative, and provide the representative with the gathered information.


%FR-3-NOMEMORY : No memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%FR-4-NNISUBINTF : Subinterface not supported on Frame Relay NNI
Explanation Trying to change the state of a subinterface on FR NNI.
Recommended Action Reconfigure the Frame Relay link type or remove the subinterface.


%FR-3-FRTSZEROCIR : FRTS: attempt to configure zero CIR
Explanation It should not be possible to configure a zero CIR. To do so would prevent data transmission on the VC.
Recommended Action Inform Cisco technical support representative


%FR-5-CONVERT_ROUTE : Converting route pair to connect
Explanation A pair of Frame Relay routes are being converted to connections.
Recommended Action No action is required.


%FR-3-NULL_PTR_DEREF : Dereferencing NULL pointer [chars]
Explanation Dereferencing a NULL pointer
Recommended Action Inform Cisco technical support representative


%FR-3-MLPOFR_ERROR : MLPoFR not configured properly on Link [chars] Bundle [chars] :[chars]
Explanation The configuration of MLPPP-over-Frame-Relay (MLPoFR) on the FR PVC is either incorrect or incomplete.
Recommended Action Ensure that FRTS has been configured on physical interface and that the service policy has been attached to the Virtual Template. To verify the configuration, use the show running-config serial inteface and show running-config virtual-template commands.


%FR-3-SVC_SETUP : [chars]: interface [chars]: DLCI [dec]
Explanation An error occurred while attempting to setup a Frame-Relay SVC. There may have been an attempt to setup a SVC using a DLCI thats already in use
Recommended Action Check if the DLCI is already in use. For example: A PVC may be configured to use the same DLCI (use <CmdBold>show frame-relay pvc<CmdBold> to verify). If so, please remove the configuration


%FR-3-MFR_UNEXPECTEDEVENT : MFR Timer process error: event table is NULL for event [dec], state [dec]
Explanation The event was ignored because the state transition table is NULL. Normal processing continue.
Recommended Action Please refer to Bug Toolkit on CCO to check for existing bugs. If you need further assistance, please provide 'show version' and 'show running' and any configurations that were being done at the time the message was seen. Copy the message text exactly as it appears on the console or in the system log. Inform Cisco technical support representative, and provide the representative with the gathered information.


%FR-3-FR_PVC_STATUS_Q_CREATE_ERROR : FR PVC status event queue error: failed to create queue
Explanation Unable to create FR PVC status event queue
Recommended Action LOG_STD_ACTION


%FR-3-MAP_DELETE_ERROR : [chars]
Explanation An error occurred while deleting a frame-relay map
Recommended Action LOG_STD_ACTION


%FR-3-FR_INV_OUTPUT_VECTOR : An invalid output vector detected on interface [chars]
Explanation An invalid internal function vector is installed on a Frame Relay interface, which affects the ability of processing outbound traffic on the device.
Recommended Action Remove and re-apply Frame Relay encapsulation on the interface to recover from the error.


FRAG

%FRAG-3-FRAG_STATE_MEM_REQ_FAILED :
Explanation IPC failure occurred when attempting to request more fragment state pool memory.
Recommended Action LOG_STD_ACTION


%FRAG-3-FRAG_STATE_MEM_INIT_FAILED :
Explanation Failure occurred initializing fragment state pool.
Recommended Action LOG_STD_ACTION


%FRAG-3-FRAG_DESC_MEM_REQ_FAILED :
Explanation IPC Failure occurred when attempting to request more fragment descriptor pool memory.
Recommended Action LOG_STD_ACTION


%FRAG-3-FRAG_DESC_MEM_INIT_FAILED :
Explanation Failure occurred initializing fragment descriptor pool.
Recommended Action LOG_STD_ACTION


%FRAG-3-REASSEMBLY_ERR : Reassembly/VFR encountered an error: [chars]
Explanation Reassembly/VFR encountered a runtime error as indicated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FRAG-3-REASSEMBLY_DBG : Reassembly/VFR encountered an error: [chars], [chars] [int], [chars] [int]
Explanation Reassembly/VFR encountered a runtime error as indicated in the message with parameter data for debug
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FRAG-2-UNENABLED : [chars] feature not enabled at interface [chars], packet cannot be processed, MSGDEF_LIMIT_SLOW
Explanation Reassembly or fragmentation feature as indicated not enabled by the control plane. This is a critical problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FRAG-3-INVALID_MTU : [chars] feature failed at interface [chars] due to invalid L3 MTU [int], MSGDEF_LIMIT_SLOW
Explanation Fragmentation was not able to be performed due to invalid adj L3 MTU given by the control plane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%FRAG-3-INVALID_QFP_NO : Invalid qfp device no.: [chars]
Explanation Invalid qfp device no.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FRAG_DESC_PROXY through GBIC_SECURITY

FRAG_DESC_PROXY

%FRAG_DESC_PROXY-3-PROXY_IPC_FRAG_MEM_INIT_FAILED :
Explanation Initialization of fragment descriptor pool failed.
Recommended Action LOG_STD_ACTION


%FRAG_DESC_PROXY-3-PROXY_IPC_VFR_MEM_INIT_FAILED :
Explanation Initialization of vFR state pool failed.
Recommended Action LOG_STD_ACTION


%FRAG_DESC_PROXY-3-PROXY_IPC_FRAG_MEM_EXTEND_FAILED :
Explanation Increasing of fragment descriptor pool failed.
Recommended Action LOG_STD_ACTION


%FRAG_DESC_PROXY-3-PROXY_IPC_VFR_MEM_EXTEND_FAILED :
Explanation Increasing of vFR state pool failed.
Recommended Action LOG_STD_ACTION


%FRAG_DESC_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Invalid IPC message subtype.
Recommended Action LOG_STD_ACTION


%FRAG_DESC_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


FRR_OCE

%FRR_OCE-3-GENERAL : [chars]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-3-NULLPOINTER : [chars]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-3-INVALIDPAR : Parent OCE [IPV6 address]([chars]) is [chars]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-3-INVALID_ADDRTYPE : addrtype to xdr: [dec] [dec]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-3-INVALID_BFD_HNDL : [chars] bfd notification handle is [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-3-INVALID_BFD_EVT : Error in BFD event retrieval bfd notification handle is [IPV6 address], session handle is [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-3-INVALID_BFD_SESSION : BFD session db node mismatch: bfd context db node is [IPV6 address], frr db node is [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-3-ERROR_BFD_SESSION : [chars]BFD returned [dec] node [IPV6 address] handle [IPV6 address] interface [dec]
Explanation An internal software error occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release.


%FRR_OCE-4-INVALID_BACKUP_OCE : Invalid backup oce is found because interface [int] is removed or reloading
Explanation The interface or line card is reloading or removed.
Recommended Action Check whether the line card is present and the interface is up.


%FRR_OCE-4-NULL_PRIMARY_OCE : [chars]
Explanation The interface or line card is reloading or pulled off.
Recommended Action Check whether the line card is in online and the interface is up.


%FRR_OCE-5-ISSULOG : FRR is not ISSU compatible, notified by [chars]
Explanation ISSU negotation results for FRR not compatible
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


FR_ELMI

%FR_ELMI-3-INCORRECT_ID : Incorrect ID
Explanation Incorrect ID in QOS parameter message.
Recommended Action


%FR_ELMI-3-INCORRECT_IE : Incorrect IE
Explanation Enhanced LMI is not configured on the interface. The frame was dropped.
Recommended Action


FR_FRAG

%FR_FRAG-3-BADPAK : Inconsistent packet: size [dec], linktype [chars], input [chars], output [chars]
Explanation A packet being fragmented has inconsistent size and data
Recommended Action Inform Cisco technical support representative


FR_HA

%FR_HA-3-SYNC : [chars]: code [dec]
Explanation An error occurred when syncing Frame Relay state to the Standby Route Processor. This may affect Non-Stop Forwarding capability on Frame Relay interfaces during and after switchover until the state is recovered through normal protocol operation.
Recommended Action Reset the standby processor to attempt the sync again. LOG_STD_RECUR_ACTION


%FR_HA-3-ISSU : [chars]: [chars]
Explanation A Frame Relay ISSU error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


FR_LMI

%FR_LMI-3-INCORRECT_IE : Enhanced LMI not configured, incorrect IE
Explanation An unexpected LMI information element has been received.
Recommended Action Verify the configuration for enhanced LMI on the switch matches the c onfiguration on the router.


%FR_LMI-3-MSG_TOO_BIG : [chars] ([chars]) Status message too big, status of PVCs with dlci values from [dec] will not be reported.
Explanation LMI STATUS message size is too big to fit into interface MTU.
Recommended Action LMI type - cisco - does not support segmentation of STATUS message, so either increase the interface MTU or use LMI types - ansi or q933a.


FR_VCB

%FR_VCB-3-PROCESS_SWITCHING : Switching error - vcb [chars] - [chars]
Explanation An error occurred while switching packet(s) across vc-bundle
Recommended Action As a workaround, delete the vc-bundle and employ a PVC to substitute for the vc-bundle


%FR_VCB-3-FIBSW_MISSING_TABLE_ENTRY : FIB switching error - vc-bundle [chars]
Explanation An error occurred while FIB switching packet(s) across vc-bundle
Recommended Action As a workaround, delete the vc-bundle and employ a PVC to substitute for the vc-bundle


%FR_VCB-3-CONFIG : Configuration error - vcb [chars] - [chars]
Explanation An error occurred while interpreting vc-bundle configuration
Recommended Action Try reconfiguring the vc-bundle


%FR_VCB-3-BUMPING : Bumping error - vcb [chars] - [chars]
Explanation An error occurred while bumping traffic in a vc-bundle
Recommended Action As a workaround, reconfigure the vc-bundle to avoid bumping


%FR_VCB-5-UPDOWN : FR VC-Bundle [chars] changed state to [chars]
Explanation The state of a frame-relay vc-bundle changed to up/down
Recommended Action Notification message only. No action required


%FR_VCB-3-ADJ_SRC_ERROR : Error sourcing adjacency - vc-bundle [chars] dlci [dec]
Explanation An error occurred while setting up the adj for a member pvc
Recommended Action Try reconfiguring the vc-bundle


FW

%FW-4-ALERT_ON : [chars][chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the max-incomplete high threshold of half-open connections or the new connection initiation rate has been exceeded. This error message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is issued only when the max-incomplete high threshold is crossed.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%FW-4-ALERT_OFF : [chars][chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the number of half-open connections or the new connection initiation rate has gone below the max-incomplete low threshold. This message indicates that the rate of incoming new connections has slowed down and is issued only when the max-incomplete low threshold is crossed.
Recommended Action This message is for informational purposed only, but may indicate that an attack has stopped.


%FW-4-HOST_TCP_ALERT_ON : [chars]Max tcp half-open connections ([dec]) exceeded for host [IP_address].
Explanation The max-incomplete host limit of half-open TCP connections has been exceeded. This message indicates that a high number of half-open connections is coming to the protected server, and may indicate that a SYN flood attack is in progress and is targeted to the specified server host.
Recommended Action This message is for informational purposes only, but may indicate that a SYN flood attack was attempted. If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a lot of legitimate traffic coming in to that server. In this case, the max-incomplete host parameter should be set to a higher number to avoid false alarms.


%FW-2-BLOCK_HOST : [chars]Blocking new TCP connections to host [IP_address] for [dec] minute[chars] (half-open count [dec] exceeded).
Explanation This message indicates that any subsequent new TCP connection attempts to the specified host will be denied because the max-incomplete host threshold of half-open TCP connections is exceeded, and the blocking option is configured to block the subsequent new connections. The blocking will be removed when the configured block-time expires.
Recommended Action This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.


%FW-4-UNBLOCK_HOST : [chars]New TCP connections to host [IP_address] no longer blocked
Explanation New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted.
Recommended Action This message is for informational purposed only, but may indicate a SYN flood attack was attempted to the host.


%FW-3-NOTFOUND : [chars]Session context for ([IP_address]:[dec]) => ([IP_address]:[dec]) not found.
Explanation The CBAC code was searching its database for information for a particular inspection session, but this information was not found.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.


%FW-6-SESS_AUDIT_TRAIL_START : [chars]Start [chars] session: initiator ([IP_address]:[dec]) -- responder ([IP_address]:[dec])
Explanation This message documents the opening of an inspection session. The message is issued at the start of each inspected session and it records the source/destination addresses and ports.
Recommended Action This message is for informational purposed only, and can be used to collect the basic accounting for inspected sessions.


%FW-6-SESS_AUDIT_TRAIL : [chars]Stop [chars] session: initiator ([IP_address]:[dec]) sent [int] bytes -- responder ([IP_address]:[dec]) sent [int] bytes
Explanation This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source/destination addresses and ports, as well as the number of bytes transmitted by the client and server.
Recommended Action This message is for informational purposed only, and can be used to collect the basic accounting for the inspected sessions.


%FW-3-FTP_SESSION_NOT_AUTHENTICATED : [chars]Command issued before the session is authenticated -- FTP client [IP_address] FTP server [IP_address]
Explanation An FTP client attempted to use the PORT command or an FTP server attempted to use the response to a PASV command to open a data channel in the firewall prior to the client's successful authentication with the server. This is a suspicious attempt by the client/server to trick the firewall into opening a hole so that outside attackers can take advantage of the firewall opening. This message indicates that a suspicious violation was detected, and the PORT or PASV command/response is rejected by the firewall. The data channel in the firewall will not be opened until the authentication is done successfully.
Recommended Action This message is for informational purposes only, but may indicate that an illegal attempt was made to modify the firewall security policy.


%FW-3-FTP_PRIV_PORT : [chars]Privileged port [dec] used in [chars] -- FTP client [IP_address] FTP server [IP_address]
Explanation An FTP client attempted to use a PORT command or the FTP server attempted to use the response to a PASV command to trick the firewall into opening access to a privileged port. This message indicates that a suspicious violation was detected from the FTP client/server attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate that an attempt was made to gain access to privileged ports.


%FW-3-FTP_NON_MATCHING_IP_ADDR : [chars]Non-matching address [IP_address] used in [chars] -- FTP client [IP_address] FTP server [IP_address]
Explanation An FTP client attempted to use a PORT command or the FTP server attempted to use the response to a PASV command to trick the firewall into opening access to a third-party host that is different from the two hosts engaged in the FTP connection. This message indicates that a suspicious violation was detected while attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate that an attempt was made to grant or open access to unauthorized hosts.


%FW-3-SMTP_INVALID_COMMAND : [chars]Invalid SMTP command ([chars])(total [dec] chars) from initiator ([IP_address]:[dec])
Explanation The CBAC code detected an invalid SMTP command in the inspected SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-3-SMTP_UNSUPPORTED_PARAMETER : [chars]Unsupported SMTP parameter ([chars]) from initiator ([IP_address]:[dec])
Explanation The CBAC code detected an invalid/unsupported parameter in an SMTP command. The parameter ''data size'' means that the initiator is trying to send a huge data which is more than the default or configured firewall threshold (max-data). The parameter ''@ or # to ETRN'' means that the initiator is trying to send an invalid ETRN command.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-3-HTTP_JAVA_BLOCK : [chars]JAVA applet is blocked from ([IP_address]:[dec]) to ([IP_address]:[dec]).
Explanation A Java applet was seen in the HTTP channel, and the firewall configuration indicates that the applet from this Web site should be prohibited. The message indicates that the applet is being downloaded from one of the prohibited sites and its entrance to the protected network is not allowed. The connection is reset and the transmission of the detected applet is aborted immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-4-TCP_SENDMAIL_BAD_TO_SIG : [chars]Sendmail Invalid Recipient - from [IP_address] to [IP_address]
Explanation Triggers on any mail message with a ' 'pipe'' (|) symbol in the recipient field.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.


%FW-4-TCP_SENDMAIL_BAD_FROM_SIG : [chars]Sendmail Invalid Sender - from [IP_address] to [IP_address]
Explanation Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.


%FW-4-TCP_SENDMAIL_OLD_SIG : [chars]Archaic Sendmail Attacks - from [IP_address] to [IP_address]
Explanation Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.


%FW-4-TCP_SENDMAIL_DECODE : [chars]Sendmail Decode Alias - from [IP_address] to [IP_address]
Explanation Triggers on any mail message with '': decode@'' in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.


%FW-4-TCP_MAJORDOMO_EXEC_BUG : [chars]Majordomo Execute Attack - from [IP_address] to [IP_address]
Explanation A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.


%FW-4-TCP_SENDMAIL_INVALID_COMMAND : [chars]Invalid SMTP command - [IP_address] to [IP_address]
Explanation Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.
Recommended Action This is unusual traffic and may warrantinvestigation.


%FW-6-PRE_ALLOCATED_MEDIA_CHANNEL : [chars]Pre-Allocated [chars] channel from [IP_address][[dec]:[dec]] to [IP_address][[dec]:[dec]]
Explanation CBAC inspection has pre-allocated data-structures and created ACEs to allow the data/media traffic to flow through the Firewall.
Recommended Action This message is for informational purposes only. It may be used to verify whether data/media sessions are being created.


%FW-4-SKINNY_INSPECTION_DISABLED : Skinny Inspection Disabled; Error = [chars]
Explanation Skinny inspection is disabled due to internal errors and hence firewall will not inspect any Skinny protocol traffic. This will be caused when firewall does not have enough memory to allocate initial skinny data-structures.
Recommended Action Verify the memory usage to see if any process has used large amounts of memory and see if any corrective action can be taken for it. Otherwise, upgrade the memory. In any case, the firewall/router needs to be restarted to enable Skinny inspection.


%FW-6-INIT : Firewall inspection startup completed; beginning operation.
Explanation Firewall inspection is configured on at least one interface in the startup config.
Recommended Action This message is for informational purposes only. It may be used to verify whether firewall inspection is on at startup.


%FW-6-DROP_PKT : Dropping [chars] pkt [IP_address]:[int] => [IP_address]:[int]
Explanation Packet dropped by firewall inspection.
Recommended Action This message is for informational purposes only. It may be used to verify that packets were dropped by the firewall.


%FW-5-POP3_INVALID_COMMAND : [chars]Invalid POP3 command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected an invalid POP3 command in the inspected POP3 connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-5-POP3_NON_SECURE_LOGIN : [chars]LOGON POP3 command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected a cleartext logon attempt in the inspected POP3 connection while secure-login is configured. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-5-IMAP_INVALID_COMMAND : [chars]Invalid IMAP command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected an invalid IMAP command in the inspected IMAP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-5-IMAP_NON_SECURE_LOGIN : [chars]LOGON IMAP command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected a cleartext logon attempt in the inspected IMAP connection while secure-login is configured. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-4-SESSION_THRESHOLD_EXCEEDED : [chars]Number of sessions for the firewall rule '[chars]' applied on interface '[chars]' exceeds the configured threshold [dec]
Explanation This message indicates that the number of established CBAC sessions have crossed the configured threshold.
Recommended Action This message is for informational purpose only, but may indicate a security problem. This might also mean that the session threshold is set to a low value, in which case the threshold value could be increased through CLI command


%FW-5-EMAIL_DROP_FRAGMENT : [chars]Dropping [chars] command fragment from initiator ([IP_address]:[dec])
Explanation The CBAC code detected a pipelined POP3/IMAP command fragment, in the inspected POP3 connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The fragment is dropped by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.


%FW-3-INTERNAL_ERROR : IP Firewall internal failure -- [chars]
Explanation This message indicates the misc errors in the IP FW subsystem
Recommended Action This message indicates the misc errors in the IP FW subsystem


%FW-3-TIMER_WHEEL_INIT_FAILED : Timer Wheel initialization failed
Explanation This message indicates that Timer Wheel initialization is failed in the FW subsystem
Recommended Action This message indicates a series problem with IOS Firewall. On seeing this error message, copy the message exactly as it appears, and report it to your technical support representative.


%FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE : Dropping packet - Invalid Window Scale option for session [IP_address]:[dec] to [IP_address]:[dec] (Initiator scale [int] Responder scale [int])
Explanation Firewall detected the packet from Responder to Initiator has windows scaling option but did not have the scaling option in the SYN packet from Initiator to responder. This is an error according to RFC 1323
Recommended Action Turn on window scaling option on both Initiator and Responder,or Turn off window scaling on the Responder


FWALL_PROXY

%FWALL_PROXY-3-PROXY_SCB_MEM_INIT_FAILED :
Explanation Initialization of session control block pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_ICMP_ERROR_MEM_INIT_FAILED :
Explanation Initialization of ICMP Error control block pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_SCB_MEM_EXTEND_FAILED :
Explanation Increasing of session control block pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_ICMP_ERROR_MEM_EXTEND_FAILED :
Explanation Increasing of ICMP Error pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HA_MEM_INIT_FAILED :
Explanation Initialization of ha retry pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HA_MEM_EXTEND_FAILED :
Explanation Increasing of ha retry pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HOSTDB_MEM_INIT_FAILED :
Explanation Initialization of host database pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HOSTDB_MEM_EXTEND_FAILED :
Explanation Increasing of host database pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_TEARDOWN_MEM_INIT_FAILED :
Explanation Initialization of teardown pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_TEARDOWN_MEM_EXTEND_FAILED :
Explanation Increasing of teardown pool failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_FWALL_INIT_FAILED : [dec]
Explanation Firewall initialization failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_SEND_INIT_FAILED : [chars] [dec]
Explanation IPC failed to reply for firewall initialization status.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_FAILED : [chars] [dec]
Explanation IPC message allocation for firewall failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_TBL_INIT_FAILED : [chars]
Explanation Failed to initialize table.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_SEND_STATS_FAILED : [dec]
Explanation IPC send failed to reply for firewall status.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_SEND_SESSION_FAILED : [dec]
Explanation IPC send failed to reply for firewall session query.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_SEND_CLEAR_FAILED : [dec]
Explanation IPC send failed to reply for firewall session clear.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_SEND_DEBUG_FAILED : [dec]
Explanation IPC send failed to reply for firewall session debug.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_SEND_SCB_QUERY_FAILED : [dec]
Explanation IPC send failed to reply for firewall scb query.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Invalid IPC message subtype.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_ALLOC_FAILED : [int]
Explanation IPC allocation failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_SEND_FAILED : [int]:[chars]
Explanation IPC send failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HSL_CREATE_FAILED :
Explanation HSL creation failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HSL_ADD_DEST_FAILED :
Explanation HSL add destination failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HSL_BIND_FAILED :
Explanation HSL bind failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HSL_ENABLE_FAILED :
Explanation HSL enable failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HSL_BIND_TEMPLATE_FAILED : [dec]
Explanation HSL bind tempalte failed at given index.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-4-PROXY_HSL_ALREADY_INIT :
Explanation HSL logger already initialized
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-4-PROXY_HSL_NOT_INIT : [int]
Explanation HSL logger not initialized
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HSL_MODIFY_FAILED :
Explanation HSL modification failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_HSL_MODIFY_DEST_FAILED :
Explanation HSL modify destination failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-4-PROXY_IPC_UNINIT_POOL_FAILED : [chars]: [dec]
Explanation Could not destroy chunk pool
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-4-PROXY_UNINIT_SESSIONS : in use [int] [int]
Explanation Not all sessions freed
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_IPC_ERM_CONF_CHANGE_FAILED : [dec]
Explanation FW IPC send failed to reply for event rate monitoring configuration change.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_DEBUG_REG_FAILED : [dec]
Explanation FW Conditional Debugging registration failed.
Recommended Action LOG_STD_ACTION


%FWALL_PROXY-3-PROXY_FWALL_VFR_REG_FAILED : [chars] err: [dec]
Explanation FW VFR registration failed.
Recommended Action LOG_STD_ACTION


GBIC_SECURITY

%GBIC_SECURITY-4-GBIC_INTERR : Internal error occurred in setup for GBIC interface [chars]
Explanation The system could not allocate resources, or had some other problem, in the setup for the specified GBIC interface.
Recommended Action Reload the system. If the problem persists, contact TAC.


%GBIC_SECURITY-4-EEPROM_READ_ERR : Error in reading GBIC serial ID in [chars]
Explanation Error when reading GBIC type from EEPROM
Recommended Action Please remove GBIC from this Port


%GBIC_SECURITY-4-EEPROM_CRC_ERR : EEPROM checksum error for GBIC in [chars]
Explanation The GBIC in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.


%GBIC_SECURITY-4-EEPROM_SECURITY_ERR : GBIC in [chars] failed security check
Explanation The GBIC in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.


Was this Document Helpful?

FeedbackFeedback

Contact Cisco