System Error Messages Guide For Access and Edge Routers, Cisco IOS XE Gibraltar 16.10.1

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

Results

Updated:
July 5, 2019

Chapter: ESS_IPSUB through HL_MGR

ESS_IPSUB through HL_MGR

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 EVUTIL

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.


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

%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 https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://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 https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


EXTASSIGNER through FED_PM

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.


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

%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_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-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 through FILESYS_RFS

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

%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 through FMANRP_DPSS

FILTER

%FILTER-3-EWLC_APFILTER_REGEX_CREATE_ERR : Error in [chars]Error in [chars]
Explanation General Wireless LAN Controller Error Message.APFilter regular expression error
Recommended Action Recreate regular expression correctly


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

%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 through FMANRP_SC

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

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