ENVIRONMENTAL through ESS_FEATURE
ENVIRONMENTAL
%ENVIRONMENTAL-3-TDLERROR : Error processing TDL message. [dec] | |
---|---|
Explanation | An unexpected condition in which IOS has received a TDL message which it can not process. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%ENVIRONMENTAL-1-ALERT : [chars], Location: [chars], State: [chars], Reading: [dec] [chars] | |
---|---|
Explanation | One of the sensors in the system is reading an out of normal value. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%ENVIRONMENTAL-6-NOTICE : [chars], Location: [chars], State: [chars], Reading: [dec] [chars] | |
---|---|
Explanation | Informational message on the sensor reading |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%ENVIRONMENTAL-5-SENSOROK : [chars], Location: [chars], State: normal | |
---|---|
Explanation | One of the sensors in the system had been in a failure condition but is now operating normally. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%ENVIRONMENTAL-1-SENSORFAIL : [chars], Location [chars], State: fail | |
---|---|
Explanation | One of the sensors in the system has detected a failure condition from which it can not recover. This sensor is no longer reporting readings to the environmental monitoring subsystem. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%ENVIRONMENTAL-3-CHASFSERR : Sensor [chars] on FRU [chars] has an invalid chasfs device state [chars] | |
---|---|
Explanation | The system does not understand the state that the sensor is reporting. This is most likely a filesystem corruption or ISSU problem. You may try rebooting the router to see if the problem corrects itself. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%ENVIRONMENTAL-6-INFO : [chars] | |
---|---|
Explanation | Informational message of ambient sensor reading |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
ENVM
%ENVM-3-NOFORK : Could not create environmental polling process | |
---|---|
Explanation | |
Recommended Action |
%ENVM-4-READERROR : Error reading temperature sensor [dec] | |
---|---|
Explanation | |
Recommended Action |
%ENVM-4-LONGBUSYREAD : C2W Interface busy for long time reading temperature sensor [dec] | |
---|---|
Explanation | |
Recommended Action |
%ENVM-4-WRITEERROR : Error writing temperature sensor [dec] | |
---|---|
Explanation | |
Recommended Action |
%ENVM-4-LONGBUSYWRITE : C2W Interface busy for long time writing temperature sensor [dec] | |
---|---|
Explanation | |
Recommended Action |
EPBR_PROXY
%EPBR_PROXY-2-EPBR_MSG_PROXYINIT_FAILURE : EPBR - Failed to register IPC message handler, result code [int] | |
---|---|
Explanation | QFP EPBR feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%EPBR_PROXY-3-EPBR_MSG_PROXY_UNKNOWN_IPCMSG : EPBR - Received an unknown type (code [int]), IPC message | |
---|---|
Explanation | QFP EPBR feature received an unknown message from another layer of EPBR feature's software stack. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%EPBR_PROXY-3-EPBR_MSG_PROXY_INVALID_MSGLEN : EPBR - Received an invalid length IPC message | |
---|---|
Explanation | QFP EPBR feature received an incorrect length of IPC message from anoter layer of EPBR feature's software stack, m_enum %d, m_subtype %d, m_len %d, m_flags 0x%x, m_source %d. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%EPBR_PROXY-3-EPBR_MSG_PROXY_ALLOC_FAILURE : EPBR - Failed to get [int] bytes space for IPC reply message | |
---|---|
Explanation | QFP ET-Anallytics feature detected buffer allocation failure while sending reply to a message from another layer of EPBR feature's software stack. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%EPBR_PROXY-3-EPBR_MSG_PROXY_OPENREPLY_FAIL : EPBR - Failed to open reply message part of IPC packet | |
---|---|
Explanation | QFP EPBR feature failed to open message part of IPC packet while sending a reply to another layer of EPBR feature's software stack. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%EPBR_PROXY-3-EPBR_MSG_PROXY_IPCSEND_FAIL : EPBR - Failed to send IPC message, result code [dec] | |
---|---|
Explanation | QFP EPBR feature failed to send IPC message to another layer of EPBR feature's software stack. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%EPBR_PROXY-3-EPBR_MSG_PROXY_DEBUG_REG_FAILED : | |
---|---|
Explanation | EPBR Conditional Debugging Registration failed. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%EPBR_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec] | |
---|---|
Explanation | Invalid EPBR IPC message length. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
EPC
%EPC-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for EPC | |
---|---|
Explanation | EPC Initialization of channel pool failed. |
Recommended Action | LOG_STD_ACTION |
%EPC-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for EPC | |
---|---|
Explanation | EPC Initialization of packet replication registration failed. |
Recommended Action | LOG_STD_ACTION |
EPM
%EPM-6-POLICY_REQ : | |
---|---|
Explanation | This message indicates that a policy application/remove request has been received by the EPM |
Recommended Action | No action required |
%EPM-6-POLICY_APP_SUCCESS : | |
---|---|
Explanation | This message indicates that the displayed policy for the client has been applied successfully by the EPM |
Recommended Action | No action required |
%EPM-4-POLICY_APP_FAILURE : | |
---|---|
Explanation | This message indicates that the displayed policy for the client could not be applied by the EPM |
Recommended Action | Policy application failure could happen due to multiple reasons.The reason for the failure is notified to the client and the client has to take appropriate action based on it |
%EPM-6-AAA : | |
---|---|
Explanation | This message indicates a download request has been sent/downloaded successfully for the specified dACL |
Recommended Action | No action required |
%EPM-4-ACL_CONFIG_ERROR : | |
---|---|
Explanation | This message indicates that adding an ACE to the specified ACL was ignored because of wrong configuration |
Recommended Action | Change ACE configuration for the specifed ACL |
%EPM-6-IPEVENT : | |
---|---|
Explanation | This message indicates the IP event Wait/Release/Assignment that has occured with respect to the specified host |
Recommended Action | No action required |
%EPM-6-AUTH_ACL : | |
---|---|
Explanation | his message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been applied or removed |
Recommended Action | No action required |
EPM_PLUGIN
%EPM_PLUGIN-5-ERR_VLAN_NOT_FOUND : | |
---|---|
Explanation | An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VTP database. |
Recommended Action | Make sure the VLAN exists and is not shutdown or use another VLAN. |
EPOCH
%EPOCH-6-EPOCH_REJECTED : Peer [chars] has rejected epoch: [chars] | |
---|---|
Explanation | This error occurs if epoch from shell-manager has been rejected by the peer. |
Recommended Action | Check the epoch and peer state. |
ERM
%ERM-6-NOTIFY : Owner: [chars](%0llx), User: [chars](%0llx), Threshold Type: [chars], Level: [chars], Direction: [chars], Limit: [int], Usage: [int], Policy ID: [dec] | |
---|---|
Explanation | A notification has been sent out by the resource owner because of a threshold violation. |
Recommended Action | This is just informational message only. This message appears because a threshold has been violated. Do 'show runnning' and look for the configuration under the mode 'resource manager' and check the thresholds that has been set. This is just a notification that the threshold has been violated - nothing to stop the resource exhaustion is being done here. |
ERSPAN
%ERSPAN-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for ERSPAN | |
---|---|
Explanation | ERSPAN Initialization of channel pool failed. |
Recommended Action | LOG_STD_ACTION |
%ERSPAN-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for ERSPAN | |
---|---|
Explanation | ERSPAN Initialization of packet replication registration failed. |
Recommended Action | LOG_STD_ACTION |
ESS_FEATURE
%ESS_FEATURE-3-ESF_STUB : CPP ESS per-session feature ([chars]) executes stub entry in [chars] direction | |
---|---|
Explanation | Cisco internal software error. CPP ESS per-session feature stub entry got executed. The packet will be dropped. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%ESS_FEATURE-4-ESF_DROP_POLICY : CPP ESS feature encounted unexpected linktype=[dec] | |
---|---|
Explanation | Cisco internal software error. CPP ESS per-session feature encounted unexpected linktype when executing output drop policy |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |