System Message Guide for Cisco IOS XE 17.15.x
Cisco System Messages Overview
This document describes system messages for Cisco software releases. During operation, the system software sends these messages to the console (and, optionally, to a logging server on another system) during operation. Not all system messages indicate problems with your system. Some are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software.
How To Read System Error Messages
System error messages begin with a percent sign (%) and are structured as follows:%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text
-
FACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software.
-
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 1 lists the severity levels.
-
MNEMONIC is a code that uniquely identifies the error message.
-
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets (
[ ]
). A decimal number, for example, is represented as[dec]
. Table 2 lists the representations of variable fields and the type of information in them.
The following is a sample system error message:
%LINK-2-BADVCALL: Interface [chars], undefined entry point
Some error messages also indicate the card and slot reporting the error. These error messages begin with a percent sign (%) and are structured as follows:
%CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-text
-
CARD is a code that describes the type of card reporting the error. VIP and FEIP are possible card types.
-
MSG is a mnemonic that indicates that this is a message. It is always shown as MSG.
-
SLOT indicates the slot number of the card reporting the error. It is shown as SLOT followed by a number (for example, SLOT5).
The prepended portion of the error message (%CARD-SEVERITY-MSG:SLOT) is not shown in the error message listings in this document.
Error Message Severity Levels
Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default is to log messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the configuration guide and command reference.
Level |
Description |
---|---|
0 - emergency |
System unusable |
1 - alert |
Immediate action needed |
2 - critical |
Critical condition |
3 - error |
Error condition |
4 - warning |
Warning condition |
5 - notification |
Normal, but significant, condition |
6 - informational |
Informational message only |
7 - debugging |
Appears during debugging only |
Representation of Variable Fields in Error Messages
Representation |
Type of Information |
---|---|
[atalk_address] |
AppleTalk address |
[atalk_net] |
AppleTalk network, either 600 or 600-601 |
[char] |
Single character |
[chars] |
Character string |
[dec] |
Decimal number |
[enet] |
Ethernet address (for example, 0000.FEED.00C0) |
[hex] |
Hexadecimal number |
[inet] |
Internet address (for example, 10.0.2.16) |
[int] |
Integer number |
[node] |
Address or node name |
[sci_notation] |
Scientific notation |
[t-line] |
Terminal line number in octal (or decimal if the decimal-TTY service is enabled) |
[v-name] |
VINES name; or number (hex or decimal) |
Error Message Traceback Reports
Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.
The following sample message includes traceback information:
-Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860
System and Error Messages in Cisco IOS XE 17.15.x
The following tables list system and error messages and recommended actions. Scroll right to see the Recommendation Action. Alternatively, you can download the system and error messages in the excel format here: System Message Guide for Cisco IOS XE 17.15.x.
A to E
Facility-Severity-Mnemonic |
Severity-Meaning |
Message |
Message-Explanation |
Component |
Recommended-Action |
---|---|---|---|---|---|
AAA_AUDIT_MESSAGE-6-METHOD_LIST_STATE |
6-Information |
mlist [chars] of [chars] service is marked for notifying state and its current state is : [chars] |
Method list state change |
polaris-aaa |
LOG_STD_NO_ACTION |
AAA_AUDIT_MESSAGE-6-NOTIFY_MLIST_STATE_TO_AAA_CLIENT |
6-Information |
Notifying state of [chars] method list [chars] of [chars] service as [chars] |
Method list state change notified to AAA CLIENT |
polaris-aaa |
LOG_STD_NO_ACTION |
ACCESS_SESSION_TRACE-3-TRACE_INIT_FAIL |
3-Error |
Access session trace initialization failed with code: [dec]. |
Failed to initialize access-session trace. |
polaris-smd |
Review smd 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. |
ACCESS_SESSION_TRACE-3-TRACE_REG_FAIL |
3-Error |
Component [chars] registration failed. Error code: [dec] |
Component failed to register with access-session trace |
polaris-smd |
Review smd 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. |
ACLMGR_MESSAGE-3-ACL_LEN_ERR |
3-Error |
Error in [chars] |
ewlc ACL flex push error message. |
iosxe-binos-utils |
LOG_STD_ACTION |
ACL_ERRMSG-3-CHANGE_ERROR |
3-Error |
[chars] [chars] [chars] ACL [chars] change configuration could not be updated on all installed interfaces.\n |
The given ACL change configuration could not be applied to all installed policies in hardware. |
INVALID |
Find out more about the error by using the show platform software trace messages fed command. |
ACL_ERRMSG-3-ERROR |
3-Error |
[chars] [chars] [chars] ACL [chars] configuration could not be applied on [chars].\n |
The given ACL configuration could not be applied to hardware. |
INVALID |
Find out more about the error by using the show platform software trace messages fed command. |
ACL_ERRMSG-3-SGACL_ERROR |
3-Error |
SGACL configuration could not be changed on [chars].\n |
An error occurred during SGACL configuration change, all SGACLs have been removed from cell. |
INVALID |
User needs to manually remove the cell configuration and attempt to re-apply when resources have been freed. |
ACL_ERRMSG-4-ACLTCAM_FULL |
4-Warning |
[chars] [chars] [chars] ACL on [chars] could not be programmed in hardware, ACL TCAM is full.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of ACL TCAM, use a simpler configuration which uses less ACL entries.\n |
ACL_ERRMSG-4-DGT_FULL |
4-Warning |
[chars] [chars] [chars] ACL on [chars] could not be programmed in hardware, DGT ID table is full.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of DGT, use a simpler configuration which uses less DGT entries.\n |
ACL_ERRMSG-4-HASH_ERROR |
4-Warning |
[chars] [chars] [chars] ACL on cell [chars] could not be found.\n |
The configuration is unknown. |
INVALID |
There is no SGACL Cell with this configuration found.\n |
ACL_ERRMSG-4-HASH_FULL |
4-Warning |
[chars] [chars] [chars] ACL on cell [chars] could not be programmed in hardware, SGACL table is full.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of SGACL cells, use a simpler configuration which uses less SGACL cells.\n |
ACL_ERRMSG-4-HASH_ZERO |
4-Warning |
[chars] [chars] [chars] ACL on cell [chars] could not be programmed in hardware, sgt or mpls-vpn hash size is zero.\n |
Cannot configure in hardware due to zero sgt or mpls-vpn hash entries. |
INVALID |
Allocate hash entries to sgt or mpls-vpn using custom template.\n |
ACL_ERRMSG-4-POLICYLABEL_FULL |
4-Warning |
[chars] [chars] [chars] ACL on [chars] could not be programmed in hardware, Policy Label table is full.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of the number of Policies, use a simpler configuration which uses less Policy entries.\n |
ACL_ERRMSG-4-PROGRAM_FAILED |
4-Warning |
[chars] [chars] [chars] ACL on [chars] programming failed in hardware.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of entries, use a simpler configuration which uses less entries.\n |
ACL_ERRMSG-4-SIS_STATS_FULL |
4-Warning |
Policy id [dec] could not be programmed in hardware, SIS stats table is FULL.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of hardware resources, use a simpler configuration which uses less resources.\n |
ACL_ERRMSG-4-UNLOADED |
4-Warning |
[chars] [chars] [chars] ACL on interface [chars] could not be programmed in hardware and traffic will be dropped.\n |
The configuration is too large; dropped will be dropped on this interface. |
INVALID |
Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. If possible, use the same ACLs on multiple interfaces.\n |
ACL_ERRMSG-6-GACL_INFO |
6-Information |
Logging is not supported for GACL.\n |
The ACL logging is not supported for client/group ACL. |
INVALID |
No action is needed. |
ACL_ERRMSG-6-PACL_INFO |
6-Information |
Logging is not supported for PACL.\n |
The ACL logging is not supported on port interface. |
INVALID |
No action is needed. |
ACL_ERRMSG-6-RELOADED |
6-Information |
[chars] [chars] [chars] ACL on interface [chars] has now been loaded into the hardware.\n |
The configuration that previously was unable to fit into the hardware will now fit and has been programmed for this interface. |
INVALID |
No action required, informational only.\n |
ACL_ERRMSG-6-REMOVED |
6-Information |
The [chars] [chars] [chars] ACL configuration that was previously unloaded has been removed from interface [chars].\n |
The configuration that was previously unloaded, because of lack of space, has been removed. |
INVALID |
No action required, informational only. |
ACL_ERRMSG-6-THRESHOLD_EVENT |
6-Information |
The [chars] threshold alarm state is [chars] for switch [dec] asic [dec]; with [dec] entries used and [dec] entries remaining.\n |
The configuration exceeds the threshold, because of lack of space. |
INVALID |
No action required, informational only. |
ADMINTECH-3-INCOMPLETE_BUNDLE |
3-Error |
Admin-tech bundle is incomplete, IOS tech-support timed out after [dec] seconds |
This syslog is generated IOS tech-support times out resulting into incomplete admin-tech. Default timeout for admin-tech is 30 mins, however on loaded systems, this timeout might not be sufficient and admin-tech could potentially time out |
cedge-admintech |
Increase the timeout value for admin-tech with 'request platform software sdwan admin-tech timeout <> |
ADMINTECH-3-PUBLISH_FAILURE |
3-Error |
Admin-tech bundle [chars] could not be uploaded to Cisco SD-WAN Manager, reason: [chars] ([dec]) |
This error syslog is generated when admin-tech can not be published to SD-WAN Manager over over HTTP channel. This can be due to degration in the network or control connectivity loss |
cedge-admintech |
Retry generating admin-tech |
ADMINTECH-5-PUBLISH_SUCCESS |
5-Notice |
Admin-tech bundle [chars] successfully uploaded to Cisco SD-WAN Manager |
This notice syslog is generated when admin-tech is successfully uploaded to SD-WAN Manager after the generation is complete |
cedge-admintech |
No action is required |
AFC_SCHED-1-AFC_HTTPCON_HEALTHCHECK_FAILURE |
1-Alert |
AFC Healthcheck failed with HTTP connection error: [chars]. |
AFC Healthcheck failed due to HTTPCON error |
afc |
LOG_STD_NO_ACTION |
AFC_SCHED-1-AFC_HTTP_HEALTHCHECK_FAILURE |
1-Alert |
AFC Healthcheck failed with HTTP status code [dec]. |
AFC Healthcheck failed due to HTTP error |
afc |
LOG_STD_NO_ACTION |
AFC_SCHED-1-AFC_PROVIDER_HEALTHCHECK_FAILURE |
1-Alert |
AFC Healthcheck failed : [chars]. |
AFC Healthcheck failed due to provider error |
afc |
LOG_STD_NO_ACTION |
AFC_SCHED-3-AFC_CLOUDM_HEALTHCHECK_FAILURE |
3-Error |
AFC Healthcheck failed, can't communicate with cloud services because [chars]. |
AFC Healthcheck failed due cloudm communication failure |
afc |
LOG_STD_NO_ACTION |
AFC_WNCD-1-AFC_CONDITIONS_NOT_MET |
1-Alert |
Some geolocation information is missing for AP with Radio MAC [chars] to use AFC:[chars] |
Some conditions are preventing the AP from using AFC |
afc |
LOG_STD_NO_ACTION |
AFC_WNCD-4-AFC_GEOLOCATION_HIGH_UNCERTAINTY |
4-Warning |
Current location uncertainty for AP [chars] is high ([dec] meters). |
Geoloocation uncertainty for the AP is above 400m |
afc |
LOG_STD_NO_ACTION |
AFC_WNCD-6-AFC_WNCD_INFO |
6-Information |
Info Level - [chars] |
General AFC WNCD Lib info message |
ewlc-spwifi |
LOG_STD_ACTION |
APMGR_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_GTK_UNABLE_TO_UPDATE_BROADCAST_KEYS_TO_AP |
3-Error |
User ID: [chars] - Unable to update broadcast keys to AP |
Unable to update broadcast keys to AP |
ewlc-client |
LOG_STD_ACTION |
APMGR_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_COP_1_DataEncryption |
6-Information |
AP [chars] User ID: [chars] [chars] [chars] [chars] [chars] |
TLV_AP_CC_AUDIT_PAYLOAD parameters |
ewlc-ap |
LOG_STD_ACTION |
APMGR_AWIPS_SYSLOG-6-APMGR_AWIPS_MESSAGE |
6-Information |
AWIPS alarm:[chars] ([dec]) |
AWIPS alarm detected |
ewlc-awips |
LOG_STD_NO_ACTION |
APMGR_TRACE_MESSAGE-2-BSSID_CLEANUP_TIMEOUT |
2-Critical |
BSSID cleanup timeout, [chars] |
BSSID cleanup could not be completed. This may result in failure to push configuration updates to Access Points. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. |
ewlc-ap |
Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. |
APMGR_TRACE_MESSAGE-2-WLAN_CRIT_ERR |
2-Critical |
WLAN Error : [chars] |
Critical issue seen with WLAN config. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. |
ewlc-ap |
Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. |
APMGR_TRACE_MESSAGE-2-WLAN_CRIT_INFO |
2-Critical |
CRITICAL, [chars] |
General Wireless LAN Controller critical message |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-2-WLC_APMGR_CRIT_MSG |
2-Critical |
CRITICAL, [chars] |
General Wireless LAN Controller warning message |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-AP_NTP_SYNC |
3-Error |
AP [chars] MAC [chars], NTP sync has failed. Reason: [chars] |
The Ap failed to sync with the NTP server |
ewlc-ap |
Verify the IP address of the NTP server and the authentication credentials. |
APMGR_TRACE_MESSAGE-3-AP_RADIO_STUCK_ALARM |
3-Error |
Radio Stats Monitoring: [chars] |
Radio stats monitoring and radio stuck alarm |
ewlc-ap |
No action required |
APMGR_TRACE_MESSAGE-3-EWLC_APMGR_ANTENNA_SET_ERROR |
3-Error |
Antenna set error: [chars] |
Antenna id enable/disable operation has resulted in error. please follow error message for details |
ewlc-rrm |
Please follow error message string and take corrective action |
APMGR_TRACE_MESSAGE-3-EWLC_APMGR_AP_REG_DOMAIN_MISMATCH |
3-Error |
Error: Cannot set country code [chars] for AP MAC:[chars],Regulatory domain check failed |
Regulatory domain of all radio slots of the AP does not match with the country code |
ewlc-rrm |
In most cases, the problem can be corrected by checking regulatory domain supported by Access Point (AP). Radios within APs are assigned to a specific regulatory domain as a part of factory setting. Configuring a country code ensures that each radio's broadcast frequency bands, channels and transmit power levels are compliant with country-specific regulations. Please ensure that user configured country code is compliant with country code setting in AP. |
APMGR_TRACE_MESSAGE-3-EWLC_APMGR_UNSUPPORTED_COUNTRY |
3-Error |
Regulatory domain error while setting country code for AP MAC:[chars], country code [chars] is not configured on WLC |
Specified country code is not present in the configured country code list |
ewlc-rrm |
Validate the country code configuration on the Controller and add the country code to the configured country code list if it is not already present. Please refer to the configuration guide to configure country code. If you still require contact your Cisco technical support representative and provide the information you have gathered. |
APMGR_TRACE_MESSAGE-3-EWLC_GEN_CHAN_ERR |
3-Error |
Error in [chars] |
General Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-EWLC_RRM_ERROR |
3-Error |
event change: [chars] |
General Wireless LAN Controller RRM error message |
ewlc-rrm |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-EWLC_RRM_QUERY_ERR |
3-Error |
Error in [chars] |
Trying to query information related to AP with invalid slot ID. |
ewlc-rrm |
Please report the error to technical support representative. |
APMGR_TRACE_MESSAGE-3-EWLC_WLAN_ETA_MSG |
3-Error |
et-analytics config validation Error: [chars] |
Global and Wireless et-analytics config dependency error |
ewlc-ap |
No action required |
APMGR_TRACE_MESSAGE-3-EWLC_WLAN_MPSK_MSG |
3-Error |
MPSK config validation Error: [chars] |
MPSK and Central auth dependency error |
ewlc-ap |
No action required |
APMGR_TRACE_MESSAGE-3-EWLC_WLAN_MPSK_PSK_MSG |
3-Error |
MPSK config validation Error: [chars] |
MPSK and PSK dependency error |
ewlc-ap |
No action required |
APMGR_TRACE_MESSAGE-3-EXEC_CLI_INVALID_SLOT |
3-Error |
Executed exec-cli is not applicable for AP: [chars], number of slots: [dec], while cli executed for slot: [dec]. |
The executed EXEC CLI is not applicable for this AP, because the limitation number of slots |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-EXEC_CLI_NOT_5G_DUAL_RADIO_AP |
3-Error |
Executed exec-cli is not applicable for AP: [chars] because AP does not support dual 5ghz radio. |
The executed EXEC CLI is not applicable for this AP, because AP does not support dual 5ghz radio |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-EXEC_CLI_NOT_MASTER_RADIO |
3-Error |
Executed exec-cli is applicable for only master radio for AP : [chars] |
The executed EXEC CLI is applicable only for master radio |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-EXEC_CLI_TX_POWER |
3-Error |
Tx Power Config Notification: Radio Role is AUTO. So, Tx power change is not allowed for AP [chars] on slot [dec]. |
Tx Power configuration is not allowed. |
ewlc-rrm |
LOG_STD_NO_ACTION |
APMGR_TRACE_MESSAGE-3-WLC_AP_AUDIT_REPORT_ERR |
3-Error |
Error in [chars] |
AP Audit Report Error Message. |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-WLC_AP_CONFIG_CHECKER_ERR |
3-Error |
error received from AP [chars] |
Error on AP while applying configuration updates from controller. |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_24G_DCA_CHANNEL_LIST_EMPTY |
3-Error |
The DCA Channel list is empty for 24ghz rf profile [chars] |
DCA Channel list for 24ghz radio is empty, it affects Channel Assignment to AP |
ewlc-rrm |
Please add channels to DCA List |
APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_5G_DCA_CHANNEL_LIST_EMPTY |
3-Error |
The DCA Channel list is empty for 5ghz rf profile [chars] |
DCA Channel list for 5ghz radio is empty, it affects Channel Assignment to AP |
ewlc-rrm |
Please add channels to DCA List |
APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_6G_DCA_CHANNEL_LIST_EMPTY |
3-Error |
The DCA Channel list is empty for 6ghz rf profile [chars] |
DCA Channel list for 6ghz radio is empty, it affects Channel Assignment to AP |
ewlc-rrm |
Please add channels to DCA List |
APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_CRIT_ERR |
3-Error |
AP Join/Disjoin Error: [chars] |
AP Join/Disjoin Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-WLC_AP_LOG_MSG |
3-Error |
AP Remote Log: [chars] |
AP Remote logging |
ewlc-ap |
No action required |
APMGR_TRACE_MESSAGE-3-WLC_AP_PACKET_CAPTURE_ERR |
3-Error |
Error in [chars] |
AP packet capture Error Message. |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-WLC_EXEC_MSG |
3-Error |
%% Error: [chars] |
Improper arguments or config |
ewlc-ap |
Arguments to be changed |
APMGR_TRACE_MESSAGE-3-WLC_GEN_ERR |
3-Error |
Error in [chars] |
General Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-WLC_MDNS_AP_ERROR_MSG |
3-Error |
Error mDNS AP : [chars] |
Error Message related to mDNS AP |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-3-WLC_UNSUPPORTED_AP_MODE_ERR |
3-Error |
Unsupported AP mode. [chars] |
vWLC ultra-low WLCs do not support Local Mode APs. This error will be logged whenever an AP tries to join in Local Mode on a vWLC ultra-low WLC. |
ewlc-ap |
Fix the configuration to allow AP to join in Flexconnect Mode. |
APMGR_TRACE_MESSAGE-4-AP_CPU_ALARM |
4-Warning |
AP [chars], MAC [chars], CPU=[dec]%%, alarm state: [dec] |
An alarm was triggered for AP CPU measurements |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-4-AP_GNSS_USB_DISCONNECTED |
4-Warning |
AP [chars], GNSS USB Module has been removed. This might impact location availabilty and derivation for nearby APs |
GNSS USB module disconnected from AP |
ewlc-afc-rrm |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-4-AP_MEM_ALARM |
4-Warning |
AP [chars], MAC [chars], Memory=[dec]%%, alarm state: [dec] |
An alarm was triggered for AP Memory measurements |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-4-AP_MERAKI_CONVERSION_FAILURE |
4-Warning |
AP [chars], MAC [chars], Meraki serial number: [chars], Meraki persona change result: Failed. Reason: [chars] |
Conversion to Meraki AP validation result |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-4-EASYPSK_UNSUPPORTED_AP_MODE |
4-Warning |
Unsupported AP mode for Easy-PSK WLAN [dec] on AP [chars], MAC [chars]. Easy-PSK only supported in local mode. |
Easy-PSK WLAN configured on AP not in local mode. WLAN will not be pushed to the AP. |
ewlc-spwifi |
Fix the configuration to move AP in local mode. |
APMGR_TRACE_MESSAGE-4-WLC_APMGR_WARNING_MSG |
4-Warning |
Warning, [chars] |
General Wireless LAN Controller warning message |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-4-WLC_CONFIG_CHECKER_WARNING |
4-Warning |
config check: [chars] |
Warning message related to config checker |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-4-WLC_MDNS_AP_WARNING_MSG |
4-Warning |
Warning mDNS AP : [chars] |
Warning message related to mDNS AP |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-5-AP_AFC_BELOW_TX_MIN |
5-Notice |
AP [chars], 6GHZ radio operating below tx min due to afc restriction |
6GHZ radio operating below rf profile configured tx min due to afc restriction |
ewlc-afc-rrm |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-5-AP_AFC_IMMINENT_FLAG_SET |
5-Notice |
AP [chars], 6GHZ radio AFC response is about to expire on AP |
6GHZ AFC expiry imminent flag set |
ewlc-afc-rrm |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-5-AP_EXEC_CLI |
5-Notice |
Exec CLI : [chars] |
Exec cli information or output |
ewlc-ap |
LOG_STD_NO_ACTION |
APMGR_TRACE_MESSAGE-5-EWLC_APMGR_NOTICE |
5-Notice |
event change: [chars] |
General Wireless LAN Controller Notice message |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-5-WLC_AP_PUBLIC_CLOUD_ERR |
5-Notice |
Unsupported AP mode. [chars] |
Public cloud WLCs do not support Local Mode in AP. This error will be logged whenever an AP tries to join in Local Mode in a Public Cloud WLC. |
ewlc-ap |
Fix the configuration to allow AP to join in Flexconnect Mode. |
APMGR_TRACE_MESSAGE-6-AP_MERAKI_CONVERSION_SUCCESS |
6-Information |
AP [chars], MAC [chars], Meraki serial number: [chars], Meraki persona change result: [chars] |
Conversion to Meraki AP validation result |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-6-CHAN_ZERO_DETECTED |
6-Information |
AP: [chars] reported channel 0 on slot [dec] |
AP has reported Channel 0 on one of the radio slots. This generally happens when the configurations on the AP are set to factory default. WLC recovers this by rebooting the AP. Unless the message repeatedly appears, it does not require any action. |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-6-CLIENT_DEBUG_BUNDLE_INFO |
6-Information |
Client debug bundle [chars] |
General Wireless LAN Controller Client debug bundle info message |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-6-EWC_APMGR_OLD_VERSION |
6-Information |
AP Event: [chars] Please upgrade AP to 8.10 or 16.12 or higher before joining a EWC network |
Please upgrade 11AX AP to 8.10 or 16.12 so it can join EWC network |
ewcap-image |
LOG_STD_NO_ACTION |
APMGR_TRACE_MESSAGE-6-EWC_APMGR_POLL_CCO_SUCCESS |
6-Information |
CCO polling for software version completed successfully |
The action of polling CCO for LATEST and SUGGESTED software version has completed successfully |
ewcap-image |
LOG_STD_NO_ACTION |
APMGR_TRACE_MESSAGE-6-WLC_APMGR_INFO |
6-Information |
Info : - [chars] |
General Wireless LAN Controller info message |
ewlc-ap |
LOG_STD_ACTION |
APMGR_TRACE_MESSAGE-6-WLC_AP_JOIN |
6-Information |
AP Join Info : [chars] |
AP Join/Disjoin Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
AP_POWER_PROFILE_TRACE_MESSAGE-3-WLC_GEN_ERR |
3-Error |
Error in [chars] |
General Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
AUTO_FPD-3-FRU_HWPRG_UPG_ERR |
3-Error |
Error reason:[chars] |
Some error occurred during auto upgrade |
iosxe-binos-utils |
Retry upgrade |
AUTO_FPD-3-FRU_HWPRG_UPG_FAILED |
3-Error |
[chars] in slot [chars] failed to program. error: [chars] |
The hw-programmable was upgraded failed |
iosxe-binos-utils |
Retry upgrade |
AUTO_FPD-5-FRU_HWPRG_UPG_START |
5-Notice |
[chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. |
The hw-programmable firmware is upgrading |
iosxe-binos-utils |
No action is required. This is informational message |
AUTO_FPD-5-FRU_HWPRG_UPG_SUCCESS |
5-Notice |
[chars] in slot [chars] are successfully programmed. |
The hw-programmable was upgraded succesfully |
iosxe-binos-utils |
No action is required. This is informational message |
AUTO_UPGRADE-3-AUTO_ADVISE_SW_COM_BUNDLED |
3-Error |
Switch [dec] running incompatible bundled software has been added to the stack. Switch [dec] must be running compatible bundled software in order to join the stack. |
No explanation required. |
iosxe-binos-utils |
Boot the member with compatible software. |
AUTO_UPGRADE-3-AUTO_ADVISE_SW_FAILED_PLATFORM |
3-Error |
Failed to determine platform hardware type of switch [dec] |
Somehow the platform type could not determined. |
iosxe-binos-utils |
Add an action |
AUTO_UPGRADE-3-AUTO_ADVISE_SW_MODE_UNKNOWN |
3-Error |
Switch [dec] has been added to the stack. Failed to initiate auto advise for switch [dec] because switch [dec] is not running installed or bundled software |
No explanation required. |
iosxe-binos-utils |
Boot the member with compatible software. |
AUTO_UPGRADE-3-AUTO_CONF_EXEC |
3-Error |
Auto upgrade is enabled by config. Please disable auto upgrade configuration to execute auto upgrade manually using exec CLI. |
TODO: add an explanation. |
iosxe-binos-utils |
TODO: add an action |
AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_COPY |
3-Error |
Failed to copy upgrade packages from [chars] [dec] to [chars] [dec]/R[dec]. |
TODO: add an explanation. |
iosxe-binos-utils |
TODO: add an action |
AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_DISK |
3-Error |
[chars] [dec]/[dec] doesn't have enough free disk space to perform auto upgrade. A minimum of [dec] KB of free disk space is required Initiating the auto-delete of the old images on joining member/FRU. (Default is oldest image in configuration mode) |
There might be older files because of which there is not enough memory. |
iosxe-binos-utils |
Clean up disk space in the remote switch. |
AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_EXPAND |
3-Error |
Failed to install the running software on switch [dec] |
TODO: add an explanation. |
iosxe-binos-utils |
No action required. |
AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_MEM |
3-Error |
[chars] [dec] doesn't have enough free memory to perform auto upgrade. A minimum of [dec] KB of free memory is required |
There might be older files because of which there is not enough memory. |
iosxe-binos-utils |
Clean up disk space in the remote switch. |
AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_PLATFORM |
3-Error |
Failed to determine platform hardware type of [chars] [dec]/R[dec] |
Somehow the platform type could not determined. |
iosxe-binos-utils |
Add an action |
AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_STATE |
3-Error |
A previous provisioning action is pending reboot. Please reboot the [chars] [dec]. |
The user has run an operation that requires a reboot to take action. |
iosxe-binos-utils |
Reload the switch |
AUTO_UPGRADE-3-AUTO_UPGRADE_INTERNAL_ERROR |
3-Error |
Local chassis/RP number did not publish yet |
Somehow the chassis/FRU number is missing. |
iosxe-binos-utils |
Try to do it again. |
AUTO_UPGRADE-3-AUTO_UPGRADE_MODE_UNKNOWN |
3-Error |
Switch [dec] has been added to the stack. Failed to initiate auto upgrade for switch [dec] because switch [dec] is not running installed or bundled software |
No explanation required. |
iosxe-binos-utils |
Boot the member with compatible software. |
AUTO_UPGRADE-3-AUTO_UPGRADE_NOTHING_TO_CLEAN |
3-Error |
Couldn't find enough old install images on incompatible standby/member for deletion. Please manually free up [dec] MB space on incompatible standby/member and try again using 'install autoupgrade'. |
If there is no old images are found on joining standby/member's boot directory |
iosxe-binos-utils |
User will have to manually delete old files using IOS delete command |
AUTO_UPGRADE-3-AUTO_UPGRADE_NOTHING_TO_UPGRADE |
3-Error |
No incompatible standby/member is found, nothing to auto-upgrade. |
Exec autoupgrade scenario when there is no incompatible member in stack. |
iosxe-binos-utils |
No action is required from the user |
AUTO_UPGRADE-3-AUTO_UPGRADE_NOT_SUPPORTED |
3-Error |
The system is not running installed software. Auto upgrade for [chars] [dec]/R[dec] cannot be initiated |
A system with incompatible software has been detected in the stack. The auto upgrade functionality cannot be initiated because the stack/HA system is not running installed software. The user must manually upgrade the incompatible switch/FRU. |
iosxe-binos-utils |
Perform the one shot cli to convert system is install mode. Boot the system from the boot directory (bootflash/harddisk) using 'boot bootflash:packages.conf' |
AUTO_UPGRADE-3-AUTO_UPGRADE_NO_DOWNGRADE |
3-Error |
Skip auto-upgrade on chassis [dec]. The Active chassis's software version [chars] is lower than this chassis's minimum software version requirement [chars]. |
Skip auto-downgrade scenario when the active switch does not fulfill the minimum software release version requirment. The active switch is running an image lower than the remote chassis's minimum software version. |
iosxe-binos-utils |
Upgrade the stack to a higher release version or remove the switch from the stack. |
AUTO_UPGRADE-3-AUTO_UPGRADE_PLATMISMATCH |
3-Error |
No software was found to upgrade [chars] [dec]/R[dec] |
Happens because of incompatible switches. For example, ngwc and non-ngwc ones are incompatible |
iosxe-binos-utils |
Plugin compatible switches for autoupgrade to run. |
AUTO_UPGRADE-3-AUTO_UPGRADE_ROMMON_NOT_UPDATED |
3-Error |
Unable to confirm boot config on [chars] [dec]/R[dec], assuming it is set as [chars]. |
TODO: add an explanation. |
iosxe-binos-utils |
NO action is required. |
AUTO_UPGRADE-3-SMU_SYNC_FAILED |
3-Error |
SMU upgrade failed on switch [dec]. Auto upgrade of image will pass with out syncing SMUs on this switch. SMUs will be synced at boot time of the switch [dec] |
SMU sync failed because of some reason. |
iosxe-p-smu |
No action required, SMU sync will be tried in next reload. |
AUTO_UPGRADE-3-SMU_UPGRADE_FAILED_DISK |
3-Error |
Switch [dec] doesn't have enough free disk space to sync SMU. A minimum of [dec] KB of free disk space is required. Auto upgrade will pass with out syncing SMUs on this switch |
There might be older files because of which there is not enough memory. |
iosxe-p-smu |
Clean up disk space in the remote switch. |
AUTO_UPGRADE-5-AUTO_ADVISE_SW_BUNDLED |
5-Notice |
switch [dec] running installed software has been added to the stack. Switch [dec] must be running bundled software in order to join the stack. |
No explanation required. |
iosxe-binos-utils |
Boot the member with compatible software. |
AUTO_UPGRADE-5-AUTO_ADVISE_SW_CONV |
5-Notice |
[chars] [dec] running bundled software has been added to the stack that is running installed software. The 'install autoupgrade' command can be used to convert [chars] [dec] to the installed running mode by installing its running software. |
No explanation required. |
iosxe-binos-utils |
No specific action required. |
AUTO_UPGRADE-5-AUTO_ADVISE_SW_FOUND |
5-Notice |
Found donor switch [dec] to auto upgrade switch [dec]. |
Just an init message. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_ADVISE_SW_INITIATED |
5-Notice |
Auto advise initiated for [chars] [dec]. |
A system with incompatible software has been detected in the stack. The stack will now determine whether or not software is available to be copied to the incompatible system, and if so, advise the user how to copy it. Otherwise, the system will merely let the user know that the software on the stack needs to be updated. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_ADVISE_SW_MSG |
5-Notice |
[chars] [dec]/R[dec] with incompatible software has been added to the system/stack. all system/stack members were scanned and it has been determined that the 'install autoupgrade' command can be used to install compatible software on [chars] [dec]/R[dec]. |
TODO: add an explanation. |
iosxe-binos-utils |
TODO: add an action |
AUTO_UPGRADE-5-AUTO_ADVISE_SW_SEARCH |
5-Notice |
Searching stack for software to upgrade [chars] [dec]/R[dec]. |
Just an init message. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_ADVISE_SW_START |
5-Notice |
Upgrading [chars] [dec] with software from [chars] [dec]. |
Just an init message. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_UPGRADE_CONV |
5-Notice |
Converting [chars] [dec] to installed mode by installing its running software. |
This needs to be converted as part of the auto upgrade. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_UPGRADE_FINISH |
5-Notice |
Finished installing software on [chars] [dec]/R[dec]. |
TODO: add an explanation. |
iosxe-binos-utils |
TODO: add an action |
AUTO_UPGRADE-5-AUTO_UPGRADE_FOUND |
5-Notice |
Found donor [chars] [dec] to auto upgrade [chars] [dec]/R[dec]. |
Just an init message. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_UPGRADE_INITIATED |
5-Notice |
Auto upgrade initiated for [chars] [dec]/R[dec]. |
A system with incompatible software has been detected in the stack. The stack will first attempt to download software from a previously-configured location, and install it to make the system compatible. If this is not successful, the stack will then determine whether running software on another stack member is available to be copied to the incompatible system, and whether or not it is appropriate to copy the software automatically |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_UPGRADE_INSTALLED |
5-Notice |
Finished installing the running software on [chars] [dec]. |
TODO: add an explanation. |
iosxe-binos-utils |
TODO: add an action |
AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD |
5-Notice |
Reloading [chars] [dec] to complete the auto upgrade. |
Part of autoupgrade |
iosxe-binos-utils |
Just wait until the reload completes. |
AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD_INSTALLED |
5-Notice |
Reloading [chars] [dec] to boot in installed mode. |
TODO: add an explanation. |
iosxe-binos-utils |
TODO: add an action |
AUTO_UPGRADE-5-AUTO_UPGRADE_SEARCH |
5-Notice |
Searching stack for software to upgrade [chars] [dec]/R[dec]. |
Just an init message. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_UPGRADE_START |
5-Notice |
Upgrading [chars] [dec]/R[dec] with software from [chars] [dec]. |
Just an init message. |
iosxe-binos-utils |
No action is required. |
AUTO_UPGRADE-5-AUTO_UPGRADE_START_CHECK |
5-Notice |
Auto upgrade start checking for incompatible switches. |
Part of autoupgrade |
iosxe-binos-utils |
NO action is required. |
AUTO_UPGRADE-5-SMU_RB_SYNC_FAILED |
5-Notice |
SMU rollback sync failed on [chars]. Rollback operations may be affeced |
SMU rollback sync failed on some reason. Most probable causes are SMUs are not present on the media or the media is full. |
iosxe-p-smu |
Bring back the SMUs deleted and check whether there is enough space in remote member/SMUs |
AUTO_UPGRADE_MODULAR-3-AUTO_ERR_SMU_SYNC_FAILED |
3-Error |
Failed to sync SMUs to standby. Make sure that SMU files are present on active and there is space enough to copy SMUs on standby. |
SMU sync failed. Most probable cause are the smu files may have been removed from the active switch using IOS/linux commands. Another reason is there is no space enough to copy the files to the standby |
iosxe-p-smu |
If the files are removed from the active bring it back to same location. Make sure there is enough space to copy the files on the standby |
AUTO_UPGRADE_MODULAR-3-AUTO_NOTICE_RUN_CORRECTION_FAILED |
3-Error |
Failed to correct the SMU mismatch between the running version on active and standby. Pls abort the smu installation using 'install abort' |
The system tried to recover from the missmatch, but failed. Engineer intervention is required |
iosxe-p-smu |
Get the 'show install log' and the btrace logs from active and standby |
AUTO_UPGRADE_MODULAR-5-AUTO_ADVISE_SW_MISSMATCH |
5-Notice |
Active and standby are running differnt versions, SMUs will not be synced. |
No explanation required. |
iosxe-binos-utils |
Boot the member with same software. |
AUTO_UPGRADE_MODULAR-5-AUTO_NOTICE_RUN_MISSMATCH_STBY_RELOAD |
5-Notice |
Missmatch between running version of SMUs. Trying to recover. Standby will reload |
There is a missmatch on the running version. This will happen when the standby reloads after activate/deactivate and before commit. The machine will try to correct it. One reload is required for correcting the chanages. |
iosxe-binos-utils |
No action required. |
AUTO_UPGRADE_MODULAR-5-AUTO_NOTICE_STBY_RELOAD |
5-Notice |
Installing SMUs on standby. Standby will reload |
No explanation required. |
iosxe-binos-utils |
No action required. |
AUTO_UPGRADE_MODULAR-5-SMU_AUTO_UPGRADE_INITIATING |
5-Notice |
Initiating SMU autoupgrade for [chars] [dec]/R[dec] |
No explanation required. |
iosxe-binos-utils |
Boot the member with same software. |
AVC_MESSAGE-3-EWLC_AVC_FNF_CLI_ERR |
3-Error |
CLI validation error: [chars] |
General AVC FNF CLI validation error |
iosxe-binos-utils |
LOG_STD_ACTION |
BBU-0-CHASFS_OBJECT_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] not present. |
A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-0-CHASFS_PROPERTY_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly created. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-0-CHASFS_PROPERTY_GET |
0-Emergency |
Failed to read chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly read by the system. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-0-CHASFS_PROPERTY_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] property [chars] not present. |
A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-0-CHASFS_PROPERTY_SET |
0-Emergency |
Failed to write chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property failed to write. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-0-SERVICES_INITIALIZATION |
0-Emergency |
Failed to initialize general application services because [chars] |
The system failed to initialize application services. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-0-UIPEER_CREATE |
0-Emergency |
Failed to create user interface peer. |
The system failed to create a user interface peer. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-3-BAD_CELL |
3-Error |
Bad battery cell detected in unit [dec] |
Battery firmware detected a bad cell, which can't be recharged. |
cabo-platform |
Replace the bad battery unit. |
BBU-3-CHASFS_PROPERTY_DESTROY |
3-Error |
Failed to destroy chassis filesystem property [chars]/[chars] because [chars] |
A chassis filesystem property that should have been destroyed was not destroyed. |
cabo-platform |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-3-CLI_ERROR |
3-Error |
[chars] command execution failed with err=[dec] |
CLI execution failed |
cabo-platform |
No user action is required. |
BBU-3-COMM_ERR |
3-Error |
Battery communication error: [chars] |
Battery communication error. |
cabo-platform |
Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-3-FW_UPGRADE_FAILED |
3-Error |
Firmware upgrade failed with error [dec] |
Battery firmware upgrade failed. |
cabo-platform |
Check battery status. |
BBU-3-HW_INIT_PH_ERR |
3-Error |
Hardware init phase error, [chars] init returned [dec] |
Hardware failed to initialize. |
cabo-platform |
Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-3-HW_RUNTIME_ERR |
3-Error |
Hardware runtime error, [chars] init returned [dec] |
Hardware failed. |
cabo-platform |
Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BBU-4-AC_TO_DC_TRANSITION |
4-Warning |
AC power is off, running on batteries. |
Lost power from AC power line, system is powered by backup batteries. |
cabo-platform |
Check AC power line. |
BBU-4-FW_UPGRADE_STARTED |
4-Warning |
Firmware upgrade to version [dec] started |
Battery firmware upgrade started. |
cabo-platform |
No user action is required. |
BBU-4-LOW_LEVEL |
4-Warning |
Battery charge running low ([dec]%%) |
Battery charge is below low level threshold. |
cabo-platform |
Check AC power line. |
BBU-4-STATUS_CHANGE |
4-Warning |
The [chars] parameter for BBU unit [dec] has changed |
Status change of BBU parameters |
cabo-platform |
No user action is required. |
BBU-5-BBU_EVT_LOG |
5-Notice |
Battery Event Log - [chars]:[chars] \n |
BBU Event Log Data. |
cabo-platform |
No user action is required. |
BBU-5-CELL_RECOVERED |
5-Notice |
Battery cell in unit [dec] recovered |
A battery cell, which was previously detected to be bad, has now recovered. |
cabo-platform |
No user action is required. |
BBU-5-CLI_OK |
5-Notice |
Command [chars] |
CLI execution successful. |
cabo-platform |
No user action is required. |
BBU-5-DC_TO_AC_TRANSITION |
5-Notice |
AC power is back on, running on power line |
AC power is restored, system is powered by AC power line |
cabo-platform |
No user action is required. |
BBU-5-FW_UPGRADE_FINISHED |
5-Notice |
Firmware upgrade finished successfully |
Battery firmware upgrade finished. |
cabo-platform |
No user action is required. |
BBU-5-HW_HOTPLUG |
5-Notice |
Battery detected, started initialization |
Battery hotplugged in the system, Started probing and initialization. |
cabo-platform |
No user action is required. |
BBU-5-NORMAL_LEVEL |
5-Notice |
Battery charge reached normal level ([dec]%%) |
Battery charge is above low level threshold. |
cabo-platform |
No user action is required. |
BBU-7-FSM_TRANSITION |
7-Debug |
FSM transition ([dec], [dec]) -> [dec] |
FSM transition (old_state, event) -> new state |
cabo-platform |
No user action is required. |
BCRDU-3-PATCH_ACTIVATE_FAIL_MESSAGE |
3-Error |
Failed to activate patch. The patch name is [chars] and the reason is: [chars] |
During system reload, all committed patches will be automatically activated.For some reason, a patch activation fails. |
iosxe-binos-utils |
Check [bcrdu] ERR entries in the log files for message reporting problems. |
BCRPGC-3-REFERENCE_STUBBED |
3-Error |
Stubbed [chars] is referenced |
Stubbed function/variable is referenced. |
iosxe-binos-utils |
File a DDTS and attach the backtrace |
BCRPGC-3-USWAP_ERROR |
3-Error |
uswap error - no space on [chars] |
Path for USWAP files. |
iosxe-binos-utils |
If this error is seen, it is recommended to clean up the flash usage. If more assistance is required, file a DDTS, attach the backtrace and btrace |
BFDMGR-5-BFD_STATE_CHANGE |
5-Notice |
BFD tunnel ([chars]:[dec] => [chars]:[dec], [chars]) state changed to [chars], Local-TLOC: [chars]/[chars], Remote-TLOC: [chars]/[chars], reason for state change: [chars] |
This syslog is generated when a BFD tunnel state changes |
cedge-forwarding |
No action is required |
BFDMGR-6-BFD_SLA_CHANGE |
6-Information |
BFD tunnel ([chars]:[dec] => [chars]:[dec], [chars]) SLA changed from [chars] to [chars], Local-TLOC: [chars]/[chars], Remote-TLOC: [chars]/[chars] PFR stats: [chars] |
This syslog is generated whenever SLA of a BFD tunnel running on top of specific TLOC changes |
cedge-forwarding |
No action is required |
BINOS_LOGIN-3-AUTHERR |
3-Error |
The authentication process failed, [chars] |
This error occurs when there is an error in the system that prevents the user from being successfully authenticated |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
BINOS_LOGIN-3-NOTROOT |
3-Error |
login attempted to run without proper credentials. |
login can not be run without proper credentials. |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
BINOS_LOGIN-3-NOTTY |
3-Error |
login attempted but stdin is not a tty |
login can not be run without stdin set to tty |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
BINOS_LOGIN-3-PAMERR |
3-Error |
PAM error [chars] encountered. |
The system encountered a PAM error. |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
BINOS_LOGIN-3-PWNOENT |
3-Error |
No entry for user [chars] in passwd file |
The username/password authenticated correctly, but the user's environment could not be established because the user's environment data is missing. |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
BINOS_LOGIN-6-PAMAUTHDENY |
6-Information |
User was not authenticated |
User was not authenticated |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
BINOS_LOGIN-6-PAMMAXTRIES |
6-Information |
Maximum number of retries exceeded. |
The user tried and failed too many times to login. |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
BIPC-3-BIPC_PERFORMANCE |
3-Error |
buffer size request [dec] failed |
An internal buffer allocation has failed. |
iosxe-binos-utils |
No action is required. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
BIPCMGR-3-INVALID_TDL_ERROR_ON_MARSHAL |
3-Error |
TDL epoch error on marshal [dec] unexpected: [chars] |
The bipc manager has attempt to marshal a message to be sent. The tdl library has generated an error on marshal that is unexpected. The message was not sent. |
iosxe-binos-utils |
This is unexpected. Report this to Cisco TAC |
BOOT-0-APP_STARTFAILCRIT |
0-Emergency |
Failed to launch a critical process [chars] |
A process important to the chassis has failed. |
iosxe-binos-utils |
Note the time of the message and investigate the error message logs to learn more about the problem. If the problem persists or cannot be resolved, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. |
BOOT-0-BOOT_BADDIMM |
0-Emergency |
WARNING: This memory configuration: [chars] is not supported on this platform! |
This memory configuration isn't supported on this platform. |
iosxe-binos-utils |
Change memory configuration to a supported one. |
BOOT-0-BOOT_COMPLETE_FAIL |
0-Emergency |
Critical boot tasks failed: [chars] |
The system has encountered a critical failure preventing successful boot. |
iosxe-binos-utils |
Note the time of the error message and system logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. |
BOOT-0-BOOT_NOSPACE |
0-Emergency |
WARNING: No space on bootflash [chars] for packages, using system memory! Delete files from bootflash to free memory and reload the system; otherwise, system behavior will be unpredictable due to high memory utilization. |
Failed to boot system from bootflash. Image is booting from system memory! Delete files from bootflash to free memory and reload the system; otherwise, system behavior will be unpredictable due to high memory utilization. |
iosxe-binos-utils |
Delete files from bootflash to free memory and reload the system. |
BOOT-0-BOOT_VERITY_CORRUPT |
0-Emergency |
Verity device [chars] is corrupted. Reloading FRU. |
The integrity check of the verity mapped device has failed. |
iosxe-binos-utils |
Check image integrity. |
BOOT-0-DRV_INITFAIL |
0-Emergency |
[chars] driver failed to initialize properly |
A kernel driver that is critical to the functioning of the system failed to initialialize properly. |
iosxe-binos-utils |
Note the time of the error message and check the kernel error logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. |
BOOT-0-DRV_LOADFAIL |
0-Emergency |
Failed to load driver [chars] ( [chars] ) |
A kernel driver that was critical to the functioning of the system failed to load. |
iosxe-binos-utils |
Note the time of the error message and check the kernel error logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. |
BOOT-3-APP_STARTFAIL |
3-Error |
Failed to launch process [chars] |
A process that does not affect the forwarding of network traffic failed to start. |
iosxe-binos-utils |
If the failed process is not something that needs to be corrected, do not address this message. If the failed process needs to be addressed, install new software and reload the router. |
BOOT-3-BOOTTIME_GET_ISSU_INFO_OF_REMOTE_CHASSIS_FAILED |
3-Error |
Failed to get ISSU information from remote chassis. Details: [chars] |
Failed to get remote switch information for compatibility check. This could be for multiple underlying failures such as reachability of peer member lost or remote member not responding |
iosxe-binos-utils |
If standby is stuck retry with reloading standby. If standby does not comes up even after reloading attempts, try reloading the whole stack to recover. |
BOOT-3-BOOTTIME_INCOMPATIBLE_SW_DETECTED |
3-Error |
Incompatible software detected. Details: [chars] |
Incompatible software is detected on target fru/chassis. |
iosxe-binos-utils |
Upgrade manually or check auto-upgrade configuration. |
BOOT-3-BOOTTIME_MISMATCH_RESTRICTED_STACK_SETUP_DETECTED |
3-Error |
Mismatch detected. Details: [chars] |
Incompatible stacked setup detected on target fru/chassis. |
iosxe-binos-utils |
Switch with mismatch require to be reloaded |
BOOT-3-BOOTTIME_SMU_MISSING_DETECTED |
3-Error |
SMU file [chars] missing and system impact will be unknown |
SMU file not found during bootup. |
iosxe-p-smu |
System will be running without the fix from the SMU |
BOOT-3-BOOTTIME_SMU_RUN_CORRECTION_FAILED |
3-Error |
Failed to correct the SMU mismatch between the running version on active and [chars]. Pls abort the smu installation using 'install abort' |
The system tried to recover from the missmatch, but failed. Engineer intervention is required |
iosxe-p-smu |
Get the 'show install log' and the btrace logs from active and standby |
BOOT-3-BOOTTIME_SMU_SYNC_FAILED |
3-Error |
Failed to copy the SMUs to switch [chars]. Reload cancelled and switch will be declared incompatible |
SMU sync failed on newly joined switch. |
iosxe-p-smu |
Switch with mismatch will be declared incompatible. Check the space on the remote switch. Check whether the file is present on active. |
BOOT-3-COMP_SW_TREE_DIR_CREATION |
3-Error |
COMP_SW_TREE directory is being generated |
If chasfs/issu directory is missing on active, this message is displayed and the directory and its contents are being regenerated |
iosxe-binos-utils |
No user action is necessary. This is an informative message. |
BOOT-3-DUAL_BOOT_MEMORY |
3-Error |
Dual IOS boot indicated in ROMMON ([chars]), unavailable on [chars] RP |
Running two IOS instances on the same RP is unavailable on route-processors with insufficient memory |
iosxe-binos-utils |
Unset the specified ROMMON variable or increase the memory on the route-processor. |
BOOT-3-EXT_ISSU_CHK_FAILED |
3-Error |
Detected booting up of standby RP with image beyond the ISSU domain of active RP by the [chars] process. The standby RP is forced to reset. |
If standby RP is booted up with an image which is beyond the ISSU software domain of the active RP's image, the functionality of active RP may be unpredictable. Hence the standbby is being reset. |
iosxe-binos-utils |
Remove the standby RP FRU from the chassis or boot it up with an image whose version is compatible with current running active RP. |
BOOT-3-FLASH_READ_FAIL |
3-Error |
failed to get [chars] from flash |
Property not populated. |
iosxe-binos-utils |
No user action is necessary. This is informative message. |
BOOT-3-FSCK_FAILED |
3-Error |
filesystem on [chars] contains errors fsck couldn't resolve. |
A device's file system consistency check failed & fsck utility was unable to repair it. |
iosxe-binos-utils |
If this occurs frequently, contact Cisco technical support representative. |
BOOT-3-OPMODE_ERR |
3-Error |
Device-mode error : [chars] |
The system has encountered a device-mode failure during boot. |
iosxe-binos-utils |
The device-mode booting err information captured with console logging For information, try show platform softwate device-mode CLI. |
BOOT-3-PARTIAL_CORE_CLEANUP_FAILURE |
3-Error |
Partial core clean up failed for [chars]: [chars] |
During RP boot, a failure occurred cleaning up incomplete core files. |
iosxe-binos-utils |
Please check the router file systems. |
BOOT-3-SYSD_STARTFAIL |
3-Error |
Failed to launch boot task [chars] ( [chars] ) |
A boot task failed to start. |
iosxe-binos-utils |
If the failed boot task is not something that needs to be corrected, do not address this message. If the failed boot task needs to be addressed, install new software and reload the router. |
BOOT-4-BOOT_CORRUPT |
4-Warning |
Boot Partition corrupted. |
Boot Parition on the router is corrupted. Router booting from bootflash. |
iosxe-binos-utils |
Contact Cisco technical support. |
BOOT-5-BOOTTIME_RB_SYNC_FAILED |
5-Notice |
Failed to sync the SMUs to switch [chars]. Install rollback operation may get affected. |
Rollback point sync failed on newly joined switch. |
iosxe-p-smu |
Switch will not have the rollback points. Check the space on the remote switch. |
BOOT-5-BOOTTIME_SMU_MISMATCH_DETECTED |
5-Notice |
SMU mismatch from active detected. SMUs will be copied and switch [chars] will be reloaded |
SMU mismatch found on newly joined switch. |
iosxe-p-smu |
Switch with mismatch will be reloaded |
BOOT-5-BOOTTIME_SMU_RUN_MISMATCH_DETECTED |
5-Notice |
Running SMU mismatch from active dectected. System will try to correct it, switch [chars] will be reloaded |
Running version of SMU mismatch found on newly joined switch. |
iosxe-p-smu |
Stack will try to correct itself. |
BOOT-5-BOOTTIME_SMU_TEMP_ACTIVE_DETECTED |
5-Notice |
SMU file [chars] active temporary... SMU commit is pending |
SMU file is active temporary and 'install commit' needs to be run to make it permanent. Else reload without commit will deactive this SMU. |
iosxe-p-smu |
Execute 'install commit' before reload to make activate permanent. |
BOOT-5-BOOTTIME_SMU_TEMP_DEACTIVE_DETECTED |
5-Notice |
SMU file [chars] deactive temporary... SMU commit is pending |
SMU file is deactive temporary and 'install commit' needs to be run to make it permanent. Else reload without commit will active this SMU again. |
iosxe-p-smu |
Execute 'install commit' before reload to make deactivate permanent. |
BOOT-5-OPMODE_LOG |
5-Notice |
Device-mode logging : [chars] |
The device-mode booting information.: |
iosxe-binos-utils |
The device-mode booting information captured with console logging For information, try show platform softwate device-mode CLI. |
BOOT-6-APP_START |
6-Information |
The process [chars] has started |
The process has successful launched and begun executing. |
iosxe-binos-utils |
No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. |
BOOT-6-DRV_LOAD |
6-Information |
Loaded driver [chars] |
A kernel driver that was critical to the functioning of the system was successfully loaded. |
iosxe-binos-utils |
No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. |
BOOT-6-PARTIAL_CORE_REMOVED |
6-Information |
Removed incomplete core file: [chars] |
On boot of the RP, an incomplete core file was found and removed. Incomplete core files can happen for a variety or reasons, including the coincident failure of the active RP while a core file is being generated. |
iosxe-binos-utils |
No action required. This is not an error, it is an indication that the system is cleaning up a previous error. |
BRELAY-3-LOCATE_FRU |
3-Error |
Command could not be executed. Target FRU could not be resolved |
The brelay process is responsible for determining the target of a command, either local or a remote brelay instance. Control is returned to IOSd by exiting the brelay instance. |
iosxe-binos-utils |
Check the status of the command target. Check the brelay log files for further indications as to why the initialization failed and if necessary restart the machine. |
BSHELL-3-EXEC_DIRECTIVE_FAIL |
3-Error |
[[chars]] Command directive execution failed: [chars] |
The diagnostic shell was unable to execute the requested directive. |
iosxe-binos-utils |
Check the diagnostic shell trace file for more information on the underlying failure. |
BSHELL-3-EXEC_FAIL |
3-Error |
[[chars]] Command execution failed |
The diagnostic shell was unable to execute the requested interactive command. |
iosxe-binos-utils |
Check the diagnostic shell trace file for more information on the underlying failure. |
BSHELL-3-EXEC_PREPARE_FAIL |
3-Error |
[[chars]] Command execution prepare failed |
The diagnostic shell was unable to prepare the requested interactive command for execution. The command failed. |
iosxe-binos-utils |
Check the diagnostic shell trace file for more information on the underlying failure. |
BSHELL-3-GET_HOSTNAME_FAIL |
3-Error |
[[chars]] Get hostname failed: [chars] |
The diagnostic shell was unable to read the hostname from the kernel. |
iosxe-binos-utils |
No action is required. The diagnostic shell periodically checks for hostname changes to set the user prompt. |
BSHELL-3-RECEIVE_MESSAGE_FAILED |
3-Error |
[[chars]] Receive message [chars] failed: [chars] |
The diagnostic shell was unable to receive a message from the Shell Manager |
iosxe-binos-utils |
Retry the operation or start a new diagnostic shell session. |
BSHELL-3-SEND_MESSAGE_FAILED |
3-Error |
[[chars]] Send message [chars] failed: [chars] |
The diagnostic shell was unable to send a message to the Shell Manager. |
iosxe-binos-utils |
Retry the operation or start a new diagnostic shell session. |
BSHELL-3-TERMINAL_OPERATION_FAIL |
3-Error |
[[chars]] Terminal [chars] [chars] failed: [chars] |
The diagnostic shell was unable to get or set terminal properties. An attempt to change or act on terminal properties failed. |
iosxe-binos-utils |
Restart the diagnostic shell and reattempt the failed operation |
BSHELL-6-BSHELL_UPGRADE_DETECTED |
6-Information |
[[chars]] New software detected. Bshell instance restarting. |
The diagnostic shell detected a new installation of diagnostic shell software. The diagnostic shell instance exits and restarts with the new software version. |
iosxe-binos-utils |
This is an informational message only. No action is required. |
BSHELL-6-SESSION_ENDED |
6-Information |
[[chars]] bshell session ended for user '[chars]' |
A user has exited a diagnostic shell session. |
iosxe-binos-utils |
This is an informational message only. No action is required. |
BSHELL-6-SESSION_STARTED |
6-Information |
[[chars]] bshell session started for user '[chars]' |
A user has started a diagnostic shell session. |
iosxe-binos-utils |
This is an informational message only. No action is required. |
BSHELL-6-SMAN_CONNECTION_FAILED |
6-Information |
[[chars]] Shell Manager connect failed: [chars] |
The diagnostic shell is unable to connect to the Shell Manager, possibly because the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress. |
iosxe-binos-utils |
No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect. |
BSHELL-6-SMAN_CONNECTION_LOST |
6-Information |
[[chars]] Shell Manager connection lost |
The diagnostic shell was disconnected from the Shell Manager and the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress. |
iosxe-binos-utils |
This is an informational message only. No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect. |
BSMRP-0-CHASFS_LOCATION_TRANSLATE |
0-Emergency |
Failed to translate a location to a chasfs object name because [chars] |
The backplane switch manager failed to translate a location to a chasfs object name. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASFS_OBJECT_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] because [chars] |
The hardware failed to create a chassis filesystem object. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASFS_OBJECT_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] not present. |
A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASFS_OBJECT_WATCH |
0-Emergency |
Failed to watch chassis filesystem object [chars] because [chars] |
A chassis filesystem object was not watched because of the reason stated in the error message. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASFS_PROPERTY_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly created. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASFS_PROPERTY_GET |
0-Emergency |
Failed to read chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly read by the system. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASFS_PROPERTY_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] property [chars] not present. |
A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASFS_PROPERTY_SET |
0-Emergency |
Failed to write chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property failed to write. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASSIS_STATUS |
0-Emergency |
Failed to get chassis hardware status because [chars] |
The system failed to get the chassis hardware status. |
esg-bsm |
Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-CHASSIS_TYPE |
0-Emergency |
The chassis type [chars] is invalid. |
The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
esg-bsm |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-INVALID_ARGUMENT |
0-Emergency |
A system function was given an invalid argument. |
A system function was given an invalid argument. This is due to a software defect. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-IPC_CONNECTION_INVALID |
0-Emergency |
An IPC connection has invalid state. |
An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-IPC_CONNECT_MASTER |
0-Emergency |
IPC connection to the active RP failed because [chars] |
IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-IPC_INITIALIZATION |
0-Emergency |
IPC initialization failed because [chars] |
IPC initialization failed. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-MESSAGE_REGISTER |
0-Emergency |
Failed to register with active RP because [chars] |
The active RP failed to register. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-MESSAGE_RELAY |
0-Emergency |
Failed to relay a message because [chars] |
Failed to relay a message. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-MESSAGE_RESPONSE |
0-Emergency |
An invalid message response was received because [chars] |
An invalid message response was received. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-MQIPC_ADVANCE |
0-Emergency |
Failed to advance MQIPC queue because [chars] |
The MQIPC initialization failed. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-MQIPC_INITIALIZATION |
0-Emergency |
MQIPC initialization failed because [chars] |
MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-PEER_TABLE |
0-Emergency |
A peer table initialization or maintenance function failed because [chars] |
A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-PLATFORM_FAMILY_TYPE |
0-Emergency |
The platform family type [chars] is invalid. |
The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
esg-bsm |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-RESOLVE_FRU |
0-Emergency |
Failed to determine [chars] card because [chars] |
The router failed to determine a FRU state. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-SERVICES_INITIALIZATION |
0-Emergency |
Failed to initialize general application services because [chars] |
The system failed to initialize application services. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-SIGNAL_INITIALIZATION |
0-Emergency |
Failed to initialize signals because [chars] |
The system failed to initialize signals. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-SLOTS_INITIALIZATION |
0-Emergency |
Failed to initialize chassis slot information because [chars] |
The system failed to initialize the chassis slot information. |
esg-bsm |
Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-SLOT_INVALID |
0-Emergency |
A card absolute slot number cannot be determined for this chassis type |
An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content. |
esg-bsm |
Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-0-UIPEER_CREATE |
0-Emergency |
Failed to create user interface peer. |
The system failed to create a user interface peer. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-3-BSM_SERVICE_SETUP |
3-Error |
Failed to setup the backplane switch manager (bsm) service |
Backplane Switch Manager failed to set itself up as a proxy to the backplane switch. |
esg-bsm |
Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-3-CHASFS_OBJECT_DESTROY |
3-Error |
Failed to destroy chassis filesystem object [chars] because [chars] |
A chassis filesystem object that should have been destroyed was not destroyed. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-3-CHASFS_PROPERTY_DESTROY |
3-Error |
Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] |
A chassis filesystem property that should have been destroyed was not destroyed. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSMRP-3-PEER_INVALID |
3-Error |
A peer table entry has invalid state. |
A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion. |
esg-bsm |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
BSSID_MGR_TRACE_MSG-3-WLC_GEN_ERR_TB |
3-Error |
Error in [chars] |
General Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
BTRACE_MANAGER-3-BTRT_ERR_MSG |
3-Error |
Btrace Rotate Error: [chars] |
Btrace Rotate error message. |
iosxe-binos-utils |
LOG_STD_ACTION |
BTRACE_MANAGER-4-FILTER_CONFIG |
4-Warning |
Btrace Manager UTF Filter Applied from conf file: [chars] |
Btrace Filter Manager |
polaris-trace |
No action required |
BTRACE_MANAGER-7-BTRT_LOG_MSG |
7-Debug |
Btrace Export: [chars] |
Btrace export info |
iosxe-binos-utils |
No action required |
CAC_TRACE_MESSAGE-5-EWLC_GEN_ERR |
5-Notice |
Call admission control : [chars] |
General ewlc Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
CAPWAPAC_SMGR_TRACE_MESSAGE-3-DUPLICATE_IP_PORT |
3-Error |
IP-Port mapped to more than one AP. [chars] |
If the APs are behind NAT/PAT, one of the port is possibly mapped to multiple APs. Client may not be able to join this AP |
ewlc-ap |
If the APs are behind NAT/PAT, kindly check if same port is mapped to multiple APs |
CAPWAPAC_SMGR_TRACE_MESSAGE-3-WLC_GEN_ERR |
3-Error |
Error in [chars] |
General ewlc Error Message. |
ewlc-ap |
LOG_STD_ACTION |
CAPWAPAC_SMGR_TRACE_MESSAGE-4-AP_MSG_THRESHOLD |
4-Warning |
Warning : [chars] |
Number of messages in capwap queue crossed the threshold(exceeded or recovered) |
ewlc-ap |
LOG_STD_NO_ACTION |
CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN |
5-Notice |
AP Event: [chars] |
AP Join/Disjoin Event |
ewlc-ap |
LOG_STD_NO_ACTION |
CAPWAPAC_SMGR_TRACE_MESSAGE-6-WLC_APMGR_INFO |
6-Information |
Info : - [chars] |
General Wireless LAN Controller info message |
ewlc-ap |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-2-MAX_SUPPORTED_AP_LIMIT_90PCT_EXCEEDED |
2-Critical |
90%% ([dec]) of Maximum Supported AP Join Limit: [dec] exceeded |
Exceeded 90% of maximum supported AP join limit |
ewlc-ap |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-2-MAX_SUPPORTED_AP_LIMIT_EXCEEDED |
2-Critical |
Maximum supported AP join limit: [dec] exceeded |
Maximum supported AP join limit exceeded |
ewlc-ap |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-3-MAX_AP_LIMIT_REACHED |
3-Error |
Ap [chars] will be disconnected. Maximum AP Join Limit: [dec] Reached |
Maximum AP join limit reached error |
ewlc-ap |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-3-MAX_LICENSE_AP_LIMIT_REACHED |
3-Error |
Ap [chars] is not allowed to join. Please start reporting licensing to Cisco to get the ACK for resumption of normal operation. |
Device is not registered, maximum AP join limit reached error |
ewlc-ap |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-4-EWC_AP_JOIN_DISABLED_DURING_PNP |
4-Warning |
Attempt by AP [chars] with MAC [chars] to join this controller was rejected due to PnP image download in progress |
External AP is not allowed to join when internal AP image upgrade is going on as part of PnP image download |
ewcap-image |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-4-EWC_AP_JOIN_DISABLED_DURING_PREDOWNLOAD |
4-Warning |
Attempt by AP [chars] with MAC [chars] to join this controller was rejected due to network upgrade |
New AP is not allowed to join during network upgrade |
ewcap-image |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-4-EWC_AP_JOIN_DISABLED_WNCDS_CONFIG_INIT_STILL_IN_PROGRESS |
4-Warning |
Attempt by AP with MAC [chars] to join this controller was rejected as WNCDs config init still in progress |
External AP is not allowed to join as WNCD processes are still being initialized with wlan/policy/site configs |
ewlc-app-infra |
LOG_STD_ACTION |
CAPWAPAC_TRACE_MSG-4-EWC_INTERNAL_AP_JOIN_DISABLED_DURING_PNP_NO_PROVISION |
4-Warning |
Attempt by Internal AP [chars] with MAC [chars] to join this controller was rejected due to PnP Image Dwonload is in progress and PnP Provision is not Done |
Internal AP is not allowed to join in PnP image upgrade flow till the PnP Provision is done |
ewcap-image |
LOG_STD_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_ACTIVE_CHECK_FAILED |
3-Error |
Unable to determine name of AP running active controller. Please ensure internal AP has joined and try again |
Installer needs to check that the configured preferred master matches the current active controller AP name before reloading. However it was unable to determine the active controller AP name, probably because the internal AP has not joined. Please ensure that the internal AP has joined and then try again |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_ACTIVE_NOT_PREFERRED_MASTER |
3-Error |
The configured preferred master AP name does not match the current active controller AP name. Please configure the preferred master AP name with 'wireless ewc-ap preferred-master' to match the active controller AP name as shown by 'show wireless ewc-ap redundancy summary' and try again |
Installer requires that the configured preferred master matches the current active controller AP name before reloading. Please ensure that the preferred master is configured correctly and then try again |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_DOWNLOAD_ERROR |
3-Error |
Configured image download profile failed to download version.info; check network and server configuration |
Configured image download profile may not be able to download the correct AP images |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_DOWNLOAD_START_FAILURE |
3-Error |
Failed to start downloading AP image version with error [chars] |
Configured image download profile may not be able to download the correct AP images |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_DWNLD_IMG_MASTER_INTERNAL_AP |
3-Error |
External download for internal AP cannot start, a previous download has been already performed. |
EWC image upgrade workflow requires mandatory download for new image master AP required by the internal AP. If a previous 'install add' has been performed without ativation, an 'install remove' action is needed to clear fully the previous downloads. |
ewcap-image |
Execute 'install remove profile default', 'clear ap predownload statistics', and retry Network Upgrade |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_EXTERNAL_DOWNLOAD_IN_PROGRESS |
3-Error |
Controller performs another external transfer, for example a new AP joins the network. Once transfer completed, please try Network Upgrade again |
EWC allows only one active image transfer. For an AP join case, such a transfer has to be completed/aborted before a Network Upgrade is started. |
ewcap-image |
Check 'show ap summary'. If the number of APs is the expected one, update the image download profile to point to the new software version, and retry Network Upgrade |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_GEN_ERR |
3-Error |
%% Error: [chars] |
Network not ready for this install command |
iosxe-binos-utils |
Try again later |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_NO_SPACE |
3-Error |
No sufficient space on bootflash for upgrade. Please do 'dir bootflash:' to list and delete unwanted files. Please do 'install remove profile default'. |
No sufficient space on flash to hold the image, please do some cleanup on bootflash: |
iosxe-binos-utils |
Try 'install remove profile default' |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_PREDOWNLOAD_REQUIRES_POLL_CCO_FIRST |
3-Error |
Please do poll-cco once before starting EWC-AP software predownload via CCO |
EWC-AP software prodownload via CCO requires polling CCO first to get suggested/latest software version |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_INTERNAL_AP_JOIN_IN_PROGRESS |
3-Error |
Internal AP has not joined the controller. Once internal AP is up, please try Network Upgrade again. |
If internal AP is not present Network Upgrade can not start. |
ewcap-image |
Check 'show ap summary'. Wait for internal AP is present before Network Upgrade start |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_GEN_ERR |
3-Error |
%% Error: [chars] |
Improper arguments or config |
iosxe-binos-utils |
Arguments to be changed |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-4-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_MISMATCH |
4-Warning |
Configured image download profile downloads AP image version [chars]; requires AP image version [chars] to join this controller |
Configured image download profile does not work for AP join |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-4-CAPWAPIMGDWNLD_EWC_PREMATURE_ACTIVATE |
4-Warning |
Image predownload is still in progress, 'install activate' might lead to a longer upgrade of the network |
Not all APs might have the new image yet |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-5-CAPWAPIMGDWNLD_EWC_AP_AP_LIST_EVENTS |
5-Notice |
List Event: [chars] |
EWC-AP Master/Invalid Master AP list insertion/deletion/reelection Events |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_AP_IMAGE_DELETED |
6-Information |
AP Event: Downloaded AP image [chars] was deleted |
Downloaded AP image deleted |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_AP_IMAGE_WITHOUT_NODE_DELETED |
6-Information |
AP Event: Downloaded AP image [chars] without image node was deleted |
Downloaded AP image deleted from RAM disk |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_MATCH |
6-Information |
Configured image download profile downloads AP image version [chars], matching required AP image version to join this controller |
Configured image download profile works for AP join |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_DWNLD_COMPLETE_WITHOUT_NODE_DELETED |
6-Information |
AP Event: External Download complete and deleted for AP image [chars] without image node |
Downloaded AP image deleted from RAM disk |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_HARDDISK_CLEANUP |
6-Information |
corefiles and/or tracelogs have been deleted, [dec] Bytes disk space is freed |
corefiles and tracelogs have been deleted |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_IMAGE_MMAPED |
6-Information |
EWC-AP Event: EWC-AP Controller image [chars] mmaped ... Timer started to unmap |
EWC-AP Image MMaped in Memory |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_IMAGE_MMAPED_RESET |
6-Information |
EWC-AP Event: EWC-AP Controller image [chars] already mmaped in memory ... Timer to unmap reset |
EWC-AP Image MMaped in Memory |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_IMAGE_MUNMAPPED |
6-Information |
EWC-AP Event: EWC-AP Controller image [chars] unmapped from memory ... Timer to unmap Stopped |
Controller image unmapped from memory |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_PREDOWNLOAD_AP_COUNT_MISMATCH |
6-Information |
AP Event: Predownload Total AP count [dec], predownloaded AP count [dec] |
Predownload Total and Completed AP count mismatched |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_SEND_MASTER_GOING_DOWN |
6-Information |
Sending master-going-down message to other APs so that they backoff for 5 minutes for existing active controller to be active after reload |
To prevent EWC-AP-capable AP's from becoming EWC-AP controller when current controllr goes through reload, send master-going-down message to them so they wait 5 minutes for the current controller to reboot and become controller again |
ewcap-image |
LOG_STD_NO_ACTION |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_WRONG_STATE |
6-Information |
Network upgrade is not in correct state. Please do 'install remove profile default', and try again |
Network Upgrade is not in correct state. Please cancel and try again |
ewcap-image |
Try 'install remove profile default' |
CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-TRACE_EXPORT_TEST |
6-Information |
Btrace log export test event: Testing Log Export Feature |
GUI Triggered Flow to test Log Export Feature |
ewcap-image |
LOG_STD_NO_ACTION |
CERT-1-CERT_EXPIRED |
1-Alert |
Certificate expired |
This alert syslog is generated when the certificate used for DTLS/TLS connection towards SD-WAN controller has expired. Control connection to controllers will not come up as a result of this catastrophic failure |
vip-certificate |
Please contact Cisco TAC |
CERT-1-CERT_EXPIRING |
1-Alert |
Certificate expiring soon. Time remaining: [dec] [chars] |
This alert syslog is generated to warn impending certificate expiry |
vip-certificate |
New certificate should be installed prior to expiring. Please contact Cisco TAC for assistance |
CERT-3-CERT_STORE_INIT_FAILED |
3-Error |
Certificate store init failed |
This error syslog is generated when certificate store initialization fails. Control connection to controllers will not come up as a result of this failure |
vip-certificate |
Please contact Cisco TAC and open a support ticket for this issue |
CERT-5-CERT_INSTALLED |
5-Notice |
A new certificate has been installed |
This notice syslog is generated when a new certificate is installed |
vip-certificate |
No action is required |
CERT-5-CERT_UNINSTALLED |
5-Notice |
Certificate has been uninstalled |
This notice syslog is generated when an installed certificate is uinstalled by administrative action |
vip-certificate |
No action is required |
CERT-5-NEW_CSR_GENERATED |
5-Notice |
New certificate signing request generated |
This notice syslog is generated whenever new certificate signing request is generated |
vip-certificate |
No action is required |
CERT-5-ROOT_CA_CRL_INSTALLED |
5-Notice |
Root CA CRL has been installed |
This notice syslog is generated when a root CA Certificate Revocation List is installed |
vip-certificate |
No action is required |
CERT-5-ROOT_CA_CRL_UNINSTALLED |
5-Notice |
Certificate has been uninstalled |
This notice syslog is generated when a root CA Certificate Revocation List is uninstalled by administrative action |
vip-certificate |
No action is required |
CERT-5-ROOT_CERT_CHAIN_INSTALLED |
5-Notice |
Root certificate chain installed |
This notice syslog is generated when a root certificate chain is installed |
vip-certificate |
No action is required |
CERT-5-ROOT_CERT_CHAIN_UNINSTALLED |
5-Notice |
Root certificate chain uninstalled |
This notice syslog is generated when an installed root certificate chain is uninstalled by administrative action |
vip-certificate |
No action is required |
CERT_MGR_ERRMSG-3-CERT_MGR_GENERAL_ERR |
3-Error |
General error: [chars] |
General cert mgr lib error message |
ewlc-ap |
LOG_STD_ACTION |
CERT_MGR_ERRMSG-3-CERT_VALIDATION_ERR |
3-Error |
Certificate Validation Error, [chars] |
General Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
CERT_MGR_ERRMSG-3-FIPS_AUDIT_FIA_X509_EXT_1_ITT_LSC_CA_CERT |
3-Error |
LSC CA certificate not generated with CA flag true |
LSC CA certificate not generated with CA flag true |
ewlc-ap |
LOG_STD_ACTION |
CERT_MGR_ERRMSG-3-FIPS_SUITABILITY_ERR |
3-Error |
FIPS Compliance: [chars] |
General cert mgr lib error message |
ewlc-ap |
LOG_STD_ACTION |
CERT_MGR_ERRMSG-3-PKI_SSL_IPC_RESP_ERR |
3-Error |
IPC Respone Error, [chars] |
General Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
CERT_MGR_ERRMSG-3-WLANCC_UPDATE_ERR |
3-Error |
Failed to send WLAN CC (Commit Criteria) update to PKI IOSd due to database error |
General Wireless LAN Controller Error Message. |
ewlc-ap |
LOG_STD_ACTION |
CERT_MGR_ERRMSG-4-CERT_MGR_WARNING |
4-Warning |
Warning, [chars] |
General Wireless LAN Controller warning message |
ewlc-ap |
LOG_STD_ACTION |
CERT_MGR_ERRMSG-6-FIPS_SUITABILITY_INFO |
6-Information |
FIPS Compliance: [chars] |
General cert mgr lib error message |
ewlc-ap |
LOG_STD_ACTION |
CFGMGR-3-ADMIN_PASSWD_UNCHANGED |
3-Error |
Failed to set new admin password |
This syslog is generated when the default password of admin account is not updated due to an error. This could occur during bootup when the system is initializing |
cedge-confd-startup |
Please retry updating default password for admin account. If admin password cannot be updated after couple of attempts, please contact Cisco TAC for assistance |
CFGMGR-4-ADMIN_PASSWD_CHANGE_DEFERRED |
4-Warning |
New admin password not set yet, waiting for daemons to read initial config |
This syslog is generated when the system is initializing and user tries to update default password of admin account. Once bootup completes, config database is unlocked and admin password can be changed |
cedge-confd-startup |
This should be a temporary log, if the log continues to be seen on console, please contact Cisco TAC for assistance |
CFGMGR-6-ADMIN_PASSWD_CHANGED |
6-Information |
Successfully set new admin password |
This info syslog is generated when the default password of admin account is updated |
cedge-confd-startup |
No action is required |
CFMGR_LOG-4-COUNTRY_CFG_DEPRECATED_CLI |
4-Warning |
[chars]: 'ap country <coutry-code>' is deprecated, instead use 'wireless country <country-code>' |
'ap country <code>' cli has been has been deprecated, Please start using 'wireless country <code>' instead |
ewlc-rrm |
Please start using new form of cli mentioned in the explanation message |
CFMGR_LOG-4-UNSUPPORTED_AP_DTLS_CIPHER |
4-Warning |
Unsupported AP DTLS ciphersuite: [chars] |
Unsupported ciphersuite for AP DTLS in a given security mode |
ewlc-ap |
No action required |
CFMGR_LOG-7-CFG_DOWNLOAD_LOG_MSG |
7-Debug |
Scheduled Config Download: [chars] |
Config Download info |
iosxe-binos-utils |
No action required |
CGM_NGWC-3-NOMEM |
3-Error |
No Enough Shared Memory in CGM\n |
The configuration is too large. |
INVALID |
Check the existing ACL configuration.\n |
CHASFS-3-NOCHASFSDIR |
3-Error |
The directory [chars] does not exist. |
No explanation. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
CHASFS-3-NOINOTIFY |
3-Error |
The inotify device could not be opened. Error [dec]. |
This error occurs when there is an error in the system that prevents the notification facility from being accessed. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
CHASFS-3-NOOPEN_PROPERTY |
3-Error |
Error opening chassis file system object [chars]: [chars] |
An application was not able to open a an object in its local chassis file system. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CHASFS-3-NORESOLVE_LOCAL_OBJECT |
3-Error |
Error resolving local FRU object: [chars] |
An application was not able to create a reference to an object in its local chassis file system. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CIA-0-CPA_INITIALIZATION |
0-Emergency |
cpa_init failed, return code: [dec] |
cpa_init has failed. This might be because CPA south bound libraries are missing or a mapping of CPA libraries to PD_TYPE missing in cpa_fru_db.conf |
iosxe-chassismgr |
Review cpa logs |
CLIENT_EXCLUSION_AUDIT_MESSAGE-3-FIPS_AUDIT_FTA_TSE_1_CLIENT_ASSOCIATION_REJECTED |
3-Error |
Client [chars] association rejected and excluded, reason: [chars] |
Client association rejected because of excluding |
ewlc-client |
LOG_STD_ACTION |
CLIENT_EXCLUSION_SERVER-5-ADD_TO_EXCLUSIONLIST_REASON |
5-Notice |
Client [chars] was added to exclusion list, reason: [chars] |
Client was added to exclusion list |
ewlc-client |
Message notification informing about the client was added to exclusion list |
CLIENT_EXCLUSION_SERVER-5-ADD_TO_EXCLUSIONLIST_REASON_DYNAMIC |
5-Notice |
Client [chars] was added to exclusion list associated with AP Name:[chars], BSSID:[chars], reason:[chars] |
Client was added to exclusion list |
ewlc-client |
Message notification informing about the client was added to exclusion list |
CLIENT_HA_SVC_MESSAGE-3-EWLC_RECREATE_ERR |
3-Error |
Heap recreate failure in module [chars]. [chars] |
Failure seen during heap recreate |
iosxe-binos-utils |
LOG_STD_ACTION |
CLIENT_IPV6_TRACE_MESSAGE-3-CLIENT_IPV6_CRIT_ERR |
3-Error |
client_ipv6 Error: [chars] |
Client IPv6 Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
CLIENT_IPV6_TRACE_MESSAGE-4-CLIENT_IPV6_WARN |
4-Warning |
client_ipv6 Warning: [chars] |
Client IPv6 Warning Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_GTK_UNABLE_TO_UPDATE_BROADCAST_KEYS_TO_CLIENT |
3-Error |
User ID: [chars] - Unable to update broadcast keys to Client |
Unable to update broadcast keys to Client |
ewlc-client |
LOG_STD_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_DEFLECTION_ATTACK |
3-Error |
User ID: [chars] - Deflection attack detected from this mobile |
Deflection attack detected from this mobile |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_KEY_DATA_LEN |
3-Error |
User ID: [chars] - Invalid key data length |
Invalid key data length |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_KEY_TYPE |
3-Error |
User ID: [chars] - Invalid key type |
Invalid key type |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_MIC |
3-Error |
User ID: [chars] - Received Invalid MIC in EAPOL Key Message handshake |
Received Invalid MIC in EAPOL Key Message handshake |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_MIC_IN_M2 |
3-Error |
User ID: [chars] - Received Invalid MIC in EAPOL Key Message M2 |
Received Invalid MIC in EAPOL Key Message M2 |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_REPLAY_WINDOW |
3-Error |
User ID: [chars] - Invalid Replay Window |
Invalid Replay Window |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_SECURE_BIT |
3-Error |
User ID: [chars] - Invalid secure bit |
Invalid secure bit |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_ZERO_MIC |
3-Error |
User ID: [chars] - Zero MIC received |
Zero MIC received |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PTK_UNABLE_TO_SEND_SESSION_KEY_TO_AP |
3-Error |
User ID: [chars] - Unable to send Session key to AP |
Unable to send Session key to AP |
ewlc-client |
LOG_STD_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FTA_TSE1_DENY_CLIENT_ACCESS |
3-Error |
User ID: [chars] - - Client association denied as it is not in Active Hours slot [chars] |
Received association request in non-active hours |
ewlc-client |
LOG_STD_RECUR_ACTION |
CLIENT_ORCH_AUDIT_MESSAGE-6-FIPS_AUDIT_FIA_8021X_EXT_1_CLIENT_ASSOCIATION_RECEIVED_FROM_MOBILE |
6-Information |
[chars] [chars]: [chars] Association received from mobile on BSSID [chars] AP [chars] |
Association received from mobile on BSSID |
ewlc-client |
LOG_STD_ACTION |
CLIENT_ORCH_GUEST_LAN_LOG-3-CLIENT_JOIN_FAILED |
3-Error |
Wired Guest client [chars] failed joining on vlan [dec] physical interface [chars]. Reason: [chars] |
Wired Guest client failed joining |
ewlc-client |
If this message occurs, client failed joining and was deleted. |
CLIENT_ORCH_GUEST_LAN_LOG-3-CLIENT_JOIN_FAILED_NO_MAC |
3-Error |
Refusing creation of wired Guest client with no MAC on vlan [dec] physical interface [dec]. |
Wired Guest client failed joining |
ewlc-client |
If this message occurs, client failed joining and was deleted. |
CLIENT_ORCH_GUEST_LAN_LOG-5-CLIENT_JOIN_IGNORED |
5-Notice |
Already existing client [chars] join request on vlan [dec] and physical interface [chars] was ignored |
A request to join the client was ignored because the client is already connected |
ewlc-client |
No action is required |
CLIENT_ORCH_GUEST_LAN_LOG-7-CLIENT_RECEIVED |
7-Debug |
Wired Guest Client [chars] join request received on vlan [dec] - interface [chars] |
New Wired Guest client join received |
ewlc-client |
No action is required |
CLIENT_ORCH_LOG-3-CLIENT_TRACEBACK |
3-Error |
Error in [chars] |
General Client Error Message. |
ewlc-client |
LOG_STD_ACTION |
CLIENT_ORCH_LOG-4-ANCHOR_INVALID_MBSSID |
4-Warning |
Export anchor required but config is incorrect (e.g.: wlan should be up, wlan profile name and policy profile name should match) for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] |
Export anchor required but config is incorrect (e.g.: wlan should be up, wlan profile name and policy profile name should match) |
ewlc-guest |
If this message occurs, it implies that Wlan needs to be up or wlan profile name and policy profile name need to match |
CLIENT_ORCH_LOG-4-ANCHOR_INVALID_WLAN_ID |
4-Warning |
Export anchor required but unable to get wlan id for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] |
Export anchor required but unable to get wlan id |
ewlc-guest |
If this message occurs, it implies that Wlan name is not configured |
CLIENT_ORCH_LOG-4-ANCHOR_NOT_EXPORT_WLAN |
4-Warning |
Export anchor required but wlan not configured as mobility export anchor for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] |
Export anchor required but wlan not configured as mobility export anchor |
ewlc-guest |
If this message occurs, it implies that Wlan is not configured as mobility export anchor |
CLIENT_ORCH_LOG-4-ANCHOR_VAP_SECURITY_MISMATCH |
4-Warning |
Export anchor required but local and remote security/profile configuration is not matching for: Wlan-Profile: [chars], Policy-Profile: [chars] client [chars] |
Export anchor required but local and remote security/profile configuration (wlan and/or policy profile) is not matching |
ewlc-guest |
If this message occurs, it implies that local and remote wlan and policy profiles need to have the same security or configuration settings |
CLIENT_ORCH_LOG-4-ANCHOR_WEBAUTH_ON_MAB_NOT_CONFIGURED |
4-Warning |
Export anchor: webauth on mac failure configuration mismatch between anchor and foreign for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] |
Webauth on Mac Failure configuration mismatch between anchor and foreign |
ewlc-guest |
If this message occurs, it implies that Wlan on anchor or foreign is not configured for webauth on mac failure |
CLIENT_ORCH_LOG-5-ADD_TO_EXCLUSIONLIST_MAC_THEFT_REASON |
5-Notice |
Client [chars] with IP: [chars] was added to exclusion list, legit ifid: 0x%08x, current ifid: 0x%08x, reason: [chars] |
Blacklisting client on MAC address theft. |
ewlc-client |
If this message occurs, it implies that there was MAC address theft. |
CLIENT_ORCH_LOG-5-ADD_TO_EXCLUSIONLIST_REASON |
5-Notice |
Client [chars] with IP: [chars] was added to exclusion list, legit Client [chars], IP: [chars], reason: [chars] |
Blacklisting client on IP address theft or MAC address theft or IP and MAC address theft. |
ewlc-client |
If this message occurs, it implies that there was IP theft or MAC address theft or IP and MAC address theft. |
CLIENT_ORCH_LOG-5-EASYPSK_CLIENT_DELETED |
5-Notice |
Easy-PSK client [chars] : client deleted due because AAA exchange failed reason [chars]. |
Easy-PSK client was deleted because of AAA Exchange failure. |
ewlc-client |
If this message occurs, it implies that client was deleted due to AAA exchange failure. |
CLIENT_ORCH_LOG-5-WEBAUTH_ON_MAB_FAILURE_ROAMING_DENIED |
5-Notice |
Client [chars] : Roaming denied, reason: [chars] |
Roaming denied for Webauth on MAB failure client. |
ewlc-client |
If this message occurs, it means that roaming occurred with controllers with different MAC authentication lists. |
CLIENT_ORCH_LOG-6-CLIENT_ADDED_TO_RUN_STATE |
6-Information |
Username entry ([chars]) joined with ssid ([chars]) for device with [chars] on channel ([dec]) |
Details for client when it goes to run state |
ewlc-client |
If this message occurs, it implies that client successfully went to RUN state |
CLIENT_ORCH_LOG-7-CLIENT_IP_UPDATED |
7-Debug |
Username ([chars]), [chars], IP [chars]IP address updated, [chars] to AP ([chars]) with SSID ([chars]) |
Details for client when it goes to run state |
ewlc-client |
If this message occurs, it implies that client successfully went to RUN state |
CLIENT_ORCH_LOG-7-CLIENT_MOVED_TO_DELETE_STATE |
7-Debug |
Username ([chars]), [chars], IP [chars]disconnected from AP ([chars]) with SSID ([chars]) |
Details for client when it goes to delete state |
ewlc-client |
If this message occurs, it implies that client successfully went to DELETE state |
CLIENT_ORCH_LOG-7-CLIENT_MOVED_TO_RUN_STATE |
7-Debug |
Username ([chars]), [chars], IP [chars][chars] to AP ([chars]) with SSID ([chars]) on channel ([dec]) |
Details for client when it goes to run state |
ewlc-client |
If this message occurs, it implies that client successfully went to RUN state |
CLIENT_ORCH_VLAN_OVERRIDE_LOG-7-CLIENT_VLAN_OVERRIDE |
7-Debug |
Client [chars] on wlan [chars] and policy profile [chars] received a vlan override after web-authentication and it is moved to the new VLAN to learn a new IP |
The client received a vlan override after web-authentication |
ewlc-client |
No action is required |
CLIENT_ORCH_VLAN_OVERRIDE_LOG-7-CLIENT_VLAN_OVERRIDE_TIMEOUT |
7-Debug |
Client [chars] on wlan [chars] and policy profile [chars] failed to re-associate and learn a new IP after the VLAN Override and is deleted |
The client needs to re-associate within 30s after a vlan override otherwise it is deleted. |
ewlc-client |
No action is required |
CLIENT_ORCH_VLAN_OVERRIDE_LOG-7-FOREIGN_CLIENT_VLAN_OVERRIDE |
7-Debug |
Export foreign client [chars] on wlan [chars] and policy profile [chars] received a vlan override from export anchor |
The export foreign client received a vlan override from anchor |
ewlc-client |
No action is required |
CLOUDM_ONBOARDING_DRAGONFLY-3-CLOUDM_ONBOARDING_HTTPCON_ERROR |
3-Error |
[chars] with HTTP connection error: [chars]. |
received an httpcon error while onboarding controller |
cloudm |
LOG_STD_NO_ACTION |
CLOUDM_ONBOARDING_DRAGONFLY-3-CLOUDM_ONBOARDING_HTTP_ERROR |
3-Error |
[chars] with HTTP status code [dec]. |
received an http error while onboarding controller |
cloudm |
LOG_STD_NO_ACTION |
CLOUDM_ONBOARDING_DRAGONFLY-6-CLOUDM_ONBOARDING_SUCCESS |
6-Information |
Successfully [chars] |
Successfully onboarded, otp updgraded, or received access token for device |
cloudm |
LOG_STD_NO_ACTION |
CLOUDM_ONBOARDING_SPACES-3-CLOUDM_ONBOARDING_SPACES_AUTH_TOKEN_ERR |
3-Error |
Cisco Spaces persistent credentials could not be installed for [chars] |
Spaces persistent credential installation went through errors |
cloudm |
If this message occurs, it means persistent credentials for Spaces could not be installed for errors |
CLOUDM_ONBOARDING_SPACES-3-CLOUDM_ONBOARDING_SPACES_OTP_INSTALL_ERR |
3-Error |
Cisco Spaces OTP could not be installed for [chars] |
Spaces OTP installation went through errors |
cloudm |
If this message occurs, it means OTP for Spaces could not be installed for errors |
CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_ACCESS_TOKEN |
6-Information |
Cisco Spaces access token has been updated. |
Updated access token for Spaces |
cloudm |
If this message occurs, it means access-token for Spaces have been installed |
CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_ACCESS_TOKEN_ERR |
6-Information |
Cisco Spaces access token could not be installed for [chars] |
Spaces access token installation went through errors |
cloudm |
If this message occurs, it means access token for Spaces could not be installed for errors |
CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_AUTH_TOKEN |
6-Information |
Cisco Spaces persistent credentials have been installed |
Installed persistent client-credentials for Spaces |
cloudm |
If this message occurs, it means client-credentials for Spaces have been installed |
CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_OTP_INSTALL |
6-Information |
Cisco Spaces OTP has been installed |
Installed OTP for Spaces |
cloudm |
If this message occurs, it means OTP for Spaces has been installed |
CLOUDM_TEST-6-HTTP_RESPONSE |
6-Information |
Completed: [chars] |
Result of the test request |
iosxe-ui |
LOG_STD_NO_ACTION |
CLUSTERMGR-1-PLATFORM_MISMATCH |
1-Alert |
\n Platform mismatch detected. A stack cannot be formed with peer switch: [chars] |
The peer switch is incompatible and cannot join the stack. |
polaris-clustering |
Replace peer switch with platform compatible switch |
CLUSTERMGR-1-RELOAD |
1-Alert |
\n Reloading due to reason [chars] |
The specified switch has received a reload request and is being reloaded. |
polaris-clustering |
No action is required |
CLUSTERMGR-6-DUAL_ACTIVE_CFG_MSG |
6-Information |
\n Dual Active Detection [chars] |
Switch detected availability or unavailability of Dual Active Detection ports. |
polaris-clustering |
No action is required |
CMAN_IDPROM_ENVMON-3-CMAN_IDPROM_FIELD_INVALID |
3-Error |
The idprom contains an invalid environmental monitoring field. |
If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMAN_LED-6-BEACON_LED_TURNED |
6-Information |
Slot [dec] Beacon LED turned [chars] |
Beacon LED turned ON/OFF. This is a notification message only.No action is required. |
iosxe-chassismgr |
This is a notification message only. No action is required. |
CMAN_NYQ-1-CMAN_INIT_FAIL |
1-Alert |
CMAN: [chars]\n |
CMAN Initialization has failed. |
iosxe-chassismgr |
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. |
CMAN_SEM-2-SEM_ERR |
2-Critical |
SEM event has occurred in device [chars]. Event code: [dec] |
A Single Event Upset (SEU) event has occurred in one of the FPGA. These events may occur at any point of time, but are considered to be rare. |
iosxe-chassismgr |
If the error is seen only once, there is no need for anything to be done. If these errors are appearing continuously/persistently, please copy over the logs as they appear in the console, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
CMAN_SYM-1-CMAN_INIT_FAIL |
1-Alert |
CMAN: [chars]\n |
CMAN Initialization has failed. |
iosxe-chassismgr |
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. |
CMCC-0-C2W_INITIALIZATION |
0-Emergency |
The SIP C2W has failed initialization because [chars] |
The C2W bus on the SIP is used to read the shared port adapter (SPA) IDPROM. This error indicates that the SIP C2W bus failed to initialize. |
iosxe-chassismgr |
Examine the logs for C2W driver errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_LOCATION_TRANSLATE |
0-Emergency |
Failed to translate a location to a chasfs object name because [chars] |
The system failed to translate a data sensor location to the chassis filesystem (CHASFS) module. This error could be caused by a software defect. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_OBJECT_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] because [chars] |
The system failed to create a chassis filesystem object. This error could be caused by a software defect or a filesystem failure. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_OBJECT_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] not present. |
The system was unable to find an expected chassis filesystem object. This error could be caused by a software defect or a filesystem failure. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_OBJECT_WATCH |
0-Emergency |
Failed to watch chassis filesystem object [chars] because [chars] |
The system failed to watch a chassis filesystem object. This error could be caused by a software defect or a filesystem failure. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_PROPERTY_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] property [chars] because [chars] |
The system failed to create a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_PROPERTY_GET |
0-Emergency |
Failed to read chassis filesystem object [chars] property [chars] because [chars] |
The system failed to read a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_PROPERTY_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] property [chars] not present. |
The system cannot locate a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASFS_PROPERTY_SET |
0-Emergency |
Failed to write chassis filesystem object [chars] property [chars] because [chars] |
The system failed to write a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CHASSIS_TYPE |
0-Emergency |
The chassis type [chars] is invalid. |
The system has detected an invalid chassis type. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content. |
iosxe-chassismgr |
Examine the logs for IDPROM or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CPLD_INITIALIZATION |
0-Emergency |
The SIP CPLD has failed initialization :[chars] |
A SIP complex programmable logic device (CPLD) failed to initialize. This error could be caused by a hardware or software driver defect. |
iosxe-chassismgr |
Examine the logs for CPLD driver or hardware errors. Verify that the software and CPLD versions are compatible. |
CMCC-0-CPLD_INTR_ENABLE |
0-Emergency |
The CPLD initialization has failed because [chars] |
The CPLD interrupt enable failed to initialize. This error could be caused by a hardware defect or CPLD driver defect. |
iosxe-chassismgr |
Examine the logs for CPLD driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-CPLD_IOCTL |
0-Emergency |
A CPLD driver I/O control has failed because [chars] |
A complex programmable logic device (CPLD) I/O driver control has failed. This error could be caused by a hardware or software driver defect. |
iosxe-chassismgr |
Examine the logs for CPLD driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information |
CMCC-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMCC-0-FLOW_CONTROL_MBE |
0-Emergency |
Multi-bit ECC error seen, Cause [chars], MIP100 is going to be reloaded to recover |
Non correctable multi bit errors were detected in the FPGA. |
iosxe-chassismgr |
MIP100 is reloaded to correct the error. If the problem persists, the MIP100 hardware may need to be replaced. |
CMCC-0-FPGA_INITIALIZATION |
0-Emergency |
The CC has failed initialization because [chars]. Reloading the card |
The FPGA on the carrier card has failed to initialize. This error could be caused by a hardware |
iosxe-chassismgr |
Examine the driver logs or hardware errors. Decode the core accompanied with this error. |
CMCC-0-HTDP_ENABLE |
0-Emergency |
The HTDP initialization has failed because [chars] |
The Hypertransort datapath failed to initialize. This error could be caused by a hardware defect or HTDP driver defect. |
iosxe-chassismgr |
Examine the logs for HTDP driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-HT_INITIALIZATION |
0-Emergency |
The SIP HyperTransport has failed initialization because [chars] |
A SIP HyperTransport (HT) CPU bus failed to initialize. This error could be caused by a hardware defect or HT driver defect. |
iosxe-chassismgr |
Examine the logs for HT driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-HT_IOCTL |
0-Emergency |
A SIP HyperTransport driver I/O control has failed because [chars] |
A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or HT driver defect. |
iosxe-chassismgr |
Examine the logs for HT driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-IPC_CONNECTION_INVALID |
0-Emergency |
An IPC connection has invalid state. |
An inter-process communication (IPC) connection has an invalid state. This error could be caused by a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-0-IPC_CONNECT_MASTER |
0-Emergency |
IPC connection to the active RP failed because [chars] |
The inter-process communication (IPC) connection to the active route processor (RP) failed. This error could be caused by a software defect or system resources limitation. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-0-IPC_INITIALIZATION |
0-Emergency |
IPC initialization failed because [chars] |
An inter-process communication (IPC) initialization failed. This error could be caused by a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-0-PCI_RESCAN |
0-Emergency |
The PCIE bus could not be rescanned because [chars] |
The PCIE bus failed to rescan. This error could be caused by a hardware defect, software driver defect, or improper internal configuration. |
iosxe-chassismgr |
Examine the logs for PCIE bus driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information |
CMCC-0-PEER_INVALID |
0-Emergency |
A peer table entry has invalid state. |
An invalid state occurred in a peer table entry. This error could be caused by a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-0-PLIM_HALT |
0-Emergency |
A PLIM driver has critical error [chars], [dec], param %x param %x |
A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect. |
iosxe-chassismgr |
Restart the SIP. If the problem persists, you may need to replace the PLIM. |
CMCC-0-PLIM_INITIALIZATION |
0-Emergency |
The PLIM has failed initialization because [chars] |
The physical layer interface module (PLIM) failed to initialize. This error could be caused by a hardware defect or a PLIM driver defect. |
iosxe-chassismgr |
Examine the logs for PLIM driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-PLIM_IOCTL |
0-Emergency |
A PLIM driver I/O control has failed because [chars] |
A physical layer interface module (PLIM) driver I/O has failed. This error could be caused by a hardware defect or a PLIM driver defect. |
iosxe-chassismgr |
Examine the logs for PLIM driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMCC-0-SERDES_INITIALIZATION |
0-Emergency |
The SIP Serial Bridge ASIC has failed initialization because [chars] |
The SIP serial bridge ASIC failed to initialize. This error could be caused by a hardware defect, software driver defect, or improper internal configuration. |
iosxe-chassismgr |
Examine the logs for serial bridge ASIC driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information |
CMCC-0-SERVICES_INITIALIZATION |
0-Emergency |
Failed to initialize general application services because [chars] |
The system failed to initialize certain application services. This error could be caused by a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-0-UIPEER_CREATE |
0-Emergency |
Failed to create user interface peer. |
The system failed to create a user interface peer. This error could be caused by a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-2-BAD_ID_HW |
2-Critical |
Failed Identification Test in [chars]. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. |
Hardware in the specified location could not be identified as a genuine Cisco product |
cbr-platform-infra |
Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information |
CMCC-2-BAD_ID_HW_SLOT_STR |
2-Critical |
Failed Identification Test in [chars]. The module [chars] on the [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. |
Hardware in the specified location could not be identified as a genuine Cisco product |
iosxe-chassismgr |
Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information |
CMCC-2-CC_SPA_MOVE_SM |
2-Critical |
***** CMCC SPA SM was strucked for a minute in state: s_kill_wait for slot [dec], moving the state machine |
CMCC SPA SM was strucked for a minute in state: s_kill_wait for the line card. |
iosxe-chassismgr |
move the cmcc spa state machine. |
CMCC-2-CC_SPA_PSM_READY_NOT_RCVD |
2-Critical |
***** CMCC did not received PSM READY event [dec] sec for slot [dec]. |
CMCC SPA SM was not received PSM READY for 100 sec. |
iosxe-chassismgr |
do remove hard. |
CMCC-2-CC_SPA_STRUCK |
2-Critical |
***** CMCC SPA SM was strucked for [dec] seconds for slot [dec]. |
CMCC SPA SM was strucked for a minute in state: s_kill_wait for the line card. |
iosxe-chassismgr |
move the cmcc spa state machine. |
CMCC-2-FRU_HWPRG_UPG_FAILED |
2-Critical |
Failed to [chars] [chars] hardware programmable on [chars] in [chars]. |
Upgrade hw-programmable failed to upgrade the CPLD/FPGA firmware on the given FRU |
iosxe-chassismgr |
Reload the card and retry to program the hw-programmable. If the card fails to come up please contact TAC |
CMCC-2-FRU_HWPRG_UPG_SUCCESS |
2-Critical |
Success to [chars] [chars] hardware programmable on [chars]. Please execute the POST Upgrade CLI: upgrade hw-programmable cable <r0/r1> daybreak post-upgrade slot <slot> to finish the upgrade process |
Upgrade hw-programmable success to upgrade the CPLD/FPGA firmware on the given FRU |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-2-FRU_IOFPGA_UPG_FAILED |
2-Critical |
Failed to upgrade field programmable device on [chars] in slot [dec]. |
Upgrade of field programmable device failed |
iosxe-chassismgr |
Reload the card and retry to program the field programmable device. If the card fails to come up please contact TAC |
CMCC-2-FRU_IOFPGA_UPG_LC_PWR_CYCLE_DONE |
2-Critical |
Power cycled the [chars] in slot [dec], after FPGA upgrade. |
Power cycled the card after FPGA upgrade. |
iosxe-chassismgr |
Line card has been power cycled after FPGA upgrade. |
CMCC-2-FRU_IOFPGA_UPG_SUCCESS |
2-Critical |
Successfully upgraded the field programmable device on [chars] in slot [dec]. Power-cycling the line card. |
Upgrade field programmable device was successful on the given FRU. Line card needs to be power-cycled or removed and re-inserted for upgrade to take effect. |
iosxe-chassismgr |
Line card needs to be power cycled or removed and re-inserted for the upgrade to take effect. |
CMCC-2-FRU_LC_PWR_RESET |
2-Critical |
***** Detected power reset for the Line card in slot [dec]. To recover from the error, Line card will brought up shortly |
Detected Auto power reset(may be HW issue) for the Linecard. |
iosxe-chassismgr |
Pseudo OIR of the Line card has been to recover/bring up the card. |
CMCC-3-C2W_READ |
3-Error |
An C2W read has failed because [chars] |
An attempt to read the C2W bus has failed. This error could be caused by a hardware or software defect. |
iosxe-chassismgr |
Examine the logs for C2W driver errors. |
CMCC-3-C2W_WRITE |
3-Error |
An I2C write has failed because [chars] |
An attempt to write to the inter-integrated circuit (I2C) has failed. This error could be caused by a hardware or software defect. |
iosxe-chassismgr |
Examine the logs for I2C driver errors. |
CMCC-3-CARD_MISMATCH |
3-Error |
The CONFIG&PICTYPE in slot [dec] mismatch : CONFIG : [chars], PIC : [chars] |
The CMD and PIC in the slot mismatch. |
iosxe-chassismgr |
Shut down the LC and change the card mode or remove the pic card. |
CMCC-3-CC_HOTSWAP_CKT_FAIL |
3-Error |
Hot Swap Circuit has failed for bay [dec] |
The Hot Swap Circuit for the SPA bay has been tripped. This error could be caused by bad SPA or CC hardware. |
iosxe-chassismgr |
Examine the CMCC and PSM OIR logs. Verify whether the recovery reload could bring up the SPA |
CMCC-3-DDR_SINGLE_BIT_ERROR |
3-Error |
Single-bit DRAM ECC error: mme: [dec], sbe: [dec], address: 0x%08X, pid: [dec], name: [chars] |
The SIP DRAM experienced a single-bit error checking code (ECC) error. |
iosxe-chassismgr |
No action is required. This error is usually self-correcting. If the problem persists, you may need to replace the SIP. |
CMCC-3-FLOW_CONTROL_SBE |
3-Error |
Single-bit ECC error seen, Cause [chars] |
Self correctable single bit errors were detected in the FPGA |
iosxe-chassismgr |
This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced. |
CMCC-3-FPGA_FAIL |
3-Error |
[chars] FPGA error detected: [chars] |
A SIP field programmable logic device failure detected. This error could be caused by a hardware or software driver defect. |
iosxe-chassismgr |
Examine the logs for FPGA driver or hardware errors. Verify that the software and firmware versions are compatible. |
CMCC-3-HB_TIMEOUT |
3-Error |
Periodic Heartbeat message from RP timed out. |
RP sends periodic heartbeat message to the SIP. The SIP did not receive this heartbeat message for last timeout period. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-HT_DETACH |
3-Error |
The SIP HyperTransport has failed detachment because [chars] |
A SIP HyperTransport (HT) CPU bus failed to detach from software during SIP MDR. This error could be caused by a hardware defect or HT driver defect. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-IDPROM_ACCESS |
3-Error |
Failed access or process an IDPROM because [chars] |
The system failed to access an IDPROM or an IDPROM process failed. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content. |
iosxe-chassismgr |
Examine the logs for IDPROM or hardware errors. |
CMCC-3-IDPROM_SENSOR |
3-Error |
One or more sensor fields from the idprom failed to parse properly because [chars]. |
One or more IDPROM sensors failed to parse. This error most likely occurred because of a checksum failure in the IDPROM. |
iosxe-chassismgr |
Examine the logs for IDPROM or hardware errors. |
CMCC-3-INCOMPATIBLE_STANDBY_SUPERVISOR |
3-Error |
Standby supervisor in slot [dec] is not compatible with the Active supervisor; Standby Supervisor will be reloaded. |
Supervisor found in Standby slot may not be fully compatible with the active supervisor and may cause issues. |
iosxe-chassismgr |
Use supervisors with the same specifications to enable High Availablitly features. |
CMCC-3-LC_FPGA_UPGRADE_FAIL |
3-Error |
The FPGA upgrade request for linecard in switch [dec] slot [dec] failed. |
Upgrade of FPGA on the linecard failed |
iosxe-chassismgr |
Reload the card and retry to program the field programmable device. If the card fails to come up please contact TAC |
CMCC-3-LC_FPGA_UPGRADE_PWR_CYCLE_FAIL |
3-Error |
Power cycle failed for the linecard in switch [dec] slot [dec], after FPGA upgrade. |
Power cycle failed for the linecard after FPGA upgrade. |
iosxe-chassismgr |
OIR the card and retry to program the field programmable device. If the card fails to come up please contact TAC |
CMCC-3-MASTERSHIP_WATCH |
3-Error |
Failed to initialize a watch on the active rp because [chars] |
The cc process has failed to setup a watch on the rp chasfs active-rp property. This error is likely caused by a problem with chasfs as a whole. |
iosxe-chassismgr |
Examine the logs to determine the exact reason for the failure. |
CMCC-3-MESSAGE_RESPONSE |
3-Error |
An invalid message response was received because [chars] |
An invalid message response was received. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMCC-3-NETWORK_CLOCK_CAL_FAIL |
3-Error |
The SIP network clock jitter attenuator calibration fails |
The SIP network clock jitter attenuator calibration can not complete within certain time. This would incur some SPA LOS alarms or other error events for some SPA port types. |
iosxe-chassismgr |
Restart the SIP |
CMCC-3-NETWORK_CLOCK_CAL_START |
3-Error |
The SIP network clock jitter attenuator is calibrating |
The SIP network clock jitter attenuator is calibrating after device initilization stage. |
iosxe-chassismgr |
Restart the SIP if SPA LOS alarms are seen after this. |
CMCC-3-NETWORK_CLOCK_DH |
3-Error |
The SIP network clock jitter attenuator has entered digital holdover |
A SIP network clock jitter attenuator has entered digital holdover mode and certain SPAs may report LOS alarms. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-3-NETWORK_CLOCK_LOS |
3-Error |
The SIP network clock jitter attenuator has lost signal |
A SIP network clock jitter attenuator has lost signal from the WAN PLL and certain SPAs may report LOS alarms. |
iosxe-chassismgr |
Restart the SIP. |
CMCC-3-PLIM_DETACH |
3-Error |
The PLIM has failed detachment from software because [chars] |
The physical layer interface module (PLIM) failed to detach from software. This error could be caused by a hardware defect or a PLIM driver defect. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-PLIM_RESTART |
3-Error |
The PLIM has failed to restart because [chars] |
The physical layer interface module (PLIM) failed to restart during SIP MDR. This error could be caused by a hardware defect or a PLIM driver defect. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-PLIM_STATUS |
3-Error |
A PLIM driver informational error [chars], block %x count %x |
A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect. |
iosxe-chassismgr |
Examine the logs for PLIM or hardware errors. |
CMCC-3-SCOOBY_ILAK_FAIL |
3-Error |
Failed to bringup the Interlaken interface. Cause: [chars] |
Interlaken Rx or Tx failed for this card. This error could be caused by a hardware or software driver defect. |
iosxe-chassismgr |
Reload the Linecard. If the problem still persists, replace the Linecard. |
CMCC-3-SIP_MDR_FAIL |
3-Error |
The SIP failed Minimal Disruptive Restart because [chars] |
The SIP failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SIP by resetting the SIP hardware. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-SPA_HOTSWAP_CKT_FAIL |
3-Error |
SPA on bay [dec] has tripped the Hot Swap Circuit during power-up. |
The Hot Swap Circuit for te SPA bay has been tripped. This error could be caused by bad SPA hardware. |
iosxe-chassismgr |
Examine the CMCC and PSM OIR logs. Verify whether the recovery reload could bring up the SPA |
CMCC-3-SPA_MDR_FAIL |
3-Error |
The SPA in bay [dec] failed Minimal Disruptive Restart because [chars] |
The SPA in bay %u failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SPA by resetting the SPA hardware. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-SPA_ONLINE_REQ_TERMINATE |
3-Error |
The online request for SPA in subslot [dec]/[dec] was terminated because [chars] |
The online request for SPA in subslot %d/%u was terminated. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-SPA_PSEUDO_HARD_OIR_VFT_NOT_IMPLEMENTED |
3-Error |
The PSEUDO OIR VFT is not implemented for bay [dec] |
The pseudo OIR vft not implemented for this platform |
iosxe-chassismgr |
Do nothing |
CMCC-3-SPA_SOFT_STOP_FAIL |
3-Error |
The SPA in bay [dec] could not be soft stopped because [chars] |
The SPA in bay %u could not be soft stopped. An attempt will be made to recover the SPA by resetting the SPA hardware. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-SSD_PIDA_OIR |
3-Error |
Hot insertion/removal of SSD module in [dec]/[dec] not supported. Please reload the router with SSD module installed in bay 3 |
Hot swapping of SSD is not supported |
iosxe-chassismgr |
Reload the router with SSD module installed in bay 3. |
CMCC-3-STANDBY_EOBC_LINK_ERROR |
3-Error |
Standby EOBC link error detected. |
Standby EOBC link error: either link state is down, or duplexity is not full, or speed is not 1Gbps. |
iosxe-chassismgr |
Examine the system hardware. Re-seat and securely screw in all FRUs. If the problem persists, please contact TAC support. |
CMCC-3-UNKNOWN_3RDPARTY_MODULE |
3-Error |
Unknown 3rd-party module was inserted in subslot [dec]/[dec]. please check whether the 3rdparty-mode is configured for this subslot |
Unknown 3rd-party module was inserted in the given subslot. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMCC-3-UNKNOWN_SPA_LC |
3-Error |
Unknown SPA was inserted in slot [dec] |
Unknown SPA was inserted in the given slot. |
iosxe-chassismgr |
Remove the unsupported SPA line card and upgrade the software as needed. |
CMCC-3-UNSUPPORTED_LC_TYPE |
3-Error |
An unsupported card of type [chars] is inserted in slot [dec] of the chassis. Remove the card from the chassis or upgrade to an image which supports the card |
Unsupported line card was inserted in the given slot. |
iosxe-chassismgr |
Remove the unsupported SPA line card and upgrade the software as needed. |
CMCC-5-C9400X_LC |
5-Notice |
C9400X-SUP-2 supports 240G per slot with [chars] installed in Slot [dec] |
Informational message that 480G Linecard is installed in the chassis with Supervisor card that supports only 240G per slot. |
iosxe-chassismgr |
Informational notification. No action is required. |
CMCC-5-CMCC_EZMAN_HB_MISS_EXCEED |
5-Notice |
CMCC Missed [dec] Heartbeats from EZMAN, Reloading the Line Card |
CMCC Monitors the Health of the EZMAN by keeping a track of the Heartbeat messages. In case the EZMAN gets stuck in a event under watchdog disable context (sw_wdog_disbale), then the CMCC will stop getting these updates. The CMCC after a certain period of time would reset the card, since EZMAN is unresponsive |
asr1k-ether-lc |
Reload the card, a software initated to restart the EZMAN |
CMCC-5-SERDES_BLOCK_EVENT |
5-Notice |
A SerDes link informational error [chars], block %x count %x |
A serial bridge I/O event has occurred. This event is not serious but is logged for diagnostic purposes. |
iosxe-chassismgr |
No user action is required. |
CMCC-5-SERDES_RX_RESET_EVENT |
5-Notice |
Interlaken Rx Alignment Status [chars], Retry Count [dec] |
Rx Sync Failed for Interlaken, Status Timer Expired. So, Resetting the Rx Interlaken Core |
asr1k-chassismgr |
No user action is required. |
CMCC-5-SPA_MDR_DONE |
5-Notice |
SPA[dec] completed Minimal Disruptive Restart |
Informational message that the Minimal Disriptive Restart of a particular SPA has completed. |
iosxe-chassismgr |
Informational notification. No action is required. |
CMCC-5-SPA_MDR_INIT |
5-Notice |
SPA[dec] initiated Minimal Disruptive Restart |
Informational message that the Minimal Disriptive Restart of a particular SPA has begun. |
iosxe-chassismgr |
Informational notification. No action is required. |
CMCC-6-FLOW_CONTROL_OTHER |
6-Information |
Flow control error seen, Cause [chars] |
Flow control error is detected in the FPGA |
iosxe-chassismgr |
Appropriate action is taken in software to correct this error. If the problem persists, the MIP100 hardware may need to be replaced. |
CMCC-6-FRU_HWPRG_UPG_ADM1266_CFG_SUCCESS |
6-Information |
Hardware programmable ADM1266 Configurations on [chars] in slot [chars] were successfully programmed. |
The hw-programmable ADM1266 configuration was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_HWPRG_UPG_LMK03328_CFG_RESET |
6-Information |
Hardware programmable LMK03328 Configurations on [chars] in slot [chars] were successfully partially programmed, please reload it to continue programming. |
The hw-programmable LMK03328 configuration was partially upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_HWPRG_UPG_LMK03328_CFG_SUCCESS |
6-Information |
Hardware programmable LMK03328 Configurations on [chars] in slot [chars] were successfully programmed. |
The hw-programmable LMK03328 configuration was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_HWPRG_UPG_PSOC_PREPARE |
6-Information |
Hardware programmable PSOCs on [chars] in slot [chars] were set in the golden mode. The card will reload to finish the upgrading |
The hw-programmable PSOCs were set in the golden mode for FPD |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_HWPRG_UPG_PSOC_START |
6-Information |
Hardware programmable PSOCs on [chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. It will take about 2 mins to finish. |
The hw-programmable PSOC is upgrading |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_HWPRG_UPG_PSOC_SUCCESS |
6-Information |
Hardware programmable PSOCs on [chars] in slot [chars] were successfully programmed. The card will reload to make new firmware work. |
The hw-programmable PSOC was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_HWPRG_UPG_TPS40422_CFG_RESET |
6-Information |
Hardware programmable TPS40422 Configurations on [chars] in slot [chars] were successfully partially programmed, please reload it to continue programming. |
The hw-programmable TPS40422 configuration was partially upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_HWPRG_UPG_TPS40422_CFG_SUCCESS |
6-Information |
Hardware programmable TPS40422 Configurations on [chars] in slot [chars] were successfully programmed. |
The hw-programmable TPS40422 configuration was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_IOFPGA_UPG_START |
6-Information |
Field programmable device on [chars] in slot [dec] is being upgraded. It will take about 2 mins to finish the upgrade. Please do not reload or power-cycle this card while upgrade is in progress. |
The field programmable device on the FRU is upgrading |
iosxe-chassismgr |
No action is required. This is informational message |
CMCC-6-FRU_LC_UPGRADE_REQD |
6-Information |
Found mismatch between the Line card FPGA versions bundled in Software and programmed in Hardware in slot [dec]. FPGA version bundled in SW: %x, present in HW: %x. To upgrade the FPGA to version bundled in SW, perform physical OIR of the line card or run the CLI: hw-module subslot <slot>/<SPA no.> oir power-cycle |
New FPGA is bundled in SW. FPGA upgrade is needed. |
iosxe-chassismgr |
To upgrade to latest FPGA, do physical OIR Line card or do Pseudo OIR of the line card using CLI: hw-module subslot <slot>/<SPA no.> oir power-cycle; To view the present FPGA versions in chassis, use the CLI: show firmware version all |
CMCC-6-FRU_UPGRADE_REQD |
6-Information |
Slot [dec] needs firmware upgrade. Firmware upgrade is traffic impacting. To perform firmware upgrade use any of the 3 options: Option 1: Perform physical removal and insertion of the line card. Option 2: Run the <CLI> 'hw-module subslot [dec]/0 oir power-cycle' </CLI>. Option 3: Perform manual upgrade using <CLI> 'upgrade hw-programmable all filename bootflash: all' </CLI>. Use <CLI>'show firmware version all'</CLI> to know the mismatch |
New version bundled in Software & Current Hardware running version is not latest. upgrade is needed. please follow the options provided |
iosxe-chassismgr |
To perform firmware upgrade use any of the 3 options: Option 1: Perform physical removal and insertion of the line card Option 2: Run the <CLI> 'hw-module subslot <slot>/0 oir power-cycle' </CLI> Option 3: Perform manual upgrade using <CLI> 'upgrade hw-programmable all filename bootflash: all' </CLI> Use <CLI>'show firmware version all'</CLI> to know the mismatch |
CMCC-6-FRU_VER_MISMATCH |
6-Information |
[chars]: Found mismatch between the versions bundled in Software and programmed in Hardware in slot [dec]. Version Present in HW: %x, Version present in SW Bundle: %x. |
New FW is bundled in SW. FW upgrade is needed. |
iosxe-chassismgr |
To perform firmware upgrade use any of the 3 options: Option 1: Perform physical removal and insertion of the line card Option 2: Run the <CLI> 'hw-module subslot <slot>/0 oir power-cycle' </CLI> Option 3: Perform manual upgrade using <CLI> 'upgrade hw-programmable all filename bootflash: all' </CLI> Use <CLI>'show firmware version all'</CLI> to know the mismatch |
CMCC-6-LC_FPGA_UPGRADE_NOT_REQUIRED |
6-Information |
FPGA version on linecard in switch [dec] slot [dec] is 0x%x |
Upgrade of FPGA on the linecard is not required. |
iosxe-chassismgr |
No action required. |
CMCC-6-LC_FPGA_UPGRADE_PWR_CYCLE_DONE |
6-Information |
Power cycled the linecard in switch [dec] slot [dec], after FPGA upgrade. |
Power cycled the linecard after FPGA upgrade. |
iosxe-chassismgr |
No action required. |
CMCC-6-LC_FPGA_UPGRADE_START |
6-Information |
Linecard fpga device in switch [dec] slot [dec] is being upgraded. It will take about 5 mins to complete the upgrade Linecard will power-cycled automatically during this process. Please do not reload or power-cycle the linecard when upgrade is in progress |
The fpga device on the linecard is upgrading |
iosxe-chassismgr |
No action required. |
CMCC-6-LC_FPGA_UPGRADE_SUCCESS |
6-Information |
Successfully upgraded the field programmable device on linecard in switch [dec] slot [dec]. The line card will be power cycled |
Upgrade field programmable device was successful on the given FRU. Linecard needs to be power-cycled or removed and re-inserted for upgrade to take effect. |
iosxe-chassismgr |
Line card needs to be power cycled or removed and re-inserted for the upgrade to take effect. |
CMCC-6-MGMT_SFP_INSERT |
6-Information |
transceiver module inserted in [chars] |
The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message. |
iosxe-chassismgr |
No action required. |
CMCC-6-MGMT_SFP_REMOVED |
6-Information |
Transceiver module removed from [chars] |
The online insertion and removal (OIR) facility detected the removal of a transceiver module from the interface specified in the error message. |
iosxe-chassismgr |
No action required. |
CMCC_LED-6-BEACON_LED_TURNED |
6-Information |
Slot [dec] Beacon LED turned [chars] |
Beacon LED turned ON/OFF. This is a notification message only.No action is required. |
iosxe-chassismgr |
This is a notification message only. No action is required. |
CMDMA-2-FPGA_DOWNLOAD_FAILED |
2-Critical |
Critical Error is detected while downloading the FPGA. After this card will reboot. |
Due to timing issue in DMA sometime FPGA download failure is seen |
iosxe-chassismgr |
Contact your Cisco technical support representative and provide the system report and crash file. |
CMDMA-6-FPGA_DOWNLOAD_INFO |
6-Information |
[chars] fpga DMA download [chars] |
This is informative message about the start/complete of the fpga DMA download |
iosxe-chassismgr |
No action required |
CMEM-3-SENSOR_INIT_FAILED |
3-Error |
Sensor ([chars]) initialization failed due to [chars]. |
This error indicates that environmental monitor software cannot initialize the sensor. The software will not register and monitor this sensor. This could occur when the IDPROM has a bad I2C address for this sensor. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
CMEM-4-OBFL_INIT_FAILED |
4-Warning |
OBFL initialization failed. |
This error indicates the OBFL dedicated filesystem is not mounted. OBFL diagnostic information will not be retained for customer troubleshooting. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
CMFC-0-CHASFS_PROPERTY_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly created. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMFC-0-CHASFS_PROPERTY_SET |
0-Emergency |
Failed to write chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property failed to write. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMFC-3-IDPROM_ACCESS |
3-Error |
Failed to access or process IDPROM '[chars]': [chars] |
Failed access or process an IDPROM. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMFP-0-CPLD_INITIALIZATION |
0-Emergency |
CPLD initialization has failed because [chars] |
The CPLD has failed to initialize. This could be due to a hardware or software driver defect. |
iosxe-chassismgr |
Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMFP-0-CPLD_IOCTL |
0-Emergency |
A CPLD driver I/O control has failed because [chars] |
A complex programmable logic device (CPLD) I/O driver control has failed. This error could be caused by a hardware or software driver defect. |
iosxe-chassismgr |
Examine the logs for CPLD driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information |
CMFP-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMFP-0-SPI4_MUX_HALT |
0-Emergency |
SPI4 MUX driver has detected a critical error [chars] |
A SPI4 MUX driver has failed or detected a critical hardware fault. This could be due to a hardware defect or driver defect. |
iosxe-chassismgr |
The only corrective action is to restart the FP |
CMFP-2-BAD_ID_HW |
2-Critical |
Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. |
Hardware in the specified location could not be identified as a genuine Cisco product |
cbr-platform-infra |
Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information. |
CMFP-2-FPGA_DOWNLOAD_FAILED |
2-Critical |
Critical Error is detected while downloading the FPGA. After this card will reboot. |
Due to timing issue in DMA sometime FPGA download failure is seen |
iosxe-chassismgr |
Contact your Cisco technical support representative and provide the system report and crash file. |
CMFP-2-UADP_EVENT |
2-Critical |
UADP EVENT (ASIC #[dec] [chars]) |
Unified Access Datapath ASIC Event |
iosxe-chassismgr |
Copy the message exactly as it appears on the console or in the system log. |
CMFP-3-CPLD_ECSR_ERROR |
3-Error |
An error has been detected on the ECSR bus |
An error has been detected on the ECSR bus. This may cause problems when accessing the fowarding processor |
iosxe-chassismgr |
Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors. |
CMFP-3-CPLD_ERP_ERROR |
3-Error |
An error has been detected on the ERP bus (cause [dec], phase [dec]) |
An error has been detected on the ERP bus. This may cause problems when accessing the fowarding processor |
iosxe-chassismgr |
Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors. |
CMFP-3-DDR_SINGLE_BIT_ERROR |
3-Error |
Single-bit DRAM ECC error: mme: [dec], sbe: [dec], address: 0x%08X, pid: [dec], name: [chars] |
A single-bit data corruption error has occurred in the forwarding processor (FP). |
iosxe-chassismgr |
These errors are self-correcting. If the problem persists, the FP hardware may need to be replaced. |
CMFP-3-DPP_MAC_LINK_ERROR |
3-Error |
DPP Mac Link failed [chars] |
One or more Mac links of DPP blocks failed. It could be because of a configuration error or hardware failure. |
iosxe-chassismgr |
Note the time of the error message and examine show hardware platform cman fp for detailed Report. |
CMFP-3-DPP_SERDES_SYNC_ERROR |
3-Error |
UADP fabric interface synchronisation [chars] |
One of more UADP fabric interface Serdes failed to sync, This could be due to a hardware defect. |
iosxe-chassismgr |
No action is required. |
CMFP-3-FPGA_IMG_ABSENT |
3-Error |
FPGA image is absent please contact Cisco technical support representative. |
Due to corruption is file system FPGA images are deleted. |
iosxe-chassismgr |
Contact your Cisco technical support representative and provide the tracelogs. |
CMFP-3-HB_TIMEOUT |
3-Error |
Periodic Heartbeat message from RP timed out. |
RP sends periodic heartbeat message to the ESP. The ESP did not receive this heartbeat message for last timeout period. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMFP-3-HT_FATAL_ERROR |
3-Error |
Failed to initialize the HyperTransport interface to the QFP |
The HyperTransport interface to the QFP failed to initialize completely. Software will restart the ESP to recover |
iosxe-chassismgr |
No action is required. |
CMFP-3-IDPROM_ACCESS |
3-Error |
Failed access or process an IDPROM because [chars] |
Access to an IDPROM failed due to a hardware or software defect, or incorrect IDPROM content. |
iosxe-chassismgr |
Examine the system logs for IDPROM and hardware errors. Copy the error message and related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered nformation. |
CMFP-3-IDPROM_SENSOR |
3-Error |
One or more sensor fields from the idprom failed to parse properly because [chars]. |
Output from the IDPROM sensors failed to parse, commonly caused by a checksum failure in the IDPROM. |
iosxe-chassismgr |
Examine the system logs for IDPROM and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
CMFP-3-MASTERSHIP_UPDATE |
3-Error |
An error ([chars]) has occurred while communicating the mastership role of this FP to the CPP. The FP is currently [chars] |
An error occurred while communicating a change in the state (Active, Active with a Standby, or Standby) of the forwarding processor (FP). The error can cause an inconsistency of expected states between FPs and could affect the replication of state between the FPs. |
iosxe-chassismgr |
Examine the system logs for errors. This error is usually temporary. |
CMFP-3-MASTERSHIP_WATCH |
3-Error |
Failed to initialize a watch on the active rp because [chars] |
The fp process has failed to setup a watch on the rp chasfs active-rp property. This error is likely caused by a problem with chasfs as a whole. |
iosxe-chassismgr |
Examine the logs to determine the exact reason for the failure. |
CMFP-3-N2_DDR_MBE |
3-Error |
The encryption processor has detected an uncorrectable multi-bit error in memory at address [dec] |
The encryption processor has detected an uncorrectable multi-bit in memory. This could be due to a hardware defect. |
iosxe-chassismgr |
Examine the logs for encryption processor hardware errors. |
CMFP-3-N2_FATAL_ERROR |
3-Error |
An error has been detected on encryption processor: type [chars] |
An error has been detected on encryption processor. |
iosxe-chassismgr |
Please check the chassis-manager logs for errors. |
CMFP-3-N2_INPUT_EXCEPT |
3-Error |
Crypto device overloaded. : type [chars]: 0x%08X |
An exception has been detected on encryption processor. |
iosxe-chassismgr |
Please lower crypto traffic rate. If the error still happens, encryption processor may stop processing. Need to reload ESP. |
CMFP-3-OCT_DRV_ERROR |
3-Error |
An error has been detected on encryption processor: [chars]: [chars] |
An error has been detected on encryption processor. |
iosxe-chassismgr |
Please check the chassis-manager logs for errors. |
CMFP-3-SBUS_FATAL_ERROR |
3-Error |
SBUS Controller not responding, bringing down [chars] |
Spico SBUS controller fails to repsond, This could be due to a hardware defect. Reset the CHIP |
iosxe-chassismgr |
No action is required. |
CMFP-3-SIF_SERDES_SYNC_ERROR |
3-Error |
Sif Serdes Sync Failed for Supervisor Failure Bitmap 0x%x |
One of more Supervisor ASIC Sif Serdes failed to sync, This could be due to a hardeware defect. |
iosxe-chassismgr |
Note the time of the error message and examine the show hardware platform cman fp for detailed Sif Serdes Report. |
CMFP-3-SPI4_MUX_STATUS |
3-Error |
SPI4 MUX driver has detected a informational error [chars] (occurred [dec] time(s)) |
A SPI4 MUX driver has failed or detected a information hardware fault. This could be due to a hardware defect or driver defect. |
iosxe-chassismgr |
Examine the logs for SPI4 MUX and hardware errors. |
CMFP-3-STANDBY_EOBC_LINK_ERROR |
3-Error |
Standby EOBC link error detected. |
Standby EOBC link error: either link state is down, or duplexity is not full, or speed is not 1Gbps. |
iosxe-chassismgr |
Examine the system hardware. Re-seat and securely screw in all FRUs. If the problem persists, please contact TAC support. |
CMFP-6-CRYPTO_MODULE |
6-Information |
Crypto Hardware Module is [chars] |
The log is to indicate whether Crypto Hardware Module IPSECHW is physically inserted in the chassis. |
iosxe-chassismgr |
No action is required. |
CMFP-6-DPP_SERDES_SYNC |
6-Information |
UADP fabric interface synchronisation [chars] |
The log is to indicate UADP fabric interface Serdes Sync succeeded during intialization of setup. |
iosxe-chassismgr |
No action is required. |
CMFP-6-N2_DRV_UPDATE |
6-Information |
Hardware crypto device disabled. [chars]: [chars] |
A crypto device driver has failed or detected a hardware fault. This could be due to a hardware defect or driver defect. |
iosxe-chassismgr |
The only corrective action is to restart the ESP |
CMLIB-2-IDPROM_INVALID |
2-Critical |
Invalid IDPROM assembly number 0x%04X. IDPROM update required |
IDPROM assembly number is not supported. |
iosxe-chassismgr |
IDPROM update is required |
CMLIB-3-THROUGHPUT_VALUE_APPLY_FAILED |
3-Error |
Throughput [chars] [chars] - failed to persist throughput of [chars] kbps. Error: [chars] |
Status indicating that a failure was observed during the writing of the throughput to persistent store. The error reason may shed light on the cause. The throughput value may have be used to configure the CPP hardware. |
iosxe-csl |
Examine the ios, chassis-manager and license-manager logs for possible clues. |
CMLIB-3-THROUGHPUT_VALUE_SETUP_FAILED |
3-Error |
Throughput [chars] [chars], throughput set to [chars] kbps. Error: [chars] |
Status indicating that a failure was observed during the setup of the throughput. The error reason may shed light on the cause. The set value is used to configure the CPP hardware. |
iosxe-csl |
Examine the ios, chassis-manager and license-manager logs for possible clues. |
CMLIB-4-FW_CHECK |
4-Warning |
slot [chars]: [chars] current firmware version is [chars], while the minimum required version is [chars]. Please upgrade it to minimum required version or higher. |
Firmware version in the specified location is lower than minimum required version |
iosxe-chassismgr |
Upgrade firmware version to latest. |
CMLIB-6-THROUGHPUT_VALUE |
6-Information |
Throughput [chars] [chars], throughput set to [chars] kbps |
Status indicating whether appropriate throughput is found or enabled and ensuring the value is used to configure the CPP hardware. |
iosxe-csl |
No user action is necessary. This is an informational message indicating that the throughput is configured. |
CMRP-0-CHASFS_LOCATION_TRANSLATE |
0-Emergency |
Failed to translate a location to a chasfs object name because [chars] |
The chassis manager failed to translate a location to a chasfs object name. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASFS_OBJECT_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] because [chars] |
The hardware failed to create a chassis filesystem object. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASFS_OBJECT_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] not present. |
A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASFS_OBJECT_WATCH |
0-Emergency |
Failed to watch chassis filesystem object [chars] because [chars] |
A chassis filesystem object was not watched because of the reason stated in the error message. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASFS_PROPERTY_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly created. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASFS_PROPERTY_GET |
0-Emergency |
Failed to read chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly read by the system. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASFS_PROPERTY_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] property [chars] not present. |
A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASFS_PROPERTY_SET |
0-Emergency |
Failed to write chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property failed to write. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASSIS_ID |
0-Emergency |
Error while updating chassis id, Error: [chars] |
The chassis Id is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASSIS_STATUS |
0-Emergency |
Failed to get chassis hardware status because [chars] |
The system failed to get the chassis hardware status. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CHASSIS_TYPE |
0-Emergency |
The chassis type [chars] is invalid. |
The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CLOCK_MASTERSHIP_SET |
0-Emergency |
Failed to set CLOCK mastership because [chars] |
The router failed to establish CLOCK mastership. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CPLD_INITIALIZATION |
0-Emergency |
The RP CPLD has failed initialization because [chars] |
The RP CPLD has failed to initialize. This could be due to a hardware or software driver defect. |
iosxe-chassismgr |
Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-CPLD_IOCTL |
0-Emergency |
A CPLD driver I/O control has failed because [chars] |
A CPLD driver I/O control has failed. This could be due to a hardware or software driver defect. |
iosxe-chassismgr |
Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-DDR_INITIALIZATION |
0-Emergency |
The RP DDR has failed initialization because [chars] |
The RP DDR has failed to initialize. This could be due to a hardware or software driver defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for DDR or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-EHSA_INITIALIZATION |
0-Emergency |
EHSA initialization has failed because [chars] |
EHSA has failed initialization. This could be due to a hardware or software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-EHSA_STATE_GET |
0-Emergency |
Failed to get EHSA state because [chars] |
Failed to get EHSA state. This could be due to a hardware or software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-EHSA_STATE_SET |
0-Emergency |
Failed to set EHSA state because [chars] |
Failed to set EHSA state. This could be due to a hardware or software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-FP_MASTERSHIP_SET |
0-Emergency |
Failed to set FP mastership because [chars] |
The router failed to establish ESP mastership. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-HT_INITIALIZATION |
0-Emergency |
The RP HyperTransport has failed initialization because [chars] |
The RP HyperTransport has failed initialization. This could be due to a hardware defect or HT driver defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-HT_IOCTL |
0-Emergency |
A RP HyperTransport driver I/O control has failed because [chars] |
A RP HyperTransport driver I/O has failed. This could be due to a hardware defect or HT driver defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-I2C_INITIALIZATION |
0-Emergency |
The RP I2C has failed initialization because [chars] |
The RP I2C has failed to initialize. These components provide low-level communications between the RP and the other cards in the system. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-INTERNALS_INITIALIZATION |
0-Emergency |
Failed to initialize internal state because [chars] |
The system failed to initilize the internal state for the reason mentioned in the error message. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-INTERNAL_HW_SHUTDOWN |
0-Emergency |
Internal unrecoverable error condition was detected. System is being reset. |
Internal unrecoverable error condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-0-INVALID_ARGUMENT |
0-Emergency |
A system function was given an invalid argument. |
A system function was given an invalid argument. This is due to a software defect. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-IPC_CONNECTION_INVALID |
0-Emergency |
An IPC connection has invalid state. |
An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-IPC_CONNECT_MASTER |
0-Emergency |
IPC connection to the active RP failed because [chars] |
IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-IPC_CONNECT_REMOTE_IOS |
0-Emergency |
IPC connection to a remote IOSd failed because [chars] |
IPC connection to a remote IOSd failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-IPC_INITIALIZATION |
0-Emergency |
IPC initialization failed because [chars] |
IPC initialization failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-MESSAGE_REGISTER |
0-Emergency |
Failed to register with active RP because [chars] |
The active RP failed to register. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-MESSAGE_RELAY |
0-Emergency |
Failed to relay a message because [chars] |
Failed to relay a message. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-MESSAGE_RESPONSE |
0-Emergency |
An invalid message response was received because [chars] |
An invalid message response was received. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-MQIPC_ADVANCE |
0-Emergency |
Failed to advance MQIPC queue because [chars] |
The MQIPC initialization failed. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-MQIPC_INITIALIZATION |
0-Emergency |
MQIPC initialization failed because [chars] |
MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-PEER_TABLE |
0-Emergency |
A peer table initialization or maintenance function failed because [chars] |
A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-PLATFORM_FAMILY_TYPE |
0-Emergency |
The platform family type [chars] is invalid. |
The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-PWR_FAULT_INITIALIZATION |
0-Emergency |
Power fault monitor initialization has failed because [chars] |
The power fault monitor has failed to initialize. |
iosxe-chassismgr |
Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-RESOLVE_FRU |
0-Emergency |
Failed to determine [chars] card because [chars] |
The router failed to determine a FRU state. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-RESOURSE |
0-Emergency |
Resource allocation failed in [chars] because [chars] |
The system is unable to allocate the requested resource. |
iosxe-chassismgr |
In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command. |
CMRP-0-ROLE_ADDRESS_UPDATE |
0-Emergency |
Failed to update role-based EOBC IP addresses because [chars]. |
The system failed to update a role-based EOBC IP address for the reason stated in the message line. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SERDES_INITIALIZATION |
0-Emergency |
The RP Serial Bridge ASIC has failed initialization because [chars] |
The RP Serial Bridge ASIC has failed to initialize. This could be due to a hardware defect, software driver defect or improper internal configuration. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for Serial Bridge ASIC and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SERDES_INTERRUPT_DISPATCH |
0-Emergency |
Serial Bridge interrupt dispatch error: [chars] |
Failed to dispatch an error interrupt from the Serial Bridge. This could be due to a software defect or inconsistent internal state. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for Serial Bridge errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SERDES_IOCTL |
0-Emergency |
A Serial Bridge driver I/O control has failed because [chars] |
A Serial Bridge driver I/O control has failed. This could be due to a hardware or software driver defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for Serial Bridge driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SERVICES_INITIALIZATION |
0-Emergency |
Failed to initialize general application services because [chars] |
The system failed to initialize application services. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SIGNAL_INITIALIZATION |
0-Emergency |
Failed to initialize signals because [chars] |
The system failed to initialize signals. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SLOTS_INITIALIZATION |
0-Emergency |
Failed to initialize chassis slot information because [chars] |
The system failed to initialize the chassis slot information. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SLOT_INVALID |
0-Emergency |
A card absolute slot number cannot be determined for this chassis type |
An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-SYSPAGE_WRITE_ERROR |
0-Emergency |
The syspage chassis-type write has failed because [chars] |
The syapge chassis-type write failed. This could be due to a software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-UIPEER_CREATE |
0-Emergency |
Failed to create user interface peer. |
The system failed to create a user interface peer. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-0-WANPLL_INITIALIZATION |
0-Emergency |
The RP WAN PLL has failed initialization because [chars] |
The RP WAN PLL has failed to initialize. This could be due to a hardware or software driver defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for WAN PLL or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-2-ACT2_UDI_DATA_INVALID |
2-Critical |
The act2 udi secure area format mismatch with unsecure area |
This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information. |
cbr-platform-infra |
Replace the current product with a Cisco authorised product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information. |
CMRP-2-BAD_ID_HW |
2-Critical |
Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. |
Hardware in the specified location could not be identified as a genuine Cisco product |
cbr-platform-infra |
Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information. |
CMRP-2-CRYPTOGRAPHIC_HW_MISMATCH |
2-Critical |
ESP[dec] does not support strong cryptography. Chassis will reload. |
IOS software featuring strong cryptography is invalid for use with any non-strong-cryptography Embedded Service Processor. The router node will reload if this combination is encountered. |
iosxe-chassismgr |
Install a non-strong-cryptography image of the RP IOS package or replace the indicated Embedded Service Processor with one that supports strong-cryptography |
CMRP-2-FRU_CPLD_INCOMPATIBLE |
2-Critical |
[chars] in slot [chars] has been held in reset as its CPLD firmware version is incompatible with [chars] |
This FRU requires a newer CPLD firmware to function properly in this chassis |
iosxe-chassismgr |
Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details. |
CMRP-2-FRU_FPGA_INCOMPATIBLE |
2-Critical |
[chars] in slot [chars] has been held in reset as its FPGA firmware version is incompatible with [chars] |
This FRU requires a newer FPGA firmware to function properly in this chassis |
iosxe-chassismgr |
Upgrade the FPGA firmware on this FRU using the <b> upgrade hw-programmable FPGA file <pkg_file> slot <fru_slot> </b> command. |
CMRP-2-FRU_HWPRG_UPG_FAILED |
2-Critical |
Failed to [chars] [chars] hardware programmable on [chars] in [chars]. |
Upgrade hw-programmable failed to upgrade the CPLD/FPGA firmware on the given FRU |
iosxe-chassismgr |
Reload the card and retry to program the hw-programmable. If the card fails to come up please contact TAC |
CMRP-2-FRU_HWPRG_UPG_PSOC_PREPARE |
2-Critical |
Hardware programmable PSOCs on [chars] in slot [chars] were set in the golden mode. Please power-cycle or OIR the card to finish the upgrading |
The hw-programmable PSOCs were set in the golden mode for FPD |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-2-FRU_HWPRG_UPG_PSOC_START |
2-Critical |
Hardware programmable PSOCs on [chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. It will take about 10 mins to finish. |
The hw-programmable PSOC is upgrading |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-2-FRU_HWPRG_UPG_PSOC_SUCCESS |
2-Critical |
Hardware programmable PSOCs on [chars] in slot [chars] were successfully programmed. Please power-cycle or OIR the card to make them work |
The hw-programmable PSOC was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-2-QUAD_SUP_DISABLE_SUPERVISOR |
2-Critical |
Exceeded the maximum failure attempts to enable Quad-Sup SVL. Forcing the supervisor in Switch [dec] slot [dec] into reset state. Keeping the supervisor in this state may cause system instability. Please pull out the supervisor and follow the quad sup migration procedure. |
ICS is booted with quad sup incompatible image |
iosxe-chassismgr |
Boot the supervisor in quad sup compatible image |
CMRP-2-QUAD_SUP_INCOMPATIBLE_SUPERVISOR_PWR_OFF |
2-Critical |
Exceeded the maximum failure attempts to enable Quad-Sup SVL. Forcing the supervisor in Switch [dec] slot [dec] into power off state. Keeping the supervisor in this state may cause system instability. Please pull out the supervisor, use 'hw-module switch <switch-num> subslot <slot> oir power-cycle' to power it on back and follow the quad sup migration procedure. |
ICS is booted with quad sup incompatible image |
iosxe-chassismgr |
Boot the supervisor in quad sup compatible image |
CMRP-2-QUAD_SUP_SW_MISMATCH |
2-Critical |
Supervisor in Switch [dec] Slot [dec] is booted with a quad-sup incompatible image. Continuing in this state could lead to undesirable behaviour. To recover from this state, boot the supervisor in Quad-SUP compatible image by following the migration Procedure.(Attempt : [dec] of 5) |
ICS is booted with quad sup incompatible image |
iosxe-chassismgr |
Boot the supervisor in quad sup compatible image |
CMRP-2-QUAD_SUP_UPLINK_SVL_SUPERVISOR_PWR_OFF |
2-Critical |
Supervisor in Switch [dec] Slot [dec] is booted when stackwise-virtual configured over supervisor ports which is unsupported. Keeping the supervisor in this state may cause system instability. Forcing the supervisor into power off state. Please pull out the supervisor, use 'hw-module switch <switch-num> subslot <slot> oir power-cycle' to power it on back and follow the quad sup migration procedure. |
ICS is booted with quad sup with stackwise-virtual over supervisor ports |
iosxe-chassismgr |
Boot the supervisor with stackwise-virtual configured over linecard ports |
CMRP-2-RP_CPLD_INCOMPATIBLE |
2-Critical |
All other cards in the system have been held in reset as the Active RP [chars] in slot [chars] has CPLD firmware version that is incompatible with [chars] |
Active RP requires a newer CPLD firmware to function properly in this chassis |
iosxe-chassismgr |
Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details. |
CMRP-2-RP_CPLD_INCOMPATIBLE_OTHER |
2-Critical |
[chars] in slot [chars] has been held in reset because [chars] |
Active RP requires a newer CPLD firmware to function properly in this chassis. |
iosxe-chassismgr |
Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details. |
CMRP-3-BITS_INITIALIZATION |
3-Error |
The RP BITS E1/T1 interface has failed initialization because [chars] |
The RP BITS E1/T1 interface has failed to initialize. This could be due to a hardware defect, a software driver defect or improper configuration. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for BITS driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative |
CMRP-3-CHASFS_OBJECT_DESTROY |
3-Error |
Failed to destroy chassis filesystem object [chars] because [chars] |
A chassis filesystem object that should have been destroyed was not destroyed. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-CHASFS_PROPERTY_DESTROY |
3-Error |
Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] |
A chassis filesystem property that should have been destroyed was not destroyed. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-CHASSIS_FRU_FAULT_IGNORED |
3-Error |
CMAN_IGNORE_FRU_FAULTS is set. [chars]: [chars] |
Debug variable will prevent a FRU from being restarted due to some faults. |
iosxe-chassismgr |
No action is necessary. |
CMRP-3-CHASSIS_FRU_FAULT_IGNORED_ISSET |
3-Error |
CMAN_IGNORE_FRU_FAULTS is set. Some FRU faults will be ignored and FRU may not restart due to a fault |
Debug variable will prevent a FRU from being restarted due to some faults. |
iosxe-chassismgr |
No action is necessary. |
CMRP-3-CHASSIS_MONITOR_FRU_BOOT_RETRIES_EXCEEDED |
3-Error |
[chars] has been held in reset because it has failed to successfully boot in [dec] tries |
The FRU has failed to successfully boot in the maximum allowable attempts and is held in reset. |
iosxe-chassismgr |
Remove the FRU from the chassis if the FRU continously fails to boot. |
CMRP-3-CHASSIS_MONITOR_FRU_BOOT_STATUS |
3-Error |
Reloading [chars] because the FRU boot status is unknown |
The time at which the FRU started booing is not available. This time is used to check the boot status of the FRU. |
iosxe-chassismgr |
Remove the FRU from the chassis if the FRU is continously reloaded. |
CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_EXCEEDED |
3-Error |
Reloading [chars] because it has failed to come online |
A FRU has failed to come online within the maximum boot time. |
iosxe-chassismgr |
Remove the FRU from the chassis if the FRU is continously reloaded. |
CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_IGNORED |
3-Error |
[chars] exceeded online time but will not be reset because fault ignore is configured |
The FRU failed to come online within the maximum online time. This message applies to all FRUs. A reload will not be performed because fault ignore is configured. |
iosxe-chassismgr |
No action is necessary. |
CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED |
3-Error |
Reloading [chars] because it has failed to become ready for packet processing |
The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover will be performed if another FP is available. |
iosxe-chassismgr |
Remove the FRU from the chassis if the FRU is continously reloaded. |
CMRP-3-CHASSIS_MONITOR_READY_TIME_IGNORED |
3-Error |
[chars] exceeded ready time but will not be reset because fault ignore is configured |
The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover and/or reload will not be performed because fault ignore is configured. |
iosxe-chassismgr |
No action is necessary. |
CMRP-3-DDR_SINGLE_BIT_ERROR |
3-Error |
Single-bit DRAM ECC error: mme: [dec], sbe: [dec], address: 0x%08X, pid: [dec], name: [chars] |
The RP DRAM has single-bit ECC errors. |
iosxe-chassismgr |
In most cases, the system self-corrects these single-bit ECC errors and no user action is necessary. If the problem persists, gather the console output with the error message along with the show tech-support command output and provide the gathered information to a Cisco technical support representative. |
CMRP-3-DUAL_IOS_STANDBY_BAY |
3-Error |
Standby bay cannot be launched due to failure in bringing down existing processes (Attempts: [dec]) |
During standby bay shutdown, some related processes still remain running for an unexpectedly prolonged period of time. Chassis-manager has timed-out waiting for all related processes to shutdown. As a result, it is unable to notify Process-manager to restart the bay |
iosxe-chassismgr |
Examine the logs for standby bay's Forwarding-manager (fman), Interface-manager (iman), Pluggable-Service-Daemon (psd) and IOS. Ascertain which of these processes is taking too long to shutdown and note the reason. Take corrective action based on the error noted in the log |
CMRP-3-EXT_ALARM_INTERRUPT |
3-Error |
Alarm [chars]:external alarm contact [dec] |
There is an external alarm on the line. |
iosxe-chassismgr |
If alarm is asserted, then clear at the source. |
CMRP-3-FAN_FAILURE_SYS_SHUTDOWN |
3-Error |
WARNING: More than one Fan Failure detected and shutdown SYS state. System shutdown now TRUE:%x. |
More than one fan failures are identified this causing overheating the system and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-3-FAN_INCOMPATIBLE |
3-Error |
The combination of Power Supply and Fan Tray is incompatible |
The combination of Fan tray and one of the power supply slots is not supported. This could cause unpredictable system behavior. |
iosxe-chassismgr |
This error indicates that the combination of one of the power supplies in P0 or P1 is not supported with the Fan Tray. In order to fix this issue, please review the installation guide, replace the fan tray or the power supply based on the requirement. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-FAN_INITIALIZATION |
3-Error |
The RP has failed to initialize Fan [dec] module controller because [chars] |
The RP failed to initialize the Fan. This could be due to a software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-FAN_REMOVE_IM_SHUT |
3-Error |
The Interface Modules (IM's) may shutdown in [dec] minutes [dec] seconds. |
Fan tray has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message. |
iosxe-chassismgr |
Reinsert a fan tray into the fan tray slot as soon as possible. |
CMRP-3-FAN_REMOVE_RSP2_SHUT |
3-Error |
The system will shut down when CYLON temp reaches 105C |
Fan tray has been removed and the router will shutdown when cylon temperature reaches critical temperature i.e. 105C to protect itself from overheating in the amount of time stated in the error message. |
iosxe-chassismgr |
Reinsert a fan tray into the fan tray slot as soon as possible. |
CMRP-3-FAN_REMOVE_RSP3_SHUT |
3-Error |
System received fan tray removal notification, Reinsert or service the faulty fan tray to avoid system shutdown due to high temperature. System will shutdown when the ARAD temp reaches Critical temperature i.e 105C. Based on current ARAD temperature [dec]C approximate time of shutdown is [dec] minutes [dec] seconds. |
Fan tray has been removed and the router will shutdown when the ARAD temp reaches Critical temperature i.e 105C to protect itself from overheating. |
asr903-system |
Reinsert a fan tray into the fan tray slot as soon as possible. |
CMRP-3-FAN_REMOVE_SHUT |
3-Error |
The system will shut down in [dec] minutes [dec] seconds |
Fan tray has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message. |
iosxe-chassismgr |
Reinsert a fan tray into the fan tray slot as soon as possible. |
CMRP-3-FAN_REMOVE_SYS_SHUTDOWN_PENDING |
3-Error |
System shutdown will occur in [dec] minutes. |
The FRU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-3-FP_DOWNREV |
3-Error |
[chars] has been held in reset because it is down-rev to the previous FP (0x%x -> 0x%x) in the chassis. Reboot the router to bring it up. |
The FP inserted is a lower version than the previous Active FP in the router. Downrev of FP is not supported. |
iosxe-chassismgr |
Reboot the router. |
CMRP-3-FP_LESSTHAN |
3-Error |
[chars] has been held in reset because it is down-rev to the active and cannot act as a standby. |
The part number read from the FP IDPROM is not compatible with part number of the active FP; therefore, it may not act as a standby. |
iosxe-chassismgr |
Remove the FP from the chassis. |
CMRP-3-FP_UNSUPP_UPREV |
3-Error |
[chars] has been held in reset because of an upsupported upgrade of FP (0x%x -> 0x%x) in the chassis. Reboot the router to bring it up. |
The FP inserted is a higher version than the previous Active FP in the router but this upgrade of FP is not supported. |
iosxe-chassismgr |
Reboot the router. |
CMRP-3-FRU_HWPRG_BAD_DEVICE |
3-Error |
Invalid HW programming device for [chars] in slot [chars]. |
The device is not supported in hardware programming. |
iosxe-chassismgr |
No action is required. This is an informational message |
CMRP-3-FRU_HWPRG_LOAD_KMODULE_FAIL |
3-Error |
Cannot load a kernel module on [chars] in slot [chars]. |
Cannot load a Kernel module when upgrade CPLD or FPGA. |
iosxe-chassismgr |
Reload the card and retry to program the hw-programmable. If you get the same error, please contact TAC |
CMRP-3-FRU_HWPRG_NO_FILE_ENTRY |
3-Error |
Cannot find file or directory on [chars] in slot [chars]. |
Cannot find a file or a directory when upgrade CPLD or FPGA. |
iosxe-chassismgr |
No action is required. This is an informational message |
CMRP-3-FRU_HWPRG_RESTART_ERROR |
3-Error |
Error [chars] when Chassis Manager restarts [chars] in slot [chars]. |
Restart procedure has an error after upgrade. |
iosxe-chassismgr |
Try hw-module command to reload the FRU. |
CMRP-3-FRU_HWPRG_UPG_PS_FAILED |
3-Error |
Power-Supply Module MCU [chars] in slot [chars] program failed |
The hw-programmable power-supply upgrade failed |
iosxe-chassismgr |
Please check Power-Supply model and PKG file. |
CMRP-3-FRU_HWPRG_UPG_SUCCESS |
3-Error |
Hardware programmable [chars] on [chars] in slot [chars] was successfully programmed. The card will now be power-cycled or reset. |
The hw-programmable CPLD/FPGA was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-3-FRU_HWPRG_UPG_UNSUPP |
3-Error |
Upgrade of hardware programmable [chars] on [chars] in slot [chars] is not supported. Card will now be powered down. |
upgrade of hw-programmable CPLD/FPGA not supported. |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-3-FRU_INCOMPATIBLE |
3-Error |
[chars] has been held in reset: [chars] is incompatible with [chars] |
The part number read from the FRU IDPROM is invalid for this chassis type. |
iosxe-chassismgr |
Remove the FRU from the chassis. |
CMRP-3-FRU_INVPARTNUM |
3-Error |
[chars] has been held in reset because the part number %08X is invalid. |
The FRU IDPROM contains an invalid part number. |
iosxe-chassismgr |
The FRU IDPROM should be repaired or the board replaced. |
CMRP-3-FRU_NOPARTNUM |
3-Error |
Cannot get part number from IDPROM for [chars]: [chars]. |
The FRU IDPROM cannot be read or does not contain a valid part number field. |
iosxe-chassismgr |
The FRU IDPROM should be repaired. |
CMRP-3-HWLIB_INITIALIZATION |
3-Error |
The hardware library has failed to initialize because [chars] |
This could be due to a hardware defect, software driver defect or improper internal configuration. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for CPLD hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-HWMOD_FAIL |
3-Error |
hw-module [chars] command for slot [chars] failed ([chars]) |
The last hw-module command that was entered failed to complete |
iosxe-chassismgr |
Retry the command. If the retry of the command fails, reload the router. If reloading the router fails to resolve the problem, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-HWPRG_UPG_UNSUPP_SLOT |
3-Error |
upgrade of hardware programmables on [chars] is not supported while in slot [chars]. Card will now be powered down. |
upgrade of hw-programmable CPLD/FPGA not supported in the given slot. Move the card to a different slot and perform the upgrade |
iosxe-chassismgr |
Move the card to a different slot and perform the upgrade |
CMRP-3-I2C_READ |
3-Error |
An I2C read has failed because [chars] |
An I2C read has failed. This could be due to a hardware or software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-I2C_WRITE |
3-Error |
An I2C write has failed because [chars] |
An I2C write has failed. This could be due to a hardware or software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-IDPROM_ACCESS |
3-Error |
Failed to access or process IDPROM '[chars]': [chars] |
Failed access or process an IDPROM. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-IDPROM_SENSOR |
3-Error |
One or more sensor fields from the idprom failed to parse properly because [chars]. |
One or more sensor fields from the IDPROM failed to parse properly. This problem is often the result of a checksum failure in the IDPROM. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-INCOMPATIBLE_FRU |
3-Error |
[chars] in slot [chars] is not compatible with [chars] and so it is disabled |
The Product ID read from the FRU IDPROM is invalid for this hardware configuration. |
iosxe-chassismgr |
Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations. |
CMRP-3-INCOMPATIBLE_FRU_SDWAN |
3-Error |
[chars] in slot [chars] is not supported in controller mode |
Product ID read from FRU IDPROM is not supported in sdwan controller mode. |
iosxe-chassismgr |
Remove the FRU from the chassis |
CMRP-3-INCOMPATIBLE_STANDBY_SUPERVISOR |
3-Error |
Standby supervisor is not compatible with the Active supervisor. Standby Supervisor will be disabled |
Supervisor found in Standby slot may not be fully compatible with the active supervisor and may cause issues. |
iosxe-chassismgr |
Use supervisors with the same specifications to enable High Availablitly features. |
CMRP-3-INTERNAL_HW_ERROR |
3-Error |
An nternal error condition was detected and resolved. |
An internal error condition was detected, and affected part of hardware was reset. If this error condition reoccurs, the hardware may need to be replaced. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-3-INVENTORY_INITIALIZATION |
3-Error |
[chars] inventory file could not be read. FRU may need a reload to initialize properly, [chars] |
The FRU inventory file could not be read. The file can possibly be corrupt. The FRU will possibly not initialize properly. The FRU should reset automatically. If it does not, it should be reloaded manually. If the error persists, the FRU will need to be replaced. |
iosxe-chassismgr |
Wait a few minutes. If FRU does not reset automatically, it should be manually reloaded. If error persists, the FRU needs to be replaced. |
CMRP-3-LICENSE_TIMEOUT |
3-Error |
Throughput license request timed out. Throughput level set to default |
Throughput license was never received from lman |
iosxe-chassismgr |
Examine logs for error messages |
CMRP-3-OOD_OPR |
3-Error |
An OOD operation has failed because [chars] |
An OOD opearion has failed. This could be due to a hardware or software defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for OOD errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-OPR_PENDING |
3-Error |
The slot [dec] is has pending operation, please try later. |
The previous operation on this board has not completed |
iosxe-chassismgr |
Try with the same command later |
CMRP-3-PEER_INVALID |
3-Error |
A peer table entry has invalid state. |
A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-PEM_REMOVE_SHUT |
3-Error |
The system will shut down in [dec] minutes |
A power supply has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message. |
iosxe-chassismgr |
Reinsert a power supply into the power supply slot as soon as possible. The second power supply is required because the fans in the power supply are essential in monitoring router temperature. |
CMRP-3-PFU_FAILURE |
3-Error |
Failed to handle power supply failure for [chars] in slot [dec], [chars] |
A power supply has failed and the system is unable to properly handle the failure. |
iosxe-chassismgr |
Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue. |
CMRP-3-PFU_FAN |
3-Error |
Failed to handle fan failure for [chars] in slot [dec], [chars] |
One or more fans have failed and the system is unable to properly handle the fan failure. |
iosxe-chassismgr |
Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue. |
CMRP-3-PFU_INCOMPATIBLE |
3-Error |
PFU Incompatible: [chars] |
Error message for any PFU compatibility errors. |
iosxe-chassismgr |
Remove incompatible PSUs. |
CMRP-3-PFU_INITIALIZATION |
3-Error |
The RP has failed to initialize a Power Supply/Fan module controller because [chars] |
The RP failed to initialize a Power Supply or Fan module controller. This could be due to a hardware defect or C2W access failure. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for C2W and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-PFU_MISSING |
3-Error |
The platform does not detect a power supply in slot [dec] |
There is no power supply in one of the power supply slots. |
iosxe-chassismgr |
Insert a power supply into the empty slot. The router requires two power supplies because the fans in the power supply are needed to cool the router. |
CMRP-3-PFU_OIR |
3-Error |
Failed to handle a [chars] oir event for PEM in slot [dec], [chars] |
A power supply was inserted or removed into or from a router and the software did not properly handle the event. |
iosxe-chassismgr |
Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue. |
CMRP-3-POWERBUDGET |
3-Error |
not enough power budget left for : [chars]:[dec] |
The system do not have enough power budget for the new card. |
cbr-platform-infra |
the message will be displayed when not enough power budget left for the new card inserted. |
CMRP-3-PSU_INCOMPATIBLE |
3-Error |
The combination of Power Supply in P0: [chars] and P1: [chars] is not supported in power [chars] mode |
An incompatible power supplies combination has been identified in P0 and P1 power supply slots. This could cause unpredictable behavior in power management in the router. |
iosxe-chassismgr |
This error indicates that the combination of the two power supplies in P0 and P1 is an unsupported combination. In order to fix this issue, please review the installation guide, plug out one of the power supplies based on the requirement. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-PWR_FAULT |
3-Error |
Shutting down [chars] because power fault on primary is [chars] and secondary is [chars] |
The FRU has been shutdown as a result of a power issue. |
iosxe-chassismgr |
Check to ensure the router is receiving power. Otherwise, note the time of the error message and examine the logs for power-related errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-RP_MASTERSHIP_SET |
3-Error |
Failed to set RP mastership [chars] because [chars] |
The router failed to establish RP mastership. |
iosxe-chassismgr |
Reload the router. |
CMRP-3-RP_MISMATCH |
3-Error |
[chars] has been held in reset because the part number differs from that of the active RP |
The part number read from the FRU IDPROM is not compatible with part number of the active RP; therefore, it may not act as a standby. |
iosxe-chassismgr |
Remove the FRU from the chassis. |
CMRP-3-RP_RESET |
3-Error |
RP is resetting : [chars] |
This RP is resetting due to the reason specified. |
iosxe-chassismgr |
No action is necessary. |
CMRP-3-RP_SB_RELOAD |
3-Error |
Reload of Standby RP failed: [chars] |
A request to reload the standby RP failed. |
iosxe-chassismgr |
Manually reload the standby RP. If that fails, configure SSO or RPR and then attempt the reload. If the problem persists, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, show redundancy state, and the output of show tech-support and provide the gathered information to a Cisco technical support representative |
CMRP-3-RP_SWITCH_SB_NOT_READY |
3-Error |
RP switchover: [chars] |
An RP switchover occurred when the standby RP was not ready. The standby RP reset. |
iosxe-chassismgr |
No user action is necessary. Allow the standby RP to reset. |
CMRP-3-SENSOR_INITIALIZATION |
3-Error |
Failed to initialize sensor monitoring because [chars]. |
Sensor monitoring failed to initialize. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-SENSOR_TYPE |
3-Error |
The sensor type is [dec] is invalid. |
A sensor type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-SERDES_ESI_INIT_FAIL |
3-Error |
Serial Bridge ESI link [chars] between [chars] and [chars] failed to config |
A Serial Bridge ESI link did not configure. This could be due to a software error. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-SERDES_ESI_LOCK_FAIL |
3-Error |
Serial Bridge ESI link [chars] between [chars] and [chars] failed to lock |
A Serial Bridge ESI link did not lock. This could be due to a hardware defect or a software configuration error. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-SERDES_NSTEP_SYNC_ERROR |
3-Error |
Link down in Slot=[dec], Link-Type=[dec], Link-Status=0x%x, Link=[dec] |
One or more Backplane Link didn't come up. This could be due to a hardware defect. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for repeated SYNC errors after repeated retries. If the logs, provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-3-SIP_MDR_FAIL |
3-Error |
The SIP[dec] failed Minimal Disruptive Restart because [chars] |
The SIP failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SIP by resetting the SIP hardware. |
iosxe-chassismgr |
Examine the system logs for errors. |
CMRP-3-SOFT_ERROR_RELOAD |
3-Error |
Uncorrected Soft error on [chars], reloading RP to recover |
Uncorrected Soft error on critical module, reloading the RP to recover |
asr903-system |
If this reoccures frequently, contact asr903-system |
CMRP-3-SOFT_ERROR_RELOAD_RECOMMENDED |
3-Error |
Uncorrected Soft error on [chars], reload is recommended to recover. |
Uncorrected Soft error on critical module, reload is recommended to recover |
asr903-system |
If this reoccures frequently, contact asr903-system |
CMRP-3-SOFT_ERROR_UPDATE |
3-Error |
Critical soft error on [chars] |
Update for each soft error on different components |
asr903-system |
If this reoccures frequently, contact asr903-system |
CMRP-3-SOFT_ERROR_WAIT |
3-Error |
Uncorrected Soft error on [chars], waiting for standby to switchover |
Uncorrected Soft error on critical module, waiting for standby to reach SSO to switchover |
asr903-system |
If this reoccures frequently, contact asr903-system |
CMRP-3-SYS_REBOOT |
3-Error |
System going down, reason: [chars] |
System reboot is called from software. Please check the reason and earlier syslog, traces |
iosxe-chassismgr |
Check the reason string and take appropriate action |
CMRP-3-THROUGHPUT_LICENSE_APPLY_FAILED |
3-Error |
Throughput license look-up failed due to '[chars]' |
This message is to notify the user that a license look-up did not succeed because license manager process could not be contacted. This is a rare case but is due to either a crashed license daemon(licensed) or it encountered an internal error. |
iosxe-chassismgr |
No user action is necessary. However, it is possible that a re-boot of the box may correct this behavior. |
CMRP-3-UDI_AUTH |
3-Error |
Quack Unique Device Identifier authentication failed |
This chassis seems to be compromised or tampered with. UDI burned on to the Quack chip and the one read from chassis EEPROM do not match. It can also be a case of either EEPROM or Quack device failure. More details about which specific field failed to match are logged in license daemon log file (licensed_R0.log). |
iosxe-chassismgr |
User immediately needs to contact Cisco support. This device appears to be tampered with or is a counterfeit device or had a system failure. |
CMRP-3-UNSUPPORTED_FRU |
3-Error |
[chars] in slot [chars] is not supported with [chars] and so it is disabled |
The Product ID read from the FRU IDPROM is not supported in this router. This is due to either Hardware or Software compatibility limitation indicated in the console log |
iosxe-chassismgr |
Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations. |
CMRP-3-UNSUPPORTED_PEM |
3-Error |
[chars] in slot [chars] is not supported with [chars] and it needs to be replaced immediately |
The Product ID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate replacement is required |
iosxe-chassismgr |
Remove the PEM from the chassis and replace it with a supported PEM. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations. |
CMRP-3-WANPLL_SETUP |
3-Error |
Failed to setup the [chars] of the RP WAN PLL because [chars] |
Failed to setup the RP WAN PLL appropriately. This could be due to a hardware defect of the device. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for WAN PLL related hardware errors. Check if the issue is transient or repeatable. If the problem is not recoverable collect the output of the error message and the chassis- manager and IOS logs. Provide the gathered information to a Cisco technical support representative. |
CMRP-4-ACTIVE_SLOTBAY_BIAS |
4-Warning |
The configured active slot/bay bias [dec] is invalid. |
The configured active slot/bay bias is not 0 or 1. The default value of 0 is used. |
iosxe-chassismgr |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-4-CPP_WARN |
4-Warning |
Active cable linecard in slot [dec] has been physically removed. |
Plug out one LC with heavy traffic, it may cause cpp queue pending drain and modem offline. |
cbr-platform-infra |
No action is required. |
CMRP-4-FAN_TRAY_OVER_CURRENT |
4-Warning |
A Fan Tray over-current has been detected. System will be reset. |
Internal error (Fan Tray over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-4-INTRUSION_ALERT |
4-Warning |
The system cover has been [chars] !! |
These tamper alert message indicate the event of intrusion. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
CMRP-4-MOTHERBOARD_OVER_CURRENT |
4-Warning |
Motherboard over-current has been detected. System will be reset. |
Internal error (Motherboard over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-4-NGWICS_OVER_CURRENT |
4-Warning |
A NIM over-current condition has been detected. System will be reset. |
Internal error (NIM over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-4-SERDES_ESI_CARD_RESEAT |
4-Warning |
Serial Bridge ESI link [chars] between [chars] and [chars] isn't locked; Card should be reseated |
A Serial Bridge ESI link did not lock during first 10 reties due to improper seating. |
iosxe-chassismgr |
Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-4-SYSTEM_OVER_CURRENT |
4-Warning |
Overall system over-current has been detected. System will be reset. |
Internal error (system over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-4-TAMPER_DETECTION_EVENT_MSG |
4-Warning |
System cover was opened [dec] times and closed [dec] times during power [chars] since last known event index [dec] at 20%02x/%02x/%02x %02x:%02x:%02x |
These tamper warning indicate the event of intrusion. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
CMRP-4-TAMPER_DETECTION_NO_LAST_KNOWN_EVENT |
4-Warning |
System cover was opened [dec] times and closed [dec] times during power [chars]. There is no last known/marked event. |
These tamper warning indicate the event of intrusion. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
CMRP-5-CHASSIS_MONITOR_BOOT_TIME_PRINT |
5-Notice |
Card [chars] took [dec] secs to boot |
This is an informational message about boot time of all cards. |
iosxe-chassismgr |
Action is not necessary. |
CMRP-5-FRU_CPLD_MISMATCH |
5-Notice |
CPLD ver [chars] in slot [chars] does not match Active CPLD ver [chars] |
This FRU requires a matching CPLD firmware to function properly in this chassis |
iosxe-chassismgr |
Upgrade the CPLD firmware to have matching versions. |
CMRP-5-HA_NOTICE |
5-Notice |
HA message: [chars] |
HA Error Occured. This could be due to a software defect, please follow action |
iosxe-chassismgr |
Note the time of the error message and examine the logs for HA and hardware errors. Try re-inserting Standby SUP properly and see if problem gets corrected, If the problem is not correctable or the logs are not helpful, collect the the output of the error message,the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-5-NEBS_ACCESS_PID_FAIL |
5-Notice |
Failed to acess NGIO PID list for [chars] on slot/bay [dec]/[dec] in NEBS mode. |
Unable to acess NGIO PID list for slot %d bay %d in NEBS mode |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-5-PEM_OUTPUT_DETECT |
5-Notice |
Output of PEM [dec] is [dec] V |
Value of Output of PEM. |
cbr-platform-infra |
If PEM Output is 0, check Power Cable. |
CMRP-5-PRERELEASE_HARDWARE |
5-Notice |
[chars] is pre-release hardware |
The board does have an official production part number. |
iosxe-chassismgr |
Immediately contact Cisco for a replacement board. |
CMRP-5-SUDI_KEY_READ_INIT_FAILED |
5-Notice |
SUDI(SHA2) key read failed during Initializtion. |
SHA key read failed during Initializtion. |
iosxe-chassismgr |
Check SUDI Trustpoint creation. Please collect output of show tech-support and provide the gathered information to a Cisco technical support representative. |
CMRP-5-UNSUPPORTED_MODULE |
5-Notice |
Unsupported Module inserted. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. |
Hardware in the specified location could not be identified as a genuine Cisco product |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-5-UNSUPPORTED_MODULE_IN_NEBS |
5-Notice |
The module [chars] on slot/subslot [dec]/[dec] is not supported in NEBS power mode. |
Hardware in the specified location should be removed in NEBS mode |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP-6-DUAL_IOS_REBOOT_REQUIRED |
6-Information |
Configuration must be saved and the chassis must be rebooted for IOS redundancy changes to take effect |
Chassis manager received notification that IOS software redundancy has been configured. For these changes to take effect, the system must be restarted. |
iosxe-chassismgr |
Reload the chassis. |
CMRP-6-DUAL_IOS_STARTING |
6-Information |
Software redundant IOS configured; starting standby in [dec] seconds. |
Chassis manager received notification that IOS software redundancy has been configured. The standby IOS will be started in the time specified. |
iosxe-chassismgr |
No action is necessary. |
CMRP-6-DUAL_IOS_STOPPING |
6-Information |
Bringing down standby IOS |
Chassis manager received notification to stop the standby IOS instance. This may be for a redundancy mode change. Depending on the reason, the standby may be subsequently restarted. |
iosxe-chassismgr |
No action is necessary. |
CMRP-6-FORCE_RESET_OTHER_RP |
6-Information |
The other SUP RP [dec] is still holding the midplane lock to block the suppervisor failover, force reset it to release the midplane lock. |
The Other Supvervisor is force reset due to hold the midplane lock for a long time during supervisor failover |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-6-FP_HA_SB_NOTREADY |
6-Information |
FP switchover: F[dec] [chars] |
The standby ESP is not ready for a switchover. |
iosxe-chassismgr |
No user action is necessary. |
CMRP-6-FP_HA_STATUS |
6-Information |
F[dec] redundancy state is [chars] |
The ESP has transitioned into a new High Availability state. |
iosxe-chassismgr |
No user action is necessary. This is an informational message. |
CMRP-6-FP_SB_RELOAD_REQ |
6-Information |
Reloading Standby FP: [chars] |
A reload of Standby FP has been requested. |
iosxe-chassismgr |
No action is necessary. |
CMRP-6-FRU_FPGA_UPG_REQUIRED |
6-Information |
[chars] in slot [chars] has INCOMPATIBLE FPGA firmware version with [chars]. Upgrade the FPGA firmware |
This FRU requires a newer FPGA firmware to function properly in this chassis |
iosxe-chassismgr |
Upgrade the FPGA firmware on this FRU using the <b> upgrade hw-programmable FPGA file <pkg_file> slot <fru_slot> </b> command. |
CMRP-6-FRU_HWPRG_CPLD_POSTUPG_SUCCESS |
6-Information |
Hardware CPLD postupgrade on CLC[dec] was successfully programmed.The LC is reloading to make it take effect. |
The hw-programmable CPLD postupgrade was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-6-FRU_HWPRG_UPG_ADM1266_FM_START |
6-Information |
Hardware programmable ADM1266s on [chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. It will take about 10 mins to finish. |
The hw-programmable ADM1266 Firmware is upgrading |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-6-FRU_HWPRG_UPG_ADM1266_FM_SUCCESS |
6-Information |
Hardware programmable ADM1266s on [chars] in slot [chars] were successfully programmed. The card is reloading to make them work |
The hw-programmable ADM1266 fimware was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-6-FRU_HWPRG_UPG_PSOC_DONE |
6-Information |
Hardware programmable PSOCs on [chars] in slot [chars] were upgraded successfully |
The hw-programmable PSOC was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-6-FRU_HWPRG_UPG_PS_SUCCESS |
6-Information |
Power-Supply Module MCUs in slot [chars] were successfully programmed. |
The hw-programmable power-supply was upgraded succesfully |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-6-FRU_HWPRG_UPG_START |
6-Information |
Hardware programmable [chars] on [chars] in slot [chars] is upgrading. please don't reload or power-cycle this card. It will take about 5 mins to finish. |
The hw-programmable was upgrading |
iosxe-chassismgr |
No action is required. This is informational message |
CMRP-6-HT_CLOSURE_MODE |
6-Information |
The HTPI driver failed to set it's closure mode properly |
This is not a critical error, but it will result in possible traffic interruption during certain software failure cases or ISSU operations. |
iosxe-chassismgr |
Note the error message and contact a Cisco technical support representative. |
CMRP-6-HT_STATUS |
6-Information |
R[dec] hypertransport configured for F[dec] active |
The RP HyperTransport driver was properly configured for a newly active FP. |
iosxe-chassismgr |
No user action is necessary. This is as informational message indicating normal system operation. |
CMRP-6-IGNORE_PFU_OIR |
6-Information |
Simulating FAN OIR due to FAN Speed profile change |
FAN tray OIR is simulated throught software to select new FAN SPEED profile. this message is to let know the user that this is a simulated FAN oir and not physical FAN oir. User needs to ignore next occurrence messages/alarms associated with FAN tray removal/insertion actions. such as FAN tray missing, PEM/FAN removed/inserted and system shutdown will happen messages |
asr903-system |
ignore FAN tray or PEM/FM removal/insertion messages and system shutdown message |
CMRP-6-MGMT_SFP_INSERT |
6-Information |
transceiver module inserted in [chars] |
The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message. |
iosxe-chassismgr |
No action required. |
CMRP-6-MGMT_SFP_REMOVED |
6-Information |
Transceiver module removed from [chars] |
The online insertion and removal (OIR) facility detected the removal of a transceiver module from the interface specified in the error message. |
iosxe-chassismgr |
No action required. |
CMRP-6-MODULE_INSERTED_CFG_MISMATCH |
6-Information |
The module inserted in Switch:[dec] Slot:[dec] doesn't support the configured Stackwise Virtual link/Dual Active Detection Link Speed. Line card is Power denied. Please replace the Line card with the configured SVL/DAD link speed or remove the config and reload the system |
The Line Card and SVL/DAD CONFIG in the slot mismatch. |
iosxe-chassismgr |
Change the config and reload the system or remove the Line card. |
CMRP-6-REDT_FP_UNSUPPORTED_IN_INTER_CHASSIS_MODE |
6-Information |
[chars] redundant FP in slot [chars] is not supported in inter-chassis redundancy mode |
Because the system is configured in box-to-box or inter-chassis redundancy mode, the intra chassis redundancy mode is not supported and redundant FP, if any, will be disabled. |
iosxe-chassismgr |
No user action is necessary. |
CMRP-6-REDT_RP_UNSUPPORTED_IN_INTER_CHASSIS_MODE |
6-Information |
[chars] redundant RP in slot [chars] is not supported in inter-chassis redundancy mode. Please remove it for inter-chassis redundancy to work properly on system reload. |
Because the system is configured in box-to-box or inter-chassis redundancy mode, the intra chassis redundancy mode is not supported and redundant RP, if any, will be disabled. |
iosxe-chassismgr |
No user action is necessary. |
CMRP-6-RFROLE |
6-Information |
RP switchover, [chars] |
On RP switchover chasfs rfrole property has been changed. |
iosxe-chassismgr |
No user action is necessary. |
CMRP-6-RP_SB_RELOAD_REQ |
6-Information |
Reloading Standby RP: [chars] |
A reload of Standby RP has been requested. |
iosxe-chassismgr |
No action is necessary. |
CMRP-6-RP_SWITCH_SB_SYNC |
6-Information |
RP switchover: [chars] |
The RP switch synchronization timer expired. |
iosxe-chassismgr |
No user action is necessary. |
CMRP-6-SINGLE_IOS_REBOOT_RECOMMENDED |
6-Information |
Configuration must be saved and the chassis should be rebooted for optimal single-IOS execution |
Chassis manager received notification that IOS software redundancy has been unconfigured. For optimal runtime resource allocation, the system must be restarted. |
iosxe-chassismgr |
Reload the chassis. |
CMRP-6-STBY_HARDDISK_UNAVAIL |
6-Information |
stby-harddisk is offline |
The stby-harddisk is not available. |
iosxe-chassismgr |
No user action is necessary. This is an informational message. |
CMRP-6-TEST_SPA_OIR_ONLINE_INSERT_DENIED |
6-Information |
SPA [dec]/[dec] oir insert is denied |
test command executed disallowing the spa to be inserted. |
iosxe-chassismgr |
Execute the test command allowing the insertion of the spa for normal operation |
CMRP-6-TEST_SPA_OIR_ONLINE_OPS |
6-Information |
SPA [dec]/[dec] oir online status is set to [chars] |
test command executed to either allow/deny the spa coming online. |
iosxe-chassismgr |
If the card does not come online, execute the test command to allow the spa to come online. |
CMRP-6-THROUGHPUT_LICENSE |
6-Information |
Throughput license [chars], throughput set to [chars] |
Status indicating whether throughput license is found and the corresponding througput the CPP hardware is configured to provide. |
iosxe-chassismgr |
No user action is necessary. This is an informational message indicating throughput configured. |
CMRP_ENVMON-3-PWR_FRU_HW_AUTO_SHUTDOWN |
3-Error |
WARNING: The card on slot [dec] hit abnormal voltage or current. it has been auto-shutdown by hardware for protection |
The FRU hit abnormal voltage or current and has been auto-shutdown in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TEMP_FRU_HW_AUTO_SHUTDOWN |
3-Error |
WARNING: The card on slot [dec] is overheating. it has been auto-shutdown by hardware for protection |
The FRU is overheating and has been auto-shutdown in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_NOW |
3-Error |
WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown now. |
The FRU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_PENDING |
3-Error |
WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes. |
The FRU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TEMP_PSU_SHUTDOWN_NOW |
3-Error |
WARNING: [chars] temperature sensor on [chars] is in a shutdown PSU state. PSU shutdown now. |
The PSU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_NOW |
3-Error |
WARNING: [chars] temperature sensor on [chars] is in a shutdown SYS state. System shutdown now. |
The FRU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_PENDING |
3-Error |
WARNING: [chars] temperature sensor on [chars] is in a shutdown SYS state. System shutdown will occur in [dec] minutes. |
The FRU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TEMP_WARN_CRITICAL |
3-Error |
WARNING: [chars] temperature sensor on [chars] is in a critical state reading [dec] |
The FRU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-3-TRANSCEIVER_TEMP_SYS_SHUTDOWN_NOW |
3-Error |
WARNING: transceiver temperature sensor is in a shutdown SYS state. System shutdown now %x. |
The Transceiver is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_ENVMON-6-TEMP_SYS_SHUTDOWN_DISABLED |
6-Information |
WARNING: System is in a thermal shutdown disabled state. System won't shut down now. |
Thermal shutdown disable is configured to bypass system shutdown. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-1-FAN_POLICY_ALERT |
1-Alert |
SYSTEM FAN POLICY Alert : [chars] |
System FAN policy check detect issues |
iosxe-chassismgr |
Monitor or Replace faulty fan modules may be needed. |
CMRP_PFU-1-PFU_FAN_FAILED |
1-Alert |
System detected fan tray removal or fan failure, reinsert or service the faulty fan tray to avoid system shutdown due to high temperature. |
Fan tray has been removed or one of the fan failed and the router will shutdown when the temp reaches Critical temperature to protect itself from overheating. |
iosxe-chassismgr |
Reinsert a fan tray into the fan tray slot as soon as possible. |
CMRP_PFU-1-PFU_NO_FAN |
1-Alert |
System detected no fan or fan tray available, either not present or in failure state. Reinsert or service the faulty fan or fan tray to avoid system shutdown. |
No working fan or fan tray detected in the system, could be removed or in failure state, switch will be shutdown when the temp reaches critical temperature to protect itself from overheating. |
iosxe-chassismgr |
Reinsert working fan or fan tray as soon as possible. |
CMRP_PFU-2-PSU_VOLATGE_MIX |
2-Critical |
Mix of 110V and 220V is not supported configuration, PSU in slot [chars] is in 110V and PSU in slot [chars] is in 220V. This can cause system reload, Connect the same voltage input to avoid system reload immediately. |
Some PSUs are connected to 110V and some are connected to 220V. This is not supported from hardware as it may cause system failure and system may go for reload. Input voltage can be checked using CLI show platform hardware chassis power-supply detail |
iosxe-chassismgr |
Connect all the power supplies to same voltage input source as soon as possible. |
CMRP_PFU-3-DCPOWERREDUNDANCY |
3-Error |
dc input [chars] failed for pem: [dec] |
The DC input failed for pem module. |
iosxe-chassismgr |
the message will be displayed when DC input failed. |
CMRP_PFU-3-FANASSY_REMOVED |
3-Error |
Fan Assembly is removed. Please insert to avoid system from heating. |
Fan Assembly has been removed from the system. It needs to be inserted back to prevent system from heating. If the system over heats, parts of the system will not function normally and system may shut itself down. |
iosxe-chassismgr |
Insert the fan assembly in the system to prevent system from over heating. |
CMRP_PFU-3-PEM_STATUS |
3-Error |
WARNING: The power supply module on slot [dec] hits [chars], |
The power supply module are not functioning properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PEM_VOLTAGENOTSUPPORTED |
3-Error |
WARNING: Input voltage of power supply module on PS[dec] is not supported. Please use the supported range of either [dec]-[dec] volts for [dec]W or [dec]-[dec] volts for [dec]W |
The input voltage of the power supply module is out of range |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_FANS_DEAD |
3-Error |
The fans in the [chars] in slot [dec] have all failed. |
The system is in danger of overheating because none of the fans in one of the PEMs are working properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_FANS_DEAD_SHUTDOWN |
3-Error |
Shutting down system now because the fans in slot [dec] have all failed. |
When the fans fail then system does not have sufficient cooling capacity. To prevent damage, the system will automatically shut down. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_FAN_DEAD |
3-Error |
WARNING: Fan [dec] in the [chars] in slot [dec] has failed. |
A fan is not functioning properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_FAN_ERR |
3-Error |
WARNING: Fan [dec] in slot [dec] has the error: [chars], Please replace it with a new fan. |
A fan is not functioning properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_IDPROM_CORRUPT |
3-Error |
The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component |
The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_IDPROM_READ_ERR |
3-Error |
Could not read the PEM/FM idprom in slot P[dec]. The system will run without environmental monitoring for this component |
The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_SHUTDOWN |
3-Error |
Shutting down system now because the PEM in slot [dec] was removed or not seated correctly. |
When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PFU_SLOT_VACANT |
3-Error |
The platform does not detect a power supply in slot [dec] |
There is no power supply in one of the power supply slots. |
iosxe-chassismgr |
Insert a power supply into the empty slot. |
CMRP_PFU-3-PWR_MGMT_ALARM |
3-Error |
WARNING: System does not have sufficient input power for minimum reliable operation requiring [dec] watts. The system needs [dec] watts of additional power. |
System power does not meet minimum requirements. Insert additional power supplies or provide current power supplies with a greater input voltage source if applicable. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PWR_MGMT_LC_SHUTDOWN |
3-Error |
WARNING: Linecard in slot [dec] with priority [dec] and a power requirement of [dec] watts has shutdown. |
A LC was shutdown due to a power loss. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PWR_MGMT_SINGLE_SUP_ERROR |
3-Error |
ERROR: Remote supervisor has been detected in slot [dec]. System is configured to SINGLE-SUP power mode. Remove remote supervisor IMMEDIATELY. |
User inserted a second supervisor in a single-sup power mode. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PWR_PROTECTION_ACTION |
3-Error |
Shutdown the card [chars] due to insufficient power budget. |
The total power is not enough, shutdown FRUs for power protection. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PWR_PROTECTION_MODE |
3-Error |
WARNING: Detected low input voltage ([dec]V) on the power supply in slot P[dec], the power budget may not be enough, some cards may be shutdown due to the power budget reduction. Please check the power input. |
Input voltage of power supply is too low. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-PWR_REDUN_ALARM_STATE |
3-Error |
WARNING: An active power supply has failed and the system has entered alarm state. The system is operating without power redundancy and has [dec] watts of power remaining |
An active power supplied failed while in redundant power mode. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-SHUTDOWN_FAILURE |
3-Error |
The system attempted to shut itself down, but failed because [chars] |
The system reached a condition where it should be shut down, but the shutdown call failed. The system should be manually rebooted. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-TEMP_FRU_SHUTDOWN |
3-Error |
[chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes. |
The FRU is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-3-TEMP_SYSTEM_SHUTDOWN |
3-Error |
[chars] temperature sensor is in a shutdown system state. System shutdown will occur in [dec] minutes. |
The system is overheating and will be shut down in order to protect the components. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-4-PFU_FANTRAY_WARN |
4-Warning |
WARNING: Fantray in slot [chars] has the error: [chars]. |
A fantray is not functioning properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-4-PFU_FAN_ID_WARN |
4-Warning |
WARNING: [chars] of [chars] has an error: [chars] |
A fan is not functioning properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-4-PFU_FAN_INSUFFICIENT |
4-Warning |
WARNING: Insufficient number of fan modules installed. There are only [dec] fan modules, expecting [dec] |
Insufficient number of fan modules installed, should insert new fans as soon as possible to avoid system from over heating. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-4-PFU_FAN_TRAY_WARN |
4-Warning |
WARNING: Fan tray in slot [dec] has the error: [chars]. |
A fan tray is not functioning properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-4-PFU_FAN_WARN |
4-Warning |
WARNING: Fan [dec] in slot [dec] has the error: [chars]. |
A fan is not functioning properly. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-4-PWR_MGMT_CAPACITY_MIXED |
4-Warning |
System contains power supplies of mixed power capacity. Redundancy operating mode Full protected is not supported with this configuration. System will run in Normal protected state. |
HW does not support Full protected mode with mixed capacity power supplies. This is due to current sharing; specifically dealing with the case in which all active power supplies fail simultaneously. Full protected state is demoted to Normal protected state. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-4-PWR_MGMT_WARN |
4-Warning |
WARNING: Insufficient number of power supplies ([dec]) are installed for power redundancy mode [chars]. The system needs [dec] watts additional power. |
Insufficient number of power supplies are installed. Should insert new power supplies as soon as possible |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-5-DCPOWERINPUT |
5-Notice |
dc input [chars] recovered for pem: [dec] |
The DC input recovered for pem module. |
iosxe-chassismgr |
the message will be displayed when DC input recovered. |
CMRP_PFU-6-FANASSY_INSERTED |
6-Information |
Fan Assembly is inserted. |
Fan Assembly that was previously removed has been inserted in the system. Preventing the system from over heating is important. So fan assembly should not be removed for extended period of time during normal operation. |
iosxe-chassismgr |
No further action is necessary. |
CMRP_PFU-6-PEM_INSERTED |
6-Information |
Power Supply in slot [dec] not operational. |
A PEM seems to be inserted without the power cable connected. This message is a notice that the power supply is not operational, will not provide power to the system, and may not be completely detected by the software until the power cable is connected and the PEM is supplied with the power. |
iosxe-chassismgr |
Insert the power supply cable in the PEM and provide power. |
CMRP_PFU-6-PFU_BEACON_LED_ON_OFF |
6-Information |
[chars] beacon LED for PFU[dec] is TURNED [chars]. |
Power Supply or Fan-tray, Beacon LED turned ON/OFF. This is a notification message only.No action is required. |
iosxe-chassismgr |
This is a notification message only. No action is required. |
CMRP_PFU-6-PFU_FAN_DETECTED |
6-Information |
The required number of fan trays or fan modules are detected. |
After previous no fan or insufficient fan modules alarm, the required minimum number of fan trays or fan modules have been detected. |
iosxe-chassismgr |
No further action is required. |
CMRP_PFU-6-PFU_FAN_RECOVERED |
6-Information |
Fan in slot [dec] has been recovered from error conditions, Now it's working normally. |
Fans are just recovered from an error condition, |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PFU_FAN_RECOVERED_I2C |
6-Information |
Successfully restored I2C communication to PSoC [dec] on fan module in slot [dec]. |
Fans are just recovered from an I2C communcation. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PFU_INSERTED |
6-Information |
[chars] inserted. System shutdown aborted. |
When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.This message serves as notice that the module has been replaced within the required time |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PSU_VOLATGE_MIX_RECOVERED |
6-Information |
All PSUs are now connected to the same input voltage. System has recovered from mix of input voltages. PSU in slot [chars] is connected to [chars] |
Some PSUs were connected to 110V and some were connected to 220V. This was not supported from hardware as it may have caused system failure. The system is now in a stable state with all PSUs connected to the same input voltage |
iosxe-chassismgr |
All the power supplies should be connected to same input voltage source |
CMRP_PFU-6-PWR_MGMT_LC_RECOVERED |
6-Information |
Linecard in slot [dec] with priority [dec] has been recovered from shutdown |
A LC was recovered from a shutdown |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PWR_MGMT_NON_REDUNDANT |
6-Information |
Changing the power redundancy mode to non-redundant |
Changing the power redundancy mode to non-redundant |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PWR_MGMT_OK |
6-Information |
Sufficient number of power supplies ([dec]) are installed for power redundancy mode [chars] (excess power [dec] watts). |
Sufficient number of power supplies are installed. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PWR_MGMT_REDUNDANT |
6-Information |
Changing the power redundancy mode to redundant. |
Changing the power redundancy mode to redundant |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PWR_MGMT_SINGLE_SUP_NOTICE |
6-Information |
NOTICE([dec] of [dec]): System is now running in SINGLE-SUP power budget mode. Insertion of the remote supervisor is not supported in this power mode. System may shutdown if second supervisor is inserted. |
User needs to be notified that single-sup mode is enabled |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PWR_PROTECTION_RECOVERED |
6-Information |
The power supply in slot P[dec] has been recovered from the power protection mode. |
Power supply input are just recovered from an error condition, |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PWR_REDUN_RECOVERED |
6-Information |
System has recovered from the alarm state and has [dec] watts of power remaining |
User has recovered the system from the alarm state triggered by a power failure |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CMRP_PFU-6-PWR_UP_FRU |
6-Information |
Power up the card [chars] due to power budget change. |
The total power become enough, power FRUs. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
CONFIG_VALIDATOR_MESSAGE-5-EWLC_GEN_ERR |
5-Notice |
Error in [chars] |
EWLC wireless config db Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
CSVERIFY-3-CSVERIFY_FAIL |
3-Error |
Signature verification: [[chars]] |
During digital signature verification, an error has occured |
iosxe-binos-utils |
Check the diagnostic csverify trace file for more information on the underlying failure. |
CSVERIFY-6-CSVERIFY_SUCCESS |
6-Information |
Signature verification success for [chars] |
Signature verification was successful for the file mentioned. |
iosxe-binos-utils |
This is an informational message. No action is required. |
CXPD-3-MAX_LOCAL_EXIT_EXCEEDED |
3-Error |
Maximum local exit: [dec] exceeded, failed to initialize application: [chars] (interface: [chars]) |
This syslog is generated when the number of DIA exits exceed maximum supported value. SaaS app initialization will fail because of this reason |
cedge-cxp |
CXP has reached the maximum number of probes it can handle. Need to disable either some applications or the links in which CoR SaaS is enabled |
CXPD-5-APP_CHANGE |
5-Notice |
Application: [chars] exit changed from ([chars] via [chars]) local-color [chars] remote-color [chars] to ([chars] via [chars]) local-color [chars] remote-color [chars] from [dec]/[dec] to [dec]/[dec] (latency/loss) |
This log is generated whenever exit for a SaaS application changes from one TLOC to another TLOC |
cedge-cxp |
No action is required |
CXPD-5-SCORE_CHANGE |
5-Notice |
Application: [chars] ([chars] exit via [chars]), local-color: [chars], remote-color: [chars], score changed from [dec]/[dec] to [dec]/[dec] (latency/loss) |
This syslog is generated whenever the score (loss/latency combination) changes for SaaS application over given TLOC |
cedge-cxp |
No action is required |
DBAL-3-BIPC_MSG_ALLOC_FAIL |
3-Error |
BIPC msg size too big to allocate |
BIPC msg size beyond limit. |
polaris-infra |
Report this occurance to Cisco TAC |
DBAL-3-MQIPC_ADVANCEERR |
3-Error |
MQIPC advance error [[chars]] reader [[chars]] |
MQIPC fails to advance to the next msg in DBAL |
polaris-infra |
Report this occurance to Cisco TAC |
DBAL-3-MQIPC_EVENTLOSS |
3-Error |
MQIPC event lost reader [[chars]] |
MQIPC event notifying of non-empty queue not delivered to DBAL |
polaris-infra |
Report this occurance to Cisco TAC |
DBAL-3-MQIPC_PEEKERR |
3-Error |
MQIPC peek error [[chars]] reader [[chars]] err_msg [[chars]] |
MQIPC fails to peek and fetch a msg in DBAL |
polaris-infra |
Report this occurance to Cisco TAC |
DBAL-3-MQIPC_READER_INIT_BY_TIMER |
3-Error |
MQIPC reader [chars] initialized by timer not chasfs watcher. |
MQIPC reader initialized by timer not chasfs watcher. |
polaris-infra |
Report this occurance to Cisco TAC |
DBAL-4-LONG_EXEC_BATCH |
4-Warning |
Long exec [[dec]:[dec]] create:exec:now [[dec]:[dec]:[dec]] e:p [[dec]:[dec]] resumes [[dec]] peer [[chars]] |
DBAL batch execution took an extended period of time. This may or may not be a problem depending on the circumstances |
polaris-infra |
Collect log archive and show tech-support and report this occurance to Cisco TAC |
DBAL-6-DELAYED_BATCH |
6-Information |
Delayed batch [[dec]:[dec]] create:exec:notif:now [[dec]:[dec]:[dec]:[dec]] eproc [[dec]] e:p [[dec]:[dec]] peer [[chars]] |
DBAL batch with an extended lifetime. This can occur when large amounts of data and/or operations are being performed. |
polaris-infra |
If this is causing impact to any service, collect log archive and show tech-support and report this occurance to Cisco TAC. Otherwise, safe to ignore. |
DBGD-3-SYNTHETIC_TEST_PROBE_DNS_ERR |
3-Error |
DNS server is [chars], [chars] interface not valid in VRF: [chars] |
This error syslog is generated during synthetic test probes when FQDN cannot be resolved due to errors in DNS config |
cedge-srvcability |
No action is required |
DBGD-5-INTERFACE_AUTO_BW |
5-Notice |
Interface [chars] (vpn: [dec]) bandwidth determined by auto speedtest, upstream b/w: [dec] bps, downstream b/w: [dec] bps |
This notice syslog is generated whenever upstream or downstream bandwidth of an interface is auto adjusted |
cedge-srvcability |
No action is required |
DBGD-5-SYNTHETIC_TEST_PROBE_RESULT |
5-Notice |
Synthetic test probe result for app: [chars], url: [chars], src_intf: [chars], latency: [dec], loss: [dec]%%, score: [dec], count [dec] |
This notice syslog is generated once synthetic test probe finishes measuing loss and latency to given SaaS application |
cedge-srvcability |
No action is required |
DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_GET_XML_FILE_SIZE |
3-Error |
Unable to get file size of dynamic XML file dc_user_profiles.xml |
Unable to get file size of dynamic XML file dc_user_profiles.xml |
ewlc-client |
LOG_STD_ACTION |
DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_LOAD_XML |
3-Error |
Unable to load dynamic XML file dc_user_profiles.xml |
Unable to load dynamic XML file dc_user_profiles.xml |
ewlc-client |
LOG_STD_ACTION |
DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_OPEN_XML_FILE |
3-Error |
Unable to open dynamic XML file dc_user_profiles.xml |
Unable to open dynamic XML file dc_user_profiles.xml |
ewlc-client |
LOG_STD_ACTION |
DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_PARSE_XML |
3-Error |
Unable to parse dynamic XML file dc_user_profiles.xml |
Unable to parse dynamic XML file dc_user_profiles.xml |
ewlc-client |
LOG_STD_ACTION |
DMI-2-CDB_MAN_SUB_FAIL |
2-Critical |
Failed to register as mandatory subscriber [chars] ([dec]): [chars] |
A Confd error has occurred attempting to mark DMI as a mandatory subscriber |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-CHG_VRF_FAIL |
2-Critical |
The DMI application failed to set the correct virtual routing and forwarding network. |
The DMI application failed to set the correct virtual routing and forwarding network; thus, it cannot communicate with Confd. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-CLI_CHANNEL_CLOSED |
2-Critical |
CLI engine event channel closed unexpectedly ([dec]): [chars]. |
The CLI engine event channel to the network element closed unexpectedly. |
ddmi-infra |
DMI will reset. No action necessary. |
DMI-2-CONFD_CB_REG_DONE_FAIL |
2-Critical |
Failed to complete callback registration [chars] ([dec]): [chars]. |
A DMI application cannot complete callback registration with Confd. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-CONFD_CB_REG_FAIL |
2-Critical |
Failed to register callback with Confd [chars] ([dec]): [chars]. |
A DMI application cannot register a particular callback with Confd. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-CONFD_CONNECT_FAIL |
2-Critical |
Failed to connect to Confd via [chars] socket [chars] ([dec]): [chars]. |
A DMI application cannot connect to Confd via a particular socket type. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-CONFD_INIT_FAIL |
2-Critical |
Failed to initialize Confd [chars] ([dec]): [chars]. |
Confd did not initialize properly. |
ddmi-infra |
Back out any recent yang model updates. Stop and restart netconf-yang. |
DMI-2-CONFD_SUB_DONE_FAIL |
2-Critical |
Failed to complete subscription [chars] ([dec]): [chars]. |
A DMI application cannot complete subscriptions for changes to yang models. |
ddmi-infra |
Back out any recent model updates. Stop and restart netconf-yang. |
DMI-2-CONFD_SUB_FAIL |
2-Critical |
Failed to subscribe [chars] model [chars] ([dec]): [chars]. |
A DMI application cannot subscribe for changes to a particular yang model. |
ddmi-infra |
Back out any recent model updates. Stop and restart netconf-yang. |
DMI-2-CONTROL_SOCKET_ERROR |
2-Critical |
Confd control socket ready check returned an error [chars] ([dec]): [chars]. |
The control socket connection to Confd has returned an error. |
ddmi-infra |
DMI will reset. No action necessary. |
DMI-2-MAAPI_CONNECT_FAIL |
2-Critical |
Could not connect to Confd via DMI MAAPI socket [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to connect via MAAPI socket. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-MAAPI_WAIT_FAIL |
2-Critical |
Wait for Confd to initialize to phase two failed [chars] ([dec]): [chars]. |
Confd did not initialize properly. |
ddmi-infra |
Back out any recent yang model updates. Stop and restart netconf-yang. |
DMI-2-NESD_CREATE_FAIL |
2-Critical |
Failed to create nes daemon. |
Either an out-of-memory condition has been encountered, or the DMI CLI engine cannot connect to the network element. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-NESD_INIT_FAIL |
2-Critical |
Failed to initialize the network element synchronizer daemon |
The nesd daemon failed to initialize. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-NESD_PREHOOK_INIT_FAIL |
2-Critical |
Failed to initialize component-specific add-ons to the network element synchronizer daemon |
The nesd daemon failed to initialize its component-specific add-ons. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-NES_RESET_FAIL |
2-Critical |
Failed to reinitialize the DMI network element synchronizer daemon. |
The network element synchronizer daemon cannot reset in order to recover from a critical error. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-NETCONF_SSH_CRITICAL |
2-Critical |
NETCONF/SSH: [chars] |
A critical message from the NETCONF SSH daemon. |
ddmi-infra |
Not applicable |
DMI-2-NOTIFICATION_READ_FAIL |
2-Critical |
Failed to read notification [chars] ([dec]): [chars]. |
An attempt to read an event from the Confd notification socket failed. |
ddmi-infra |
DMI will reset. No action necessary. |
DMI-2-RUNNING_DATASTORE_INVALID |
2-Critical |
Running datastore is invalid due to configuration failure during commit phase. |
IOS configuration failed during commit phase of the transaction. As a result, running datastore is not in sync with IOS configuration. Configuration to IOS is not allowed until datastore becomes valid after full sync. |
INVALID |
Device will perform full-sync. CDB lock must be released by the controler to unblock full-sync. |
DMI-2-SD_INIT_FAIL |
2-Critical |
Failed to initialize the syncfd daemon |
The syncfd daemon failed to initialize. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-SD_RESET_FAIL |
2-Critical |
Failed to reinitialize the DMI syncfd daemon. |
The syncfd daemon cannot reset in order to recover from a critical error. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-VTY_SERVER_RESET_FAIL |
2-Critical |
Failed to reinitializie VTY server utility instance. |
Failed to reset VTY server utility in order to recover from critical error. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-2-WORKER_SOCKET_CLOSED |
2-Critical |
Confd worker closed unexpectedly [chars] ([dec]): [chars]. |
The worker socket connection to Confd has closed unexpectedly. |
ddmi-infra |
DMI will reset. No action necessary. |
DMI-2-WORKER_SOCKET_ERROR |
2-Critical |
Confd worker socket ready check returned an error [chars] ([dec]): [chars]. |
The worker socket connection to Confd has returned an error. |
ddmi-infra |
DMI will reset. No action necessary. |
DMI-3-AUTH_TIMED_OUT |
3-Error |
[chars] request from [chars]:[chars] for [chars] over [chars] timed out. |
A AAA request timed out. |
ddmi-infra |
Check connectivity to the configured AAA server. |
DMI-3-CDB_ABORT_FAIL |
3-Error |
Failed to abort transaction [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to abort a transaction. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-CDB_READ_FAIL |
3-Error |
Could not read the yang path '[chars]' from the DMI data store [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to read a specific model path from the DMI data store. |
ddmi-infra |
Download the model in question from the network element and verify the path exists. Update the model if needed. |
DMI-3-CDB_SET_NAMESPACE_FAIL |
3-Error |
Could not set the model namespace '[chars]' for accessing the DMI data store [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to set a specific model namespace for accessing the DMI data store. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-CDB_START_FAIL |
3-Error |
Could not start session to read configuration from the DMI data store [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to open the DMI data store. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-CDB_SYNC_FAIL |
3-Error |
Confd subscription socket sync failed [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to sync the subscription socket. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-CLI_ENGINE_CONNECT_FAIL |
3-Error |
Failed to connect to network element. |
DMI cannot connect to the network element in order to interact with its CLI parser. |
ddmi-infra |
Check the CLI engine protocol settings. |
DMI-3-CLI_ENGINE_CONNECT_LOSS |
3-Error |
Detected connection to the network element has been lost. Attempting to reconnect |
DMI has lost connection to the network element. |
ddmi-infra |
No action necessary. |
DMI-3-CLI_ENGINE_EVENT_FAIL |
3-Error |
Failed to retrieve CLI engine event ([dec]): [chars]. |
DMI cannot retrieve its CLI engine event in order to interact with the network element CLI parser. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-CLI_ENGINE_LOG_LVL_FAIL |
3-Error |
Failed to set CLI engine logging level ([dec]): [chars]. |
DMI cannot set its CLI engine logging level. |
ddmi-infra |
Stop and restart DMI. |
DMI-3-CLI_ENGINE_POLL_FAIL |
3-Error |
Failed to read CLI engine results - max polling attempts exceeded ([dec]). |
DMI cannot read its CLI engine results in order to interact with the network element CLI parser. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang |
DMI-3-CLI_ENGINE_READ_EVENT_FAIL |
3-Error |
Failed to read CLI engine event ([dec]): [chars]. |
DMI cannot read its CLI engine event in order to interact with the network element CLI parser. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang |
DMI-3-CLI_ENGINE_READ_FAIL |
3-Error |
Failed to read CLI engine results ([dec]): [chars]. |
DMI cannot read its CLI engine results in order to interact with the network element CLI parser. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-CLI_ENGINE_RECONNECT_FAIL |
3-Error |
Error reconnecting to the network element ([dec]): [chars] |
The CLI engine has lost its connection to the network element and attempted to reconnect with an error occurred. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-CLI_ENGINE_VTY_CREATE_FAIL |
3-Error |
The CLI engine failed to create a VTY instance ([dec]): [chars] |
The DMI CLI engine cannot create a VTY instance. |
ddmi-infra |
Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
DMI-3-CLI_ENGINE_VTY_OPEN_FAIL |
3-Error |
The CLI engine failed to open a VTY ([dec]): [chars] |
The DMI CLI engine cannot open a VTY. |
ddmi-infra |
Free up available VTY resources by closing unused VTYs. Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang |
DMI-3-CLI_ENGINE_VTY_TIMEOUT_FAIL |
3-Error |
The DMI CLI engine failed to disable the VTY timeout ([dec]): [chars] |
DMI disables the VTY timeout for the network element synchronizer's VTY connection to ensure its number cannot be silently claimed by other VTY sessions. |
ddmi-infra |
None required |
DMI-3-CLI_ENGINE_WRITE_FAIL |
3-Error |
Error writing the CLI: [chars] - [chars] |
A CLI engine error occurred while send a command line to the network element's CLI parser |
ddmi-infra |
Enter the command line in question manually via the network element's console or vty. If successful, stop and restart netconf-yang and retry. |
DMI-3-CLI_GEN_FAIL |
3-Error |
Failed to generate CLI change set [chars] ([dec]): [chars]. |
A Confd error has occurred when requesting the CLI change set for a transaction. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-DIFF_FAIL |
3-Error |
Error saving diff file: [chars]/[chars] - [chars] |
An operating system error occurred while performing a diff of two files and redirecting to a third file. |
ddmi-infra |
Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help. |
DMI-3-DIR_EXISTS |
3-Error |
Message diagnostics directory '[chars]' exists, but is not a directory. |
A existing file is conflicting with a directory name. |
ddmi-infra |
Remove or rename the offending file. |
DMI-3-EDIT_REJECTED |
3-Error |
The NETCONF running datastore edit request from application [chars], user [chars], via [chars] was recieved while a synchronization from the device running-configuration to the NETCONF running datastore was in progress. The edit request was rejected. Resend the edit request when the running-configuration synchronization has completed. |
A NETCONF running datastore edit request occurred simultaneously with a database synchronization operation. Thus, the request has been rejected. |
ddmi-infra |
Retry the NETCONF edit again later. |
DMI-3-INIT_SYNC_FAIL |
3-Error |
Initial DMI sync failed. |
DMI failed to synchronize the network element's running configuration with the DMI data store upon DMI startup. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-INTERNAL_ERROR |
3-Error |
Internal error - [chars] [dec]: [chars] |
An unexpected internal error has occurred. |
ddmi-infra |
Consult man page for impacted area to interpret the error code and string. |
DMI-3-INVALID_PRESERVE_PATH |
3-Error |
The NED preserve path specified |[chars]| does not exist. Please remove from the /native/cisco-ia/preserve-ned-path list. |
A non-existent XPath has been specified to be preserved during complete syncs. |
ddmi-infra |
Remove the offending path from the /native/cisco-ia/preserve-ned-path list. |
DMI-3-INVALID_REG_EXP |
3-Error |
The regular expression |[chars]| is invalid. Please remove from the '[chars]' model or via the CLI '[chars] [chars]' |
An invalid regular expression has been specified which will not compile. |
ddmi-infra |
Remove the offending regular expression from the specified model or via "no CLI". |
DMI-3-LOAD_SCHEMAS_FAIL |
3-Error |
Cannot load Confd schemas [chars] ([dec]): [chars]. |
DMI failed to load Confd schemas for yang model namespaces. |
ddmi-infra |
Back out any recent yang model updates. Stop and restart netconf-yang. |
DMI-3-MAAPI_APPLY_TRANS_FAIL |
3-Error |
Failed to apply a transaction via DMI MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to apply a transaction via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_DELETE_FAIL |
3-Error |
Failed to delete model path '[chars]' via DMI MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to delete a model path via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_FINISH_TRANS_FAIL |
3-Error |
Failed to finish a transaction via DMI MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to finish a transaction via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_KILL_SESSION_FAIL |
3-Error |
Could not kill DMI MAAPI user session [dec] - [chars] ([dec]): [chars]. |
A parser lock timeout has occurred, and DMI attempted to kill the session holding the global lock, but failed. |
ddmi-infra |
Kill the NETCONF user session holding the global lock manually. |
DMI-3-MAAPI_LOAD_FAIL |
3-Error |
Failed to load '[chars]' commands to model path '[chars]' via DMI MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to load commands to a model path via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_LOAD_FILE_FAIL |
3-Error |
Failed to load file '[chars]' via DMI MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to load commands from a file via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_LOCK_FAIL |
3-Error |
Failed to lock the DMI data store via DMI MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to lock the DMI data store via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_SAVE_FAIL |
3-Error |
Could not save model path '[chars]' to file via DMI MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to save a model path via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_START_TRANS_FAIL |
3-Error |
Could not start DMI MAAPI transaction [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to start a transaction via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_START_USER_FAIL |
3-Error |
Could not start DMI MAAPI user session [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to start a user session via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MAAPI_UNLOCK_FAIL |
3-Error |
Failed to unlock the NETCONF running data store via MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to unlock the DMI data store via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-MEM_UNAVAIL |
3-Error |
Memory was not available to perform the DMI action. |
Insufficient system memory is available to perform the DMI action. |
ddmi-infra |
Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
DMI-3-MODEL_RESTORE_FAIL |
3-Error |
DMI failed to restore the model '[chars]' from the network element's running configuration to the DMI data store ([dec]): [chars]. |
DMI failed to restore the model '%s' from the network element's running configuration to the DMI data store. |
ddmi-infra |
Check the netconf-yang section of the network element's running configuration. If populated with non-default values, stop and restart netconf-yang. If problem continues, restore the model's configuration in question via Netconf |
DMI-3-NETCONF_KILL_SESSION |
3-Error |
NETCONF session [dec] has held a parser configuration lock/NETCONF datastore global lock for the maximum time allowed and has been killed. |
A parser lock timeout has occurred, and DMI has killed the corresponding NETCONF session. |
ddmi-infra |
Establish a new NETCONF session. Adjust your application to hold global locks for a shorter interval -- seconds, not minutes |
DMI-3-NETCONF_SSH_ERROR |
3-Error |
NETCONF/SSH: [chars] |
An error message from the NETCONF SSH daemon. |
ddmi-infra |
Not applicable |
DMI-3-SAVE_FAIL |
3-Error |
Error saving file: [chars] - [chars] |
An operating system error occurred while opening or writing to a diagnostic file. |
ddmi-infra |
Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help. |
DMI-3-SYNC_CLI_FILTER_ADD_FAIL |
3-Error |
Failed to add CLI configuration monitor filter ([dec]): [chars]. |
DMI cannot add a CLI filter to monitor for external CLI changes. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_CLI_FILTER_CREAT_FAIL |
3-Error |
Failed to create CLI configuration monitor filter for pattern '[chars]' ([dec]): [chars]. |
DMI cannot create a CLI filter to monitor for external CLI changes. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_CLI_FILTER_MODE_FAIL |
3-Error |
Failed to set mode for CLI configuration monitor filter ([dec]): [chars]. |
DMI cannot set the mode for its CLI filter to monitor for external CLI changes. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_ERR |
3-Error |
An attempt to synchronize the running configuration to the NETCONF running data store has failed: [chars] |
An attempt to send the running-config to ConfD to repopulate its data store has failed. |
ddmi-infra |
Identify the offending CLI that makes the sync fail and delete it from the configuration. |
DMI-3-SYNC_FAIL |
3-Error |
An attempt to synchronize the running configuration to the NETCONF running data store has failed. |
An external change (outside of NETCONF or RESTCONF) has been detected. An attempt to send the running-config to Confd to repopulate its data store has failed. |
ddmi-infra |
Force a full sync via the 'sync-from' RPC. |
DMI-3-SYNC_LOCK_FAIL |
3-Error |
Failed to lock the NETCONF running data store via MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to lock the DMI data store via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-SYNC_MODULE_CHECK_ADD_FAIL |
3-Error |
Failed to add module up check ([dec]): [chars]. |
DMI cannot add a module up check to monitor for module up status. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_OIR_FILTER_ADD_FAIL |
3-Error |
Failed to add OIR monitor filter ([dec]): [chars]. |
DMI cannot add an OIR filter to monitor for OIR induced configuration changes. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_OIR_FILTER_CREAT_FAIL |
3-Error |
Failed to create OIR monitor filter ([dec]): [chars]. |
DMI cannot create an OIR filter to monitor for OIR induced configuration changes. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_SYSLOG_FILTER_ADD_FAIL |
3-Error |
Failed to add syslog monitor filter ([dec]): [chars]. |
DMI cannot add a syslog filter to monitor for external CLI changes. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_SYSLOG_FILTER_CREAT_FAIL |
3-Error |
Failed to create syslog monitor filter for pattern '[chars]' ([dec]): [chars]. |
DMI cannot create a syslog filter to monitor for external CLI changes. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. |
DMI-3-SYNC_UNLOCK_FAIL |
3-Error |
Failed to unlock the NETCONF running data store via MAAPI [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to unlock the DMI data store via MAAPI. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-VTY_NUM_FAIL |
3-Error |
DMI failed to retrieve its tty number from the network element |
DMI must keep track of its tty number it uses to send command lines to the network element's parser in order to avoid triggering its own sync events |
ddmi-infra |
Check that the 'show users line' command line is working |
DMI-3-VTY_SERVER_CREAT_FAIL |
3-Error |
Failed to create VTY server utility instance. |
Failed to create VTY server utility instance for DMI operational data use. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-3-VTY_SERVER_START_FAIL |
3-Error |
Failed to start VTY server utility instance. |
Failed to start VTY server utility instance for DMI operational data use. |
ddmi-infra |
Stop and restart netconf-yang. |
DMI-4-CANDIDATE_DATASTORE_DIRTY |
4-Warning |
Synchronization of the running configuration to the running datastore is deferred because the candidate datastore is dirty. Commit or discard the uncommitted configuration. |
Configuration is performed from the IOS terminal while the candidate datastore has uncommitted configuration. The system cannot perform sync until the configuration in the datastore is either committed or discarded. |
INVALID |
Commit or discard the configuration in the candidate datastore in order for the sync to proceed. |
DMI-4-CDB_MAINTENANCE_MODE |
4-Warning |
WARNING!!! - CDB MAINTENANCE MODE IS ACTIVE - [chars]. This mode is intended only for Cisco support - it must be disabled for normal NETCONF operation. |
A Cisco-support only NETCONF mode has been enabled as a recovery mechanism for an out-of-sync condition. |
ddmi-infra |
Disable this mode in order to return the device to normal NETCONF operation. |
DMI-4-CLI_ENGINE_ENABLE_FAIL |
4-Warning |
The DMI CLI engine failed to enable the network element's CLI parser (enter privileged mode) ([dec]): [chars] |
DMI cannot enter privileged mode when communicating with the network element's CLI parser. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. Check AAA settings for the Netconf/Restconf user account. |
DMI-4-CLI_ENGINE_RC_FAIL |
4-Warning |
The DMI CLI engine failed to get the overall return code from the command '[chars]' ([dec]): [chars] |
DMI cannot read CLI engine return code for the particular command. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang |
DMI-4-CLI_ENGINE_STATE_FAIL |
4-Warning |
Failed to query the CLI engine state ([dec]): [chars] |
DMI cannot read its CLI engine state. |
ddmi-infra |
Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang |
DMI-4-CLI_LOCK_FAIL |
4-Warning |
Failed to obtain exclusive access to the IOS parser: [chars]. |
An IOS parser error has occurred attempting to obtain a configuration parser lock. |
ddmi-infra |
Retry NETCONF operation. |
DMI-4-CLI_LOCK_OVERRIDE |
4-Warning |
Configuration lock cleared and obtained by NETCONF session. |
An IOS parser lock has been cleared to avoid conflict with NETCONF session. |
ddmi-infra |
Retry CLI operation after NETCONF session completes. |
DMI-4-CLI_ROLLBACK_WARN |
4-Warning |
CLI rollback warning: tid ([dec]): [chars]. |
A Confd induced CLI transaction was aborted and during the rollback CLIs, an error was returned |
ddmi-infra |
Confirm that the network element's running configuration is in the original state before the failed transaction |
DMI-4-CLI_UNLOCK_FAIL |
4-Warning |
Failed to unlock the IOS parser store: [chars]. |
An IOS parser error has occurred attempting to unlock the parser lock. |
ddmi-infra |
Retry NETCONF operation. |
DMI-4-CONFD_ROLLBACK_WARN |
4-Warning |
Error copying Confd rollback file ([dec]): [chars] |
An error occurred saving the Confd rollback information. |
ddmi-infra |
Please enable rollback in Confd. Check for free file system space. |
DMI-4-CONTROL_SOCKET_CLOSED |
4-Warning |
Confd control socket closed [chars] ([dec]): [chars]. |
The control socket connection to Confd has closed unexpectedly. |
ddmi-infra |
DMI will reset. No action necessary. |
DMI-4-DIAG_WARN |
4-Warning |
Unable to prepare file system for message diagnostics. |
An error occurred saving DMI message diagnostics. |
ddmi-infra |
Check for free file system space. |
DMI-4-NETCONF_TRACE_WARN |
4-Warning |
Error copying netconf.trace. |
An error occurred saving the Netconf trace information. |
ddmi-infra |
Please enable netconfTraceLog in Confd. Check for free file system space. |
DMI-4-RUNNING_DATASTORE_VALID |
4-Warning |
Running datastore is valid. |
Running datastore is valid after successful full-sync operation. |
INVALID |
Rollback configurations using rollback-files RPC to bring device into well known state. |
DMI-4-SUB_READ_FAIL |
4-Warning |
Confd subscription socket read failed [chars] ([dec]): [chars]. |
A Confd error has occurred attempting to read the subscription socket. |
ddmi-infra |
DMI will reset. No action necessary. |
DMI-5-ACTIVE |
5-Notice |
process is in steady state. |
process is in steady state. |
ddmi-infra |
Informational only. No action required. |
DMI-5-AUTHENTICATION_FAILED |
5-Notice |
Authentication failure from [chars]:[chars] for [chars] over [chars]. |
A user failed to authenticate. |
ddmi-infra |
No action is required. |
DMI-5-AUTHORIZATION_FAILED |
5-Notice |
User '[chars]' from [chars]:[chars] was not authorized for [chars] over [chars]. |
A user was not authorized for the requested service. |
ddmi-infra |
No action is required. |
DMI-5-AUTH_PASSED |
5-Notice |
User '[chars]' authenticated successfully from [chars]:[chars] for [chars] over [chars]. External groups: [chars] |
A user authenticated successfully for a service. |
ddmi-infra |
No action is required. |
DMI-5-CONFIG_I |
5-Notice |
Configured from [chars] by [chars], transaction-id [dec] |
A change to the running configuration was performed using NETCONF or RESTCONF. |
ddmi-infra |
Informational only. No action required. |
DMI-5-INITIALIZED |
5-Notice |
process has initialized. |
process has initialized. |
ddmi-infra |
Informational only. No action required. |
DMI-5-NACM_INIT |
5-Notice |
NACM configuration has been set to its initial configuration. |
The running-config under the /nacm tree has been set to its initial configuration. |
ddmi-infra |
No action is required. |
DMI-5-NACM_READRULES |
5-Notice |
NACM readrules for privilege level [dec] loaded successfully. |
NACM rules to permit readonly access loaded successfully. |
ddmi-infra |
No action is required. |
DMI-5-RESET |
5-Notice |
process internal state reset. |
process internal state reset. |
ddmi-infra |
Informational only. No action required. |
DMI-5-SYNC_COMPLETE |
5-Notice |
The running configuration has been synchronized to the NETCONF running data store. |
An external change (outside of NETCONF or RESTCONF) has been detected; thus, the running-config has been sent to Confd to repopulate its data store. |
ddmi-infra |
Informational only. No action required. |
DMI-5-SYNC_NEEDED |
5-Notice |
Configuration change requiring running configuration sync detected - '[chars]'. The running configuration will be synchronized to the NETCONF running data store. |
A configuration change that may trigger additional changes has been detected; thus, the running-config will be sent to Confd to repopulate its data store. |
ddmi-infra |
Informational only. No action required. |
DMI-5-SYNC_START |
5-Notice |
Synchronization of the running configuration to the NETCONF running data store has started. |
An external change (outside of NETCONF or RESTCONF) has been detected; thus, the running-config will be sent to Confd to repopulate its data store. |
ddmi-infra |
Informational only. No action required. |
DMI-6-NETCONF_SSH_INFO |
6-Information |
NETCONF/SSH: [chars] |
An informational message from the NETCONF SSH daemon. |
ddmi-infra |
Not applicable |
DMI-7-GEN_DEBUG |
7-Debug |
DMI DEBUG [chars] [chars] |
A debug message for syslog consumption. For troubleshooting wihtout btrace |
ddmi-infra |
Not applicable |
DOT1X-3-PROC_START_ERR |
3-Error |
Dot1x unable to start. |
The system failed to create the Dot1x process. |
polaris-smd |
Restart Dot1x process by entering <cmd>dot1x system-auth-control<cmd> command. If this message recurs, Reload the device. |
DOT1X-3-UNKN_ERR |
3-Error |
An unknown operational error occurred. |
The Dot1x process cannot operate due to an internal system error. |
polaris-smd |
Reload the device/process |
DOT1X-4-INFO_EAPOL_PING_RESPONSE |
4-Warning |
The interface [chars] has an 802.1x capable client with MAC [chars] |
An EAPOL ping was sent out on this port to determine 802.1x readiness of the client attached. An EAPOL response has been received by the device such as a PC. |
polaris-smd |
No action required. |
DOT1X-4-MEM_UNAVAIL |
4-Warning |
Memory was not available to perform the 802.1X action. AuditSessionID [chars] |
Insufficient system memory is available to perform the Dot1x Authentication. |
polaris-smd |
Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
DOT1X-5-FAIL |
5-Notice |
Authentication failed for client ([chars]) with reason ([chars]) on Interface [chars] AuditSessionID [chars] [chars] [chars] |
Dot1x authentication was unsuccessful. |
polaris-smd |
No action is required. |
DOT1X-5-RESULT_OVERRIDE |
5-Notice |
Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars] |
Authentication result was overridden |
polaris-smd |
No action is required. |
DOT1X-5-SUCCESS |
5-Notice |
Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars] Username [chars] |
Dot1x authentication was successful. |
polaris-smd |
No action is required. |
DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSS_EXT_2_DTLS_REPLAY_ATTACK |
6-Information |
User ID: [chars] - DTLS Replay Attack for connection closed |
DTLS Replay Attack for connection closed |
ewlc-ap |
LOG_STD_ACTION |
DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSS_EXT_2_DTLS_REPLAY_ATTACK_DETECTED |
6-Information |
User ID: [chars] - DTLS Replay Attack detected for Source IP [chars] and Dest IP [chars] |
DTLS Replay Attack detected for Source IP and Dest IP |
ewlc-ap |
LOG_STD_ACTION |
DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FPT_ITT_1_DTLS_SESSION_CLOSED |
6-Information |
User ID: [chars] - DTLS peer has closed the connection, cipher [chars] |
DTLS connection established with peer |
ewlc-ap |
LOG_STD_ACTION |
DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FPT_ITT_1_DTLS_SESSION_ESTABLISHED |
6-Information |
User ID: [chars] - DTLS connection established with peer, cipher [chars] |
DTLS connection established with peer |
ewlc-ap |
LOG_STD_ACTION |
DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FPT_ITT_1_DTLS_SESSION_HANDSHAKE_FAILURE |
6-Information |
User ID: [chars] - Failed to complete DTLS handshake with peer, reason: [chars] |
Failed to complete DTLS handshake with peer |
ewlc-ap |
LOG_STD_ACTION |
DTLS_TRACE_MSG-3-WLC_DTLS_ERR |
3-Error |
DTLS Error, [chars] |
General ewlc Error Message. |
ewlc-ap |
LOG_STD_ACTION |
DTLS_TRACE_MSG-3-X509_CERT_VERIFY_ERR |
3-Error |
Cert verify Error, [chars] |
General ewlc Error Message. |
ewlc-ap |
LOG_STD_ACTION |
EAP-2-PROCESS_ERR |
2-Critical |
EAP critical error [chars] |
This is critical condition where the router could not perform EAP process related operation. |
polaris-smd |
Review SM 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. Reload the device/process. |
EAP-3-BADPKT |
3-Error |
IP=[chars] HOST=[chars] |
This messages informs that the router received an invalid or malformed EAP packet from the specified host. |
polaris-smd |
Check specified host for EAP operation. |
EAP-6-FIPS_UNSUPPORTED_METHOD |
6-Information |
Method [chars] in eap profile [chars] is not allowed in FIPS mode |
This message informs that a method is not supported in FIPS mode. |
polaris-smd |
Use FIPS supported methods - PEAP, TLS and FAST |
EAP-6-MPPE_KEY |
6-Information |
IP=[chars] MPPE_RECV_KEY_LENGTH=[dec] |
This messages informs that the router received MPPE KEY for the specified host. |
polaris-smd |
No action is required. |
EMD-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This error could be due to a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the card. |
EMD-0-RESOLVE_FRU |
0-Emergency |
Failed to determine [chars] card because [chars] |
The system was unable to to determine a card state. This error could be due to a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the card. |
EMD-0-SERVICES_INITIALIZATION |
0-Emergency |
Failed to initialize general application services because [chars] |
The system failed to initialize the application services. This error could be due to a software defect or system resource limitation. |
iosxe-chassismgr |
Restart the card. |
EMD-3-IDPROM_ACCESS |
3-Error |
Failed access or process an IDPROM because [chars] |
The system failed to access an IDPROM or an IDPROM process failed. This error can occur from a hardware defect, software defect, or incorrect IDPROM content. |
iosxe-chassismgr |
Examine the logs for IDPROM and hardware errors. |
EMD-3-IDPROM_SENSOR |
3-Error |
One or more sensor fields from the idprom failed to parse properly because [chars]. |
One or more IDPROM sensor fields failed to parse properly. The most likely reason is a checksum failure in the IDPROM from incorrect IDPROM content. |
iosxe-chassismgr |
Examine the logs for IDPROM and hardware errors. |
EMD-3-PFU_INITIALIZATION |
3-Error |
The RP has failed to initialize a Power Supply/Fan module controller because [chars] |
The route processor (RP) failed to initialize a power supply or a fan module controller. This error could be caused by a hardware defect or a C2W access failure. |
iosxe-chassismgr |
Examine the logs for C2W and hardware errors. |
EMD-3-SENSOR_INITIALIZATION |
3-Error |
Failed to initialize sensor monitoring because [chars]. |
The system failed to initialize an IDPROM sensor monitoring process. This error can occur from a hardware defect, software defect, or incorrect IDPROM content. |
iosxe-chassismgr |
Examine the logs for IDPROM and hardware errors. |
EPM-4-ACL_CONFIG_ERROR |
4-Warning |
ACL NAME '[chars]' | ACE SEQUENCE [dec] | RESULT FAILURE | REASON [chars] |
This message indicates that adding an ACE to the specified ACL was ignored because of wrong configuration |
polaris-smd |
Change ACE configuration for the specifed ACL |
EPM-4-POLICY_APP_FAILURE |
4-Warning |
Policy Application Failed for Client [[chars]] MAC [[chars]] AuditSessionID [[chars]] for POLICY_TYPE [chars] POLICY_NAME [chars] REASON [chars] |
This message indicates that the displayed policy for the client could not be applied by the EPM |
polaris-smd |
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 |
6-Information |
POLICY [chars]| EVENT [chars] |
This message indicates a download request has been sent/downloaded successfully for the specified dACL |
polaris-smd |
No action required |
EPM-6-AUTH_ACL |
6-Information |
POLICY [chars]| EVENT [chars] |
his message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been applied or removed |
polaris-smd |
No action required |
EPM-6-IPEVENT |
6-Information |
IP [chars]| MAC [chars]| AuditSessionID [chars]| EVENT [chars] |
This message indicates the IP event Wait/Release/Assignment that has occured with respect to the specified host |
polaris-smd |
No action required |
EPM-6-POLICY_APP_SUCCESS |
6-Information |
Policy Application succeded for Client [[chars]] MAC [[chars]] AuditSession ID [[chars]] for POLICY_TYPE [[chars]] POLICY_NAME [[chars]] |
This message indicates that the displayed policy for the client has been applied successfully by the EPM |
polaris-smd |
No action required |
EPM-6-POLICY_REQ |
6-Information |
IP [chars]| MAC [chars]| AuditSessionID [chars]| EVENT [chars] |
This message indicates that a policy application/remove request has been received by the EPM |
polaris-smd |
No action required |
EPM_PLUGIN-5-ERR_HS20_URLFILTER_NOT_CONFIGURED |
5-Notice |
Attempt to enable url filtering for Hotspot 2.0 client [chars] without having an Hotspot 2.0 urlfilter configured |
An attempt was made to activate post-auth Hotspot 2.0 url filtering on the client, as requested by the Radius server but no urlfilter list name configured under the wireless hotspot anqp-server linked with the wireless policy profile. |
ewlc-spwifi |
Make sure a valid urlfilter list name is configured under the wireless hotspot anqp-server profile linked with the wireless policy profile |
EPM_PLUGIN-5-ERR_VLAN_NOT_FOUND |
5-Notice |
Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars] |
An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VTP database. |
polaris-smd |
Make sure the VLAN exists and is not shutdown or use another VLAN. |
EPM_PLUGIN-5-IGNORED_VLAN_VALIDATION |
5-Notice |
Vlan [chars] not defined on the controller, choosing Vlan [dec] |
Either the client is export-foreign or fallback-vlan CLI is configured |
polaris-smd |
Check if fallback-vlan is configured or if the client is export foreign. In such a case, no action needs to be taken. |
EPM_PLUGIN-5-PRINT_SEQUENCE |
5-Notice |
Creating ACE [dec] for ACL [chars] |
Every 10000th ACE and its ACL name printed to indicate the ACEs being created. |
polaris-smd |
Please check that the ACE count matches the configured ACE count. |
EPM_PLUGIN-5-VLAN_ASSIGN |
5-Notice |
Vlan assignment successful for client : [chars] with Vlan id : [dec] on Interface : [chars], AuditSessionID is [chars] |
The syslog indicates that the Vlan was assigned to the client |
polaris-smd |
No action is required. |
EPM_PLUGIN-6-STICKY_TIMER_START |
6-Information |
Sticky timer of [dec] seconds started for mac [chars] interface [chars] for template [chars] |
Log is used to notify the start of the sticky timer |
polaris-smd |
Sticky timer has begun. No action needs to be taken. |
EPOCH-6-EPOCH_REJECTED |
6-Information |
Peer [chars] has rejected epoch: [chars] |
This error occurs if epoch from shell-manager has been rejected by the peer. |
iosxe-shellmgr |
Check the epoch and peer state. |
EVUTIL-3-PERMISSION |
3-Error |
Operation not permitted for pid [dec] tid [dec] |
Eventlib has detected that a process has attempted to invoke an API that is listed as having a level of permission. |
iosxe-binos-utils |
Review the process logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
EVUTIL-3-PREREQUISITE_INIT |
3-Error |
A preferred library has failed to initialize: [chars] |
Eventlib has detected that a preferred library which provides infrastructure services has failed to fully initialize. |
iosxe-binos-utils |
Review the process logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
EVUTIL-6-PREREQUISITE |
6-Information |
Preferred library is absent |
Eventlib has detected that a preferred library is missing from the process. |
iosxe-binos-utils |
This is an informational message. |
EWLC_HA_LIB_MESSAGE-3-BULK_SYNC_STATE_ERR |
3-Error |
Error: Bulk sync status : [chars] |
Bulk sync status Error message. TERMINATED - Bulk-sync terminated |
ewlc-ha |
LOG_STD_NO_ACTION |
EWLC_HA_LIB_MESSAGE-3-WIRELESS_CONFIG_SYNC_FAIL |
3-Error |
Error: Wireless config sync not complete. Reloading the WLC! |
Switchover happens before wireless config sync is complete! |
ewlc-ha |
LOG_STD_ACTION |
EWLC_HA_LIB_MESSAGE-6-BULK_SYNC_STATE_INFO |
6-Information |
INFO: Bulk sync status : [chars] |
Bulk sync status INFO message. COLD - Bulk-sync ongoing. CONFIG_DONE - critical DB sync complete. WARM - Most of the DB's synced. HOT - Bulk-sync completed |
ewlc-ha |
LOG_STD_NO_ACTION |
EWLC_INFRA_MESSAGE-3-EWLC_EVENTHOG |
3-Error |
Event name: [chars] |
System has detected an excessive number of sub-events. Normal WLC functionality may be impacted. |
ewlc-app-infra |
LOG_STD_ACTION |
EWLC_INFRA_MESSAGE-3-EWLC_GEN_ERR |
3-Error |
Error in [chars] |
General ewlc Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
EWLC_INFRA_MESSAGE-4-EWLC_CAC_WARNING_MSG |
4-Warning |
CPU Utilization [chars] |
CPU utilisation for the process has breached the monitored level, some functionality may be impacted. If the condition persists, action may be needed. |
ewlc-ap |
If the condition is transient and does not occur frequently, these messages can be ignored otherwise an investigation is needed. LOG_STD_ACTION |
EWLC_INFRA_MESSAGE-6-EWLC_CAC_INFO |
6-Information |
CPU Utilization [chars] |
CPU Utilisation for the process has recovered below the monitored level |
ewlc-ap |
LOG_STD_NO_ACTION |
EWLC_UTILITY_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_1_WPA2_INPUT_TOO_LARGE |
3-Error |
User ID: [chars] - Failed to compute PRF mode ([dec]), size ([dec]) - input is too large |
Failed to compute PRF mode because of input is too large |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
EWLC_UTILITY_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_1_WPA2_INVALID_MODE |
3-Error |
User ID: [chars] - Failed to compute PRF mode ([dec]), size ([dec]) - invalid mode |
Failed to compute PRF mode because of invalid mode |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
EWLC_UTILITY_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_1_WPA2_OUTPUT_BUFFER_SMALL |
3-Error |
User ID: [chars] - Failed to compute PRF mode ([dec]), size ([dec]) - output buffer is too small |
Failed to compute PRF mode because of output buffer is too small |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
EZMAN_CLIENT-2-ECC_DOUBLE_BIT_ERROR |
2-Critical |
Double bit ECC errors observed. NP (CC card) is going to be reloaded to recover |
ECC error observed on the NP device.Reset the NP Device. |
asr1k-ether-lc |
This error is usually self-correcting. If the problem persists, the CC card/hardware may need to be replaced. |
EZMAN_CLIENT-3-ECC_SINGLE_BIT_ERROR |
3-Error |
Single bit ECC error |
ECC error observed on the NP device.Reset the NP Device. |
asr1k-ether-lc |
This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced. |
EZMAN_CLIENT-3-OBJECT_FAIL |
3-Error |
Failed to bringup [chars]. Failure reason is [chars] |
Bringup of object(NP/Bay/Interface) has failed in EZMAN. This can be due to any hardware/software failures and can be a serious error |
asr1k-ether-lc |
Restart the Linecard. |
EZMAN_CLIENT-3-VLAN_STATS_ERR |
3-Error |
NP Counter Read Failed for Vlan [dec] [dec] |
NP VLAN statistics error. |
asr1k-ether-lc |
Continous MSG of these Events, Trigger the reboot of the system |
EZMAN_CLIENT-5-EZ_CLIENT_VLAN_FULL |
5-Notice |
TCAM Full VLAN is not Able to add |
Rx Sync Failed for Interlaken, Status Timer Expired. So, Resetting the Rx Interlaken Core |
asr1k-ether-lc |
No user action is required. |
EZMAN_INFRA-3-PLATFORM_ID_ERR |
3-Error |
Invalid HW Part number([dec]) and HW Revision([dec]) |
HW Part number and revision read from the IDPROM are not showing up expected values which means the IDPROM is either corrupted or incorrectly programmed. |
asr1k-ether-lc |
Possible Hardware issue. Change the hardware. |
EZMAN_RM-2-FPGA_VERSION_CHECK_ERR |
2-Critical |
CASTOR FPGA[[dec]] version does not meet minimum required version. Read version : 0x%x, Min Req Version : 0x%x |
Castor FPGA version requirement not met. |
asr1k-ether-lc |
Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
EZMAN_RM-2-SEM_ERR |
2-Critical |
CASTOR FPGA[[dec]] - SEU event has occurred. Event code: [dec], SLR: 0x%x, Frame: 0x%x, Word, 0x%x, Bit: 0x%x |
A Single Event Upset (SEU) event has occurred. These events may occur at any point of time, but are considered to be rare. |
asr1k-ether-lc |
If the error is seen only once, there is no need for anything to be done. If these errors are appearing continuously/persistently, please copy over the logs as they appear in the console, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
EZMAN_RM-3-L2_BLOCK_EVENT |
3-Error |
L2 Block Event Node:[chars] (0x%08X - Tree [dec] Instance [dec]) |
NP of L2 is generating Events. |
asr1k-ether-lc |
Continous MSG of these Events, Trigger the reboot of the system |
EZMAN_RM-3-SERDES_AUTOTUNE_FAIL |
3-Error |
Serdes Autotune [chars] on lane [dec] |
NP5 Serdes RX is unable to autotune to the peer device's TX. This is a physical layer issue between NP5 and peer device. |
asr1k-ether-lc |
OIR the Host-card if possible. |
F to J
Facility-Severity-Mnemonic |
Severity-Meaning |
Message |
Message-Explanation |
Component |
Recommended-Action |
---|---|---|---|---|---|
FED-0-HWSTALL |
0-Emergency |
ASIC [dec] CORE [dec] Packet Buffer Complex Stalled. Switch will be reloaded\n |
The specified asic/core packet buffer complex stalled. This is a critical error. This switch will reload. If there is a redundant switch, switch over will happen |
polaris-platform_mgr |
No action is required |
FED-2-INIT_FAILED |
2-Critical |
Module [chars] failed initialization\n[chars] |
The specified module failed initialization. The switch will reload. |
polaris-platform_mgr |
No action is required |
FED3_EPC_ERRMSG-4-UNSUPPORTED |
4-Warning |
EPC on interface [chars] is not supported.To recover, Stop the capture.\n |
Unsupported configuration. |
INVALID |
Stop the capture on %s interface.\n |
FED3_L3M_SYS_MSG-3-RSRC_IPv4_ERR |
3-Error |
Failed to allocate the hardware resource for ipv4 multicast entry. Use \'show platform software fed [switch] <module> ip multicast retry mroute\' for details. |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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. |
FED3_L3M_SYS_MSG-3-RSRC_IPv6_ERR |
3-Error |
Failed to allocate the hardware resource for ipv6 multicast entry. Use \'show platform software fed [switch] <module> ipv6 multicast retry mroute\' for details. |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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. |
FED3_L3M_SYS_MSG-6-RSRC_Recovered |
6-Information |
Failed Multicast hardware resources recovered. Multicast replication will be operational again. |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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. |
FED3_L3_ERRMSG-3-L3_FIB_OUT_OF_RESOURCE |
3-Error |
Failed to program [chars] fib [chars]/[dec] in NPU due to out of resource\n |
Running out of Hardware resource to support the scale of this L3 FIB feature. |
INVALID |
Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform software fed active ip/ipv6 route summary |
FED3_L3_ERRMSG-3-L3_PORT_OUT_OF_RESOURCE |
3-Error |
Failed to program port [chars] in NPU due to out of resource\n |
Running out of Hardware resource to support the scale of the L3 Port feature. |
INVALID |
Verify supported scale for the platform from sdm and reduce the L3 Port scale accordingly. Capture show platform hardware fed active fwd-asic resource utilization |
FED3_L3_ERRMSG-3-UNSUPPORTED_ACTION |
3-Error |
ERROR:[chars] Additionally, please remove this command from the interface config mode.\n |
The specified action is not supported on this platform. |
INVALID |
Find out more about this unsupported functionality from the release documents and remove the command from the interface config mode |
FED3_L3_ERRMSG-6-ADVISORY_NOTICE |
6-Information |
Advisory Notice: [chars] \n |
This message is to bring attention to the user about certain capabilities and limitations of a feature. |
INVALID |
No action is needed. Please be mindful of the limitations. |
FED3_MPLS_ERRMSG-3-mpls_unsupported_feature |
3-Error |
Unsupported feature. Failed to program. [chars] in software or hardware\n |
The feature is not yet supported. |
INVALID |
Find out more about this unsupported feature from the release documents and remove the command from the interface config mode |
FED3_MPLS_ERRMSG-4-MPLS_L2VPN_ATOM_DISP_PAUSE |
4-Warning |
Critical limit reached for [chars] resource. MPLS L2VPN ATOM_DISP Create PAUSED.\n |
MPLS L2VPN ATOM DISP creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization |
FED3_MPLS_ERRMSG-4-MPLS_L2VPN_ATOM_IMP_PAUSE |
4-Warning |
Critical limit reached for [chars] resource. MPLS L2VPN ATOM_IMP Create PAUSED.\n |
MPLS L2VPN ATOM IMP creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization |
FED3_MPLS_ERRMSG-4-MPLS_L2VPN_XCON_AC_PAUSE |
4-Warning |
Critical limit reached for [chars] resource. MPLS L2VPN XCON_AC Create PAUSED.\n |
MPLS L2VPN XCON_AC creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization |
FED3_MPLS_ERRMSG-4-MPLS_LABEL_PAUSE |
4-Warning |
Critical limit reached for [chars] resource. MPLS Label Create PAUSED.\n |
MPLS Label OCE creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization |
FED3_MPLS_ERRMSG-4-MPLS_LENTRY_PAUSE |
4-Warning |
Critical limit reached for [chars] resource. Lentry Create PAUSED.\n |
MPLS Lentry creations are paused as needed resources(mentioned in error message) are not available so new label entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. 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 |
FED3_MPLS_ERRMSG-4-mpls_out_of_resource |
4-Warning |
Out of resource for MPLS [chars]. Failed to program [chars] in hardware\n |
Running out of Hardware resource to support the scale of this MPLS feature. |
INVALID |
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 |
FED3_MPLS_ERRMSG-6-MPLS_L2VPN_ATOM_DISP_RESUME |
6-Information |
[chars] resources are now available. MPLS L2VPN ATOM_DISP Create RESUMED.\n |
MPLS L2VPN ATOM DISP creations are resumed. Now new entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED3_MPLS_ERRMSG-6-MPLS_L2VPN_ATOM_IMP_RESUME |
6-Information |
[chars] resources are now available. MPLS L2VPN ATOM_IMP Create RESUMED.\n |
MPLS L2VPN ATOM IMP creations are resumed. Now new entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED3_MPLS_ERRMSG-6-MPLS_L2VPN_XCON_AC_RESUME |
6-Information |
[chars] resources are now available. MPLS L2VPN XCON_AC Create RESUMED.\n |
MPLS L2VPN XCON_AC creations are resumed. Now new entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED3_MPLS_ERRMSG-6-MPLS_LABEL_RESUME |
6-Information |
[chars] resources are now available. MPLS Label Create RESUMED.\n |
MPLS Label creations are resumed. Now new entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED3_MPLS_ERRMSG-6-MPLS_LENTRY_RESUME |
6-Information |
[chars] resources are now available. Lentry Create RESUMED.\n |
MPLS Label entries creations are resumed. Now new label entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED3_PUNJECT-6-PKT_CAPTURE_FULL |
6-Information |
Punject pkt capture buffer is full. Use show command to display the punted packets.\n |
All the available punt capture buffers have been written with punted packets. |
INVALID |
No action is needed. |
FED3_PUNJECT_CLI-6-EPDA_NPU_TRAPS_DEBUGGING_WARNING |
6-Information |
Warning: Please note traps enabled in Enhanced Packet Drop Analyzer (EPDA) will share the counters in Enhanced Drop Detection(EDD) CLI. This will result in showing the same counter values for the trap(s) in EDD\n |
When EPDA is enabled the counters will be shared by EDD while displaying EDD counters |
INVALID |
No action is needed. |
FED3_PUNJECT_CLI-6-EPDA_TM_TRAPS_DEBUGGING_WARNING |
6-Information |
Warning: Enabling TM traps will affect Per VOQ counters. Please clear TM traps once drop-capture is completed\n |
Enabling TM traps will affect per voq counters |
INVALID |
No action is needed. |
FED3_QOS_ERRMSG-3-FED3_SERVICE_POLICY_FAILED |
3-Error |
Failed to apply service-policy.\n |
An error occurred during service-policy installation in FED. |
pangea-qos |
Need to find the info from logs. Use "sh platform software trace message fed active" to find the logs |
FED3_QOS_ERRMSG-3-FED3_SERVICE_POLICY_FAILED_PREVIOUSLY |
3-Error |
The policy [chars] on interface [chars] on [chars] direction is already in ERROR state. No action will be taken.\n |
There was an error occured early. No further action is taken until the policy removed and reattached. |
pangea-qos |
Remove the policy from the interface and reattach. |
FED3_VLAN_MAPPING_ERRMSG-3-MAPPING_HW_ERROR |
3-Error |
Failed to update VLAN_MAPPING in hardware for interface [chars].\n |
An error occurs when mapping VLAN. |
polaris-l2 |
The resource limit would have been reached, remove the recent added vlan mapping configuration |
FED3_VLAN_MAPPING_ERRMSG-3-VP_HW_ERROR |
3-Error |
Failed to add VP in hardware for interface [chars].\n |
An error occurs when adding VP |
polaris-l2 |
VP limit would have been reached, please remove the recent configuration |
FED_CCK_ERRMSG-4-INCONSISTENCY_FOUND |
4-Warning |
Consistency Checker(CCK) detected inconsistency for [chars]. Check 'show consistency run-id [dec] detail'. |
CCK has detected the inconsistency between the IOSD and fmanFP tables. |
INVALID |
Find out the entry using the show consistency <> command |
FED_COND_DEBUG-6-COND_DEBUG_BOTH_V4_V6_ADDR_SET |
6-Information |
Failed to start, both v4 & v6 addr is set |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_INVALID_IN_FILE |
6-Information |
Failed to start, invalid file, not found |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_INVALID_PORT |
6-Information |
Failed to start, invalid Port, not found |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_INVALID_SWITCH |
6-Information |
Failed to start, invalid Switch, not found |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_MAC_NOT_SET |
6-Information |
Failed to start, for simulation packet generation src/dst mac is must |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_MEMORY_ALLOC_FAIL |
6-Information |
Failed to start, memory allocation failed |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_MULTIPLE_ACES |
6-Information |
Multiple entries found in provided ACL, common fields will get overlapped by later entries |
Warning for acl having multiple aces |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_NETWROK_PREFIX_NOT_SUPPORTED |
6-Information |
Failed to start, simulation needs full address, netwrok prefix not supported |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_SRC_AND_DST_ADDR_NOT_SET |
6-Information |
Failed to start, both src and dst addr is required |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_COND_DEBUG-6-COND_DEBUG_START_FAIL |
6-Information |
Failed to start trace |
Packet trace failed to start |
polaris-platform_mgr |
No action is required |
FED_FNF_ERRMSG-3-ADVBASEATTACHERROR |
3-Error |
Unable to attach flow monitor or IP NBAR/Et-analytics to interface [chars]. Flow monitor and IP NBAR/Et-analytics are not allowed on the same interface. |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_FNF_ERRMSG-3-ATTACHERROR |
3-Error |
Failed to attach flow monitor to interface [chars].\n |
An error occurs when attaching the flow monitor to the interface. |
polaris-platform_mgr |
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 |
3-Error |
Failed to detach flow monitor from interface [chars]\n |
Error occurs when detaching the flow monitor from the interface. |
polaris-platform_mgr |
Find out more about the error by using show mgmt-infra trace messages fed-fnf-config-error switch number command |
FED_FNF_ERRMSG-3-FLOWMONITOR_ENABLEERROR |
3-Error |
'[chars]' enablement failed due to '[chars]' configuration present on interface [chars]. These features cannot co-exist. |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_FNF_ERRMSG-3-REFMONITOR_ENABLEERROR |
3-Error |
Failed to enable [chars] [chars] Reflexive ACL on [chars] and traffic will be dropped; '[chars]' configuration present on interface. |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_FNF_ERRMSG-3-REFMONITOR_FAILED |
3-Error |
Failed to enable [chars] [chars] Reflexive ACL on [chars] and traffic will be dropped; Netflow programming failed. |
The requested configuration failed; traffic will be dropped on this interface. |
polaris-platform_mgr |
Find out more about the error with the help of FED logs |
FED_FNF_ERRMSG-3-REFMONITOR_RSCFULL |
3-Error |
Failed to enable [chars] [chars] Reflexive ACL on [chars] and traffic will be dropped; Netflow profiles exhausted. |
The requested configuration failed; traffic will be dropped on this interface. |
polaris-platform_mgr |
Remove the existing FNF/FNF based feature attachment and retry |
FED_FNF_ERRMSG-3-SGTCATTACHERROR |
3-Error |
Detach the existing [chars] before attaching [chars] to interface [chars]. These features cannot co-exist. |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_FNF_ERRMSG-6-NOTALLOWED |
6-Information |
[chars] is not allowed.\n |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_FNF_ERRMSG-6-UNSUPPORTED |
6-Information |
[chars] is unsupported\n |
The requested configuration is not supported. |
polaris-platform_mgr |
Please do not use the current configuration. |
FED_IPC_MSG-5-FAST_RELOAD_COMPLETE |
5-Notice |
Fast reload operation complete |
This is used to indicate that the fast reload is complete. |
accsw-p-fsu |
No action needed. This is not an error. |
FED_L2M_ERRMSG-3-COLLISION_LIST_RSRC_ERR |
3-Error |
Failed to allocate hardware resource for group [chars] - reason: [chars] - entry collided with groups: [chars] in hash |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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_L2M_ERRMSG-3-RSRC_ERR |
3-Error |
Failed to allocate hardware resource for group [chars] - resource type: [chars] - reason: [chars] |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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_L2M_ERRMSG-3-VLAN_RSRC_ERR |
3-Error |
Failed to allocate hardware resource for vlan [dec] - resource type: [chars] - reason: [chars] |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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-3-RSRC_ERR |
3-Error |
Failed to allocate hardware resource for [chars] - rc:[chars] |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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-4-lsm_LB_warning |
4-Warning |
IGP load balance not supported for Label Switch Multicast. Configure 'no mpls mldp forward recursive' to disable |
MPLS IGP load balance/ECMP is not supported. Entries will be put into retry and once user disables the ECMP via CLI, LSM will recover |
INVALID |
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-4-lsm_RSRC_ERR |
4-Warning |
Failed to allocate the hardware resource for LSM(Label Switch multicast) entry, LSM replication will be impacted |
Hardware resource allocation has failed and the entry will not be programmed. Entry will be in retry queue waiting for resources, once available LSM will recover |
INVALID |
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-4-lsm_label_warning |
4-Warning |
MPLS label range from [dec] to [dec] is not supported with Label Switch Multicast (LSM). Reconfigure 'mpls label range' accordingly. |
MPLS range of upper 4k from 1M supported protocal value is reserved for LSM to use internally. |
INVALID |
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-4-lspvif_RSRC_ERR |
4-Warning |
Failed to allocate the hardware resource for Lspvif Adjacency, some of the LSM MDTs will be impacted |
Hardware resource allocation has failed and the entry will not be programmed. Entry will be in retry queue waiting for resources, once available LSM MDTs will recover |
INVALID |
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-6-lsm_RSRC_ERR_recovered |
6-Information |
Failed LSM hardware resources recovered. LSM replication will be operational again |
Hardware resource failure is recovered again and LSM(Label Switch Multicast) will be back to normal |
INVALID |
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-6-lspvif_RSRC_ERR_recovered |
6-Information |
Retry of Lspvif Adjacency hardware resource(s) is(are) successful, LSM MDTs will be operational again |
Hardware resource failure is recovered again and LSM(Label Switch Multicast) will be back to normal |
INVALID |
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-L3_FIB_ENTRY_PAUSE |
3-Error |
Critical limit reached for [chars] resource. L3 FIB Entry Create PAUSED.\n |
L3 FIB Entry creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for l3 routes summary, tcam utiliztion and resource utilization |
FED_L3_ERRMSG-3-L3_FIB_ENTRY_RESUME |
3-Error |
[chars] resources are now available. L3 FIB Entry Create RESUMED.\n |
L3 FIB Entry creations are resumed. Now new entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED_L3_ERRMSG-3-MAX_TUNNEL |
3-Error |
The maximum number of Tunnel has been reached\n |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
New Tunnels will not be working as expected. |
FED_L3_ERRMSG-3-MPLS_LABEL_PAUSE |
3-Error |
Critical limit reached for [chars] resource. MPLS Label Create PAUSED.\n |
MPLS Label OCE creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization |
FED_L3_ERRMSG-3-MPLS_LABEL_RESUME |
3-Error |
[chars] resources are now available. MPLS Label Create RESUMED.\n |
MPLS Label creations are resumed. Now new entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED_L3_ERRMSG-3-MPLS_LENTRY_PAUSE |
3-Error |
Critical limit reached for [chars] resource. Lentry Create PAUSED.\n |
MPLS Lentry creations are paused as needed resources(mentioned in error message) are not available so new label entries can not be programmed in HW. |
INVALID |
Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls summary, tcam utiliztion and resource utilization |
FED_L3_ERRMSG-3-MPLS_LENTRY_RESUME |
3-Error |
[chars] resources are now available. Lentry Create RESUMED.\n |
MPLS Label entries creations are resumed. Now new label entries can be programmed in HW. |
INVALID |
No action needs to be taken. |
FED_L3_ERRMSG-3-RSRC_ERR |
3-Error |
Failed to allocate hardware resource for [chars] - rc:[dec] |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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-RSRC_L3_LE_ERR |
3-Error |
Interface [chars] creation failed due to L3 Interface hardware resource exhaustion |
Hardware resource for L3 Interface exhausted and the requested interface will not be created. |
INVALID |
Collect output of show platform hardware fed switch <switch number> fwd-asic resource utilization command. Check if RSC_L3IF_LE has exhausted. If yes, free up any unused L3 Interfaces by doing no interface <interface> and retry creating the failed interface. |
FED_L3_ERRMSG-3-UNSUPPORTED_CMD |
3-Error |
[chars] is not supported on the interface [chars]\n |
The specified cli is not yet supported. |
INVALID |
Find out more about this unsupported feature from the release documents and remove the command from the interface config mode |
FED_L3_ERRMSG-3-ecr_err |
3-Error |
Platform unicast routing ecr module encountered [chars] error in FED\n |
An error occurred in platform ecr code. |
INVALID |
Find out more about this error by using the show platform ipunicast ecr commands. |
FED_L3_ERRMSG-3-fib_err |
3-Error |
Platform unicast routing fib module encountered [chars] error in FED\n |
An error occurred in platform fib code. |
INVALID |
Find out more about this error by using the show platform ipunicast route commands. |
FED_L3_ERRMSG-3-intf_err |
3-Error |
[chars] interface [chars]\n |
Error in HW programming for Interface. |
INVALID |
Find out more about this failure from ifm show outputs and debugs for the interface |
FED_L3_ERRMSG-3-mpls_ecmp_modify_err |
3-Error |
MPLS Load Balance modify is not supported [dec]\n |
Modification of an ECMP object with MPLS Adjacencies is not supported yet. It is not an expected event |
INVALID |
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_out_of_resource |
3-Error |
Out of resource for MPLS [chars]. Failed to program [chars] in hardware\n |
Running out of Hardware resource to support the scale of this MPLS feature. |
INVALID |
Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls summary, tcam utiliztion and resource utilization |
FED_L3_ERRMSG-3-mpls_recursive_label_err |
3-Error |
Unsupported recursive MPLS label for local_label [dec] [chars]\n |
The specified MPLS local label is recursive and is not yet supported. |
INVALID |
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_unsupported_feature |
3-Error |
Unsupported feature. Failed to program. [chars] in software or hardware\n |
The feature is not yet supported. |
INVALID |
Find out more about this unsupported feature from the release documents and remove the command from the interface config mode |
FED_L3_ERRMSG-3-pbr_err |
3-Error |
Platform unicast routing pbr module encountered [chars] error in FED\n |
An error occurred in platform pbr code. |
INVALID |
Find out more about this error by using the show platform ipunicast policy commands |
FED_L3_ERRMSG-3-wccp_err |
3-Error |
Platform unicast routing wccp module encountered [chars] error in FED\n |
An error occurred in platform wccp code. |
INVALID |
Find out more about this error by using the show platform ipunicast wccp commands. |
FED_PLATFORM_SYMPHONY-4-ROT_VALIDATION_FAILURE |
4-Warning |
The RoT Validation for ASIC [dec] has failed because [chars] |
The NPU RoT validation has failed. This could be due to a hardware or software defect. This is a critical error. NPU will stop forwarding traffic |
polaris-platform_mgr |
No action is required |
FED_PM-3-FRU_SWITCH_TIMEOUT |
3-Error |
Transeiver update timed out. Remove and re-insert all FRUs in this switch to recover.\n |
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. |
polaris-l2 |
Remove and re-insert all FRUs on this switch. The system should recognize and process them correctly after that. |
FED_PM-3-FRU_TIMEOUT |
3-Error |
FRU module [dec] bringup timed out. Remove and re-insert it to recover.\n |
The given FRU module in the switch in question could not be recognized because it took too long do so. |
polaris-l2 |
Remove and re-insert the specified FRU module. The system should recognize it correctly after that. |
FED_PM-3-FRU_TRANSCEIVER_TIMEOUT |
3-Error |
Transceiver event handling for interface [chars] timed out. Remove and re-insert the FRU module containing this interface to recover.\n |
Than handling onf a transceiver event took too long for the given interface. |
polaris-l2 |
Remove and re-insert the FRU module containing this interface. The system should recover from this failure condition after that. |
FED_PM-3-HW_ERROR |
3-Error |
Port Manager error -[chars] hardware update failed.\n |
An error occurred in Port Manager code. |
polaris-l2 |
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 |
3-Error |
Port Manager error -[chars] resource access failed.\n |
An error occurred in Port Manager code. |
polaris-l2 |
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_PTP_ERRMSG-3-ATTACHERROR |
3-Error |
Failed to run PTP [chars].\n |
An error occurs when running PTP. |
polaris-platform_mgr |
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 |
3-Error |
Failed to run PTP [chars]\n |
Error occurs when running PTP. |
polaris-platform_mgr |
Find out more about the error by using show mgmt-infra trace messages fed-ptp-config-error switch number command |
FED_PTP_ERRMSG-6-NOTALLOWED |
6-Information |
[chars] is not allowed.\n |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_PTP_ERRMSG-6-UNSUPPORTED |
6-Information |
[chars] is unsupported\n |
The requested configuration is not supported. |
polaris-platform_mgr |
Please do not use the current configuration. |
FED_PUNJECT-6-PKT_CAPTURE_FULL |
6-Information |
Punject pkt capture buffer is full. Use show command to display the punted packets.\n |
All the available punt capture buffers have been written with punted packets. |
INVALID |
No action is needed. |
FED_QOS_ERRMSG-3-AFD_POLICER_HW_ERROR |
3-Error |
Failed to [chars] for [chars].\n |
An error occurred in programming the Approximate Fair Dropping policer. |
INVALID |
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_QUEUE_HW_ERROR |
3-Error |
Failed to program AFD [chars] virtual queue for [chars].\n |
An error occurred in programming the Approximate Fair Dropping virtual queue. |
INVALID |
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-LABEL_2_QUEUE_MAPPING_HW_ERROR |
3-Error |
Failed to [chars] for [chars]: code [dec].\n |
An error occurred in programming label to queue map. |
INVALID |
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-NETFLOW_TABLE_HW_ERROR |
3-Error |
Failed to program netflow entries for policy-map [chars] for client mac:[chars] iifid:0x%llx. code:[dec].\n |
An error occurred in programming netflow table. |
INVALID |
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-POLICER_HW_ERROR |
3-Error |
Failed to [chars] for [chars]: code [dec].\n |
An error occurred in programming the policer. |
INVALID |
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-POLICER_MAP_HW_ERROR |
3-Error |
Failed to [chars] for [chars]: code [dec].\n |
An error occurred in programming the policer map. |
INVALID |
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-QUEUE_BUFFER_HW_ERROR |
3-Error |
Failed to [chars] for [chars]: code [dec].\n |
An error occurred when programming the queue buffer. |
INVALID |
Find 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 |
3-Error |
Failed to [chars] for [chars]: code [dec].\n |
An error occurred when programming the queue scheduler. |
INVALID |
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_EGRESS_HW_ERROR |
3-Error |
Failed to [chars] for [chars]: code [dec].\n |
An error occurred when programming egress table-map to hardware. |
INVALID |
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 |
3-Error |
Failed to [chars] for [chars]: code [dec].\n |
An error occurred when programming ingress table-map to hardware. |
INVALID |
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_INIT_ERROR |
3-Error |
Failed to initialize [chars].\n |
An error occurred during table-map initialization. |
INVALID |
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-APPLICATION_ID_OVERFLOW |
4-Warning |
Failed to allocate application ID for policy-map [chars] on [chars].\n |
The application IDs are exhausted. |
INVALID |
Reduce the number of applications to make application ID available. |
FED_QOS_ERRMSG-4-CONFIGURE_PORT_TYPE_HW_ERROR |
4-Warning |
Failed to configure port [chars] as [chars] port in hardare. rc:[dec].\n |
The port could not be configured in hardware |
INVALID |
Try to shutdown the port and then unshut the port |
FED_QOS_ERRMSG-4-LABEL_2_QUEUE_MAPPING_OVERFLOW |
4-Warning |
Failed to [chars]. No more queue-maps are available.\n |
The system supports up to 8 queue-maps. This limit has been reached. |
INVALID |
Unconfigure some of the queuing policies to make the resource available. |
FED_QOS_ERRMSG-4-NETFLOW_TABLE_OVERFLOW |
4-Warning |
Failed to program netflow entries for policy-map [chars] for client mac:[chars] iifid:0x%llx. No netflow resource is available.\n |
The netflow resources are exhausted. |
INVALID |
Unconfigure features to make the netflow resource available. |
FED_QOS_ERRMSG-4-OUTPUT_ACS_CLIENT_POLICY_ERROR |
4-Warning |
Unsupported output client policy([chars]).\n |
Unsupported policy. |
INVALID |
Unsupported client output policy |
FED_QOS_ERRMSG-4-OUTPUT_CLIENT_POLICY_ERROR |
4-Warning |
Unsupported output client policy([chars]) - range operators.\n |
Unsupported policy. |
INVALID |
Range operators are not supported in client output policy |
FED_QOS_ERRMSG-4-POLICER_MAP_TABLE_OVERFLOW |
4-Warning |
Failed to [chars] for [chars]. No more policer map tables are available.\n |
The ASIC supports up to 64 policer map tables. This limit has been reached. |
INVALID |
Unconfigure some policer maps to make the resource available. |
FED_QOS_ERRMSG-4-POLICER_OVERFLOW |
4-Warning |
Failed to [chars] for [chars]. No policer resource is available.\n |
The policer resource limit has been reached. |
INVALID |
Unconfigure some policers to make the resource available. |
FED_QOS_ERRMSG-4-STACK_BUFFER_CONFIG_MGIG |
4-Warning |
Detected stack-buffer disable ([dec]), which is not a supported configuration for mGig platforms. Change to 'stack-buffer enable' configuration.\n |
The stack-buffer configuration for an mGig switch should always remain as enabled. |
INVALID |
Change the configuration back as stack-buffer enable |
FED_QOS_ERRMSG-4-TABLEMAP_OVERFLOW |
4-Warning |
Failed to attach [chars]. No more table-maps are available.\n |
The system supports up to 16 table-maps per direction. This limit has been reached. |
INVALID |
Unconfigure some of the table-maps to make the resource available. |
FED_QOS_ERRMSG-4-TCAM_OVERFLOW |
4-Warning |
Failed to program TCAM for policy-map [chars] on [chars].\n |
The TCAM resources are exhausted. |
INVALID |
Unconfigure features to make TCAM resources available. |
FED_SPAN_ERRMSG-3-UNSUPPORTED_CONFIG |
3-Error |
SPAN configuration for source is not supported [chars] \n |
A failure occurred in platform SPAN Source prgm |
polaris-l2 |
This failure occurs with SPAN Src (port, Vlan) is part of a different SPAN session and is being reprogrammed again |
FED_SPAN_ERRMSG-3-fspan_hw_update_err |
3-Error |
Platform FSPAN encountered an error in FED - [chars]\n |
An error occurred in platform FSPAN code. |
polaris-l2 |
Collect output of hardware tables/registers related to FSPAN and details of related ASIC resource handles. |
FED_SPAN_ERRMSG-3-sess_rc |
3-Error |
Platform SPAN encountered an update error in FED - [chars], session [dec], return code [dec].\n |
An error occurred in platform update SPAN code. |
polaris-l2 |
Collect the output of debug platform monitor-fed while configuring SPAN or FSPAN. |
FED_SPAN_ERRMSG-3-span_gen_hw_update_err |
3-Error |
Platform SPAN encountered an error in FED - [chars].\n |
An error occurred in platform SPAN code. |
polaris-l2 |
Collect the output of debug platform monitor-fed command while configuring SPAN or FSPAN. |
FED_SPAN_ERRMSG-3-span_hw_update_err |
3-Error |
Platform SPAN encountered an error in FED - [chars]\n |
An error occurred in platform SPAN code. |
polaris-l2 |
Collect output of hardware tables and registers related to SPAN and details of related ASIC resource handles. |
FED_SPAN_ERRMSG-3-span_stp_status_update_err |
3-Error |
Platform SPAN encountered an error in FED - [chars]\n |
An error occurred in platform SPAN code for STP state updates in ASIC. |
polaris-l2 |
Collect output of hardware tables and registers related to FSPAN and details of related ASIC resource handles. |
FED_SRVO_ERRMSG-3-ATTACHERROR |
3-Error |
Failed to run SRVO [chars].\n |
An error occurs when running SRVO. |
polaris-platform_mgr |
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 |
3-Error |
Failed to run SRVO [chars]\n |
Error occurs when running SRVO. |
polaris-platform_mgr |
Find out more about the error by using show mgmt-infra trace messages fed-srvo-config-error switch number command |
FED_SRVO_ERRMSG-6-NOTALLOWED |
6-Information |
[chars] is not allowed.\n |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_SRVO_ERRMSG-6-UNSUPPORTED |
6-Information |
[chars] is unsupported\n |
The requested configuration is not supported. |
polaris-platform_mgr |
Please do not use the current configuration. |
FED_STATS-6-MEMORY_PARITY_ERR |
6-Information |
Detected memory parity errors on ASIC INST([dec])\n |
Memory parity errors reached threshold. |
iosxe-chassismgr |
If this message occurs, customer needs to reach out to TAC. TAC will collect and review the output of \'show logging onboard switch active message detail\'. If there are so many single-parity memory errors (>=1000 in 24 hours). TAC may ask the switch to be reloaded or RMAed. |
FED_STP_ERRMSG-3-MAX_INSTANCES |
3-Error |
The maximum number of STP instances has been reached:[dec] |
The maximum number of STP instances that can be programmed has been reached. |
INVALID |
Delete or resolve loops manually for the vlans created further. |
FED_VLAN_TRANSLATE_ERRMSG-3-ATTACHERROR |
3-Error |
Failed to run VLAN_TRANSLATE [chars].\n |
An error occurs when running VLAN_TRANSLATE. |
polaris-platform_mgr |
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 |
3-Error |
Failed to run VLAN_TRANSLATE [chars]\n |
Error occurs when running VLAN_TRANSLATE. |
polaris-platform_mgr |
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-6-NOTALLOWED |
6-Information |
[chars] is not allowed.\n |
The requested configuration is not allowed. |
polaris-platform_mgr |
Please try to modify your configuration. |
FED_VLAN_TRANSLATE_ERRMSG-6-UNSUPPORTED |
6-Information |
[chars] is unsupported\n |
The requested configuration is not supported. |
polaris-platform_mgr |
Please do not use the current configuration. |
FED_XCVR_MSG-3-BO_FAILED |
3-Error |
[dec] [dec] break out failed |
New BO command might have entered too fast or Deactivation taking time to clean feature objects |
polaris-l2 |
Likely IOS and FED might be out of state, reload to use BO ports |
FED_XCVR_MSG-3-BO_NOT_FINISHED |
3-Error |
[dec] [dec] previous breakout command not yet finished, wait for completion message |
New BO command might have entered too fast or Deactivation taking time to clean feature objects |
polaris-l2 |
Likely IOS and FED might be out of state, reload to use BO ports |
FED_XCVR_MSG-3-BO_SUCCESSFUL |
3-Error |
[dec] [dec] break out successful |
New BO command might have entered too fast or Deactivation taking time to clean feature objects |
polaris-l2 |
Likely IOS and FED might be out of state, reload to use BO ports |
FED_XCVR_MSG-3-CABLE_AUTH_FAILED |
3-Error |
*** Stack cable authentication failed for cable inserted on stack port [dec] on switch [dec] *** |
Stack Cable authentication failed on the switch |
polaris-l2 |
Fed would have crashed, remove the stack cable inserted in the mentioned port and cross check |
FED_XCVR_MSG-3-CABLE_AUTH_FAILED_RELOAD |
3-Error |
Reloading chassis because cable auth failed on stack_port [dec] |
Stack Cable authentication failed on the switch |
polaris-l2 |
Fed would have crashed, remove the stack cable inserted in the mentioned port and cross check |
FED_XCVR_MSG-3-NO_BO_SUCCESSFUL |
3-Error |
[dec] [dec] no break out successful |
New BO command might have entered too fast or Deactivation taking time to clean feature objects |
polaris-l2 |
Likely IOS and FED might be out of state, reload to use BO ports |
FED_XCVR_MSG-3-NO_PG_SUCCESSFUL |
3-Error |
Slot [dec] Portgroup [dec] No Portgroup Successful |
New PG command might have entered too fast or Deactivation taking time to clean feature objects |
polaris-l2 |
Likely IOS and FED might be out of state, reload to use PG ports |
FED_XCVR_MSG-3-PG_FAILED |
3-Error |
Slot [dec] Portgroup [dec] Failed |
New PG command might have entered too fast or Deactivation taking time to clean feature objects |
polaris-l2 |
Likely IOS and FED might be out of state, reload to use PG ports |
FED_XCVR_MSG-3-PG_SUCCESSFUL |
3-Error |
Slot [dec] Portgroup [dec] Successful |
New PG command might have entered too fast or Deactivation taking time to clean feature objects |
polaris-l2 |
Likely IOS and FED might be out of state, reload to use PG ports |
FED_XCVR_MSG-3-SPEED_MISMATCH |
3-Error |
[chars] are operating in different speeds, Ports in each port-group should operate in same speed. Please make sure that both the ports operate in same speed. Alternatively, Configure hw-module slot <> port-group <> select <speed>, shut and no shut preferred interface to use specific port in the port-group. This config is not supported if any of the ports in port-group is inserted with dual-rate optics. |
The ports in port-group should be of the same speed for all ports to function |
polaris-l2 |
Enter hw-module slot <> port-group <> select <speed>,followed by\n shut and no shut of interface to use a specific port. |
FILTER-3-EWLC_APFILTER_REGEX_CREATE_ERR |
3-Error |
Error in [chars] |
APFilter regular expression error |
iosxe-binos-utils |
Recreate regular expression correctly |
FILTER-3-EWLC_GEN_ERR |
3-Error |
Error in [chars] |
General Wireless LAN Controller Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
FILTER-4-EWLC_APFILTER_PRIORITY_UPDATE_WARN |
4-Warning |
Warning: [chars] |
APfilter priorities are overridden, old filter will be invalid |
iosxe-binos-utils |
LOG_STD_ACTION |
FILTER_BINARY_NOTIFICATION-5-MERGE_COMPLETED |
5-Notice |
Merged logs generation completed. |
Notification to user that merged logs are generated |
iosxe-binos-utils |
Go to bootflash and view the merged logs |
FIRMWARE-5-INSTALL_STATUS |
5-Notice |
Firmware install stage: [chars], install-id: [chars], message: [chars] |
This syslog is generated during firmware installation which goes through multiple steps |
lte-fw |
No action is required |
FIRMWARE-6-INSTALL_STATUS |
6-Information |
Firmware install stage: [chars], install-id: [chars], message: [chars] |
This syslog is generated during firmware installation which goes through multiple steps |
lte-fw |
No action is required |
FLASH_CHECK-3-DISK_QUOTA |
3-Error |
[chars] quota exceeded [free space is [dec] kB] - [recommended free space is [dec] kB] - Please clean up files on [chars]. |
The remaining free space on the disk is below the recommended threshold of at least 30 percent of the installed disk device space. This limits the system from core files necessary to root cause critical system faults. The disk device is bootflash or harddisk. |
iosxe-binos-utils |
Please remove unneeded files from the disk device. Any core files under the core directory should be reported and then deleted. |
FLASH_CHECK-3-FLASH_ISSUE |
3-Error |
Detected Flash issues. Please issue the [chars] command at your earliest convenience. |
eUSB failure is detected, flash partitions may be inaccessible. |
iosxe-binos-utils |
Please issue the cli command shown in the error message. |
FLASH_CHECK-3-FLASH_RECOVERY |
3-Error |
Detected Flash issues. Proceeding with [chars] soft-error recovery. |
eUSB failure is detected, which prevents access of flash partitions. |
iosxe-binos-utils |
No action required |
FLASH_CHECK-3-RESET_FAIL |
3-Error |
Flash recovery failed. Please issue the reload slot <#> command at your earliest convenience. |
An attempted flash recovery has failed. Switch needs to be manually reloaded |
iosxe-binos-utils |
No action required |
FLASH_CHECK-3-RESET_SUCCESS |
3-Error |
Flash recovery was successful. |
An attempted flash recovery was successful. |
iosxe-binos-utils |
No action required |
FMANFP-3-CRYPTO_DEVICE_REQUEST_FAILED |
3-Error |
Crypto-device is busy processing last request. This request will be discarded |
Crypto-device is still processing previous reload reqeust or still processing crypto feature packets. New request will not be applied |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-3-CRYPTO_LICENSE_THPUT_MAX_APPROACHED |
3-Error |
Average crypto throughput rate approached the licensed crypto bandwidth of [dec] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds |
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 |
iosxe-csl |
LOG_STD_NO_ACTION |
FMANFP-3-CRYPTO_LICENSE_THPUT_THRESHOLD_EXCEED |
3-Error |
Average crypto throughput rate exceeded [dec] percent of licensed crypto bandwidth of [dec] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds |
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 |
iosxe-csl |
LOG_STD_NO_ACTION |
FMANFP-3-LICENSE_THPUT_INVALID |
3-Error |
Invalid throughput [dec]kbps |
The throughput value is invalid. The forwarding engine will not operate at the throughput value. |
iosxe-csl |
LOG_STD_DDTS_TAC_DETAILS |
FMANFP-3-REFGRP_ENTRY_LIMIT_EXCEED |
3-Error |
Reflexive group [chars]([dec]) exceeded limitation of [dec] entries. Reflexive functionality is not supported for this ACE, please remove it. |
A software limitation has been exceeded. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-3-REFGRP_LIMIT_EXCEED |
3-Error |
Number of reflexive group exceeded limitation of [dec]. Reflexive functionality is not supported for this ACE, please remove it. |
A software limitation has been exceeded. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-3-REF_ACE_IDX_LIMIT_EXCEED |
3-Error |
Reflexive group [chars]([dec]) ACE index([dec]) exceeded limitation of [dec]. Reflexive functionality is not supported for this ACE, please remove it. |
A software limitation has been exceeded. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-3-REF_ACL_IDX_LIMIT_EXCEED |
3-Error |
Reflexive group [chars]([dec]) ACL index([dec]) exceeded limitation of [dec]. Reflexive functionality is not supported for this ACL, please remove it. |
A software limitation has been exceeded. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-CRYPTO_DEVICE_NOT_PRESENT |
6-Information |
Hardware crypto-device is not present. Request aborted |
Hardware crypto-device is not present on the system. User request doesn't apply or be executed. This may not be an error. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-CRYPTO_DEVICE_REQUEST_COMPLETE |
6-Information |
Crypto-device is ready to process packets |
Crypto-device is load with new core based on user request. Now it is ready to process packets |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-FMANACLLOGMISSMSG |
6-Information |
access-list logging datapath rate-limited or missed [dec] packet[chars] |
Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPACCESSLOGDP |
6-Information |
list [chars] [chars] [chars] [chars][chars] [chars]-> [chars] ([dec]/[dec]), [dec] packet[chars] |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPACCESSLOGNP |
6-Information |
list [chars] [chars] [dec] [chars][chars] [chars]-> [chars], [dec] packet[chars] |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPACCESSLOGP |
6-Information |
list [chars] [chars] [chars] [chars][chars]([dec]) [chars]-> [chars]([dec]), [dec] packet[chars] |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPACCESSLOGSGDP |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' dest-ip='[chars]' type='[dec]' code='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPACCESSLOGSGNP |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[dec]' src-ip='[chars]' dest-ip='[chars]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPACCESSLOGSGP |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' src-port='[dec]' dest-ip='[chars]' dest-port='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPV6ACCESSLOGDP |
6-Information |
list [chars] [chars] [chars] [chars][chars] [chars]-> [chars] ([dec]/[dec]), [dec] packet[chars] |
A packet matching the log criteria for the given access list was detected. |
iosxe-acl |
LOG_STD_NO_ACTION |
FMANFP-6-IPV6ACCESSLOGNP |
6-Information |
list [chars] [chars] [dec] [chars][chars] [chars]-> [chars], [dec] packet[chars] |
A packet matching the log criteria for the given access list was detected. |
iosxe-acl |
LOG_STD_NO_ACTION |
FMANFP-6-IPV6ACCESSLOGP |
6-Information |
list [chars] [chars] [chars] [chars][chars]([dec]) [chars]-> [chars]([dec]), [dec] packet[chars] |
A packet matching the log criteria for the given access list was detected. |
iosxe-acl |
LOG_STD_NO_ACTION |
FMANFP-6-IPV6ACCESSLOGSGDP |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' dest-ip='[chars]' type='[dec]' code='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPV6ACCESSLOGSGNP |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[dec]' src-ip='[chars]' dest-ip='[chars]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANFP-6-IPV6ACCESSLOGSGP |
6-Information |
ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' src-port='[dec]' dest-ip='[chars]' dest-port='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' |
A packet matching the log criteria for the given access list was detected. |
INVALID |
LOG_STD_NO_ACTION |
FMANRP-3-OBJ_DWNLD_TO_FP_FAILED |
3-Error |
[chars] download to FP failed |
An object has failed to download to the forwarding processor (FP) |
iosxe-fwdmgr |
Examine the process logs to identify the cause for object download failure |
FMANRP-3-PEER_IPC_RESET |
3-Error |
IPC to [chars] has been reset after previous stuck |
IPC to a peer has been reset after previous stuck |
iosxe-fwdmgr |
check if there is any functional impact after recovery |
FMANRP-3-PEER_IPC_RESUME |
3-Error |
IPC to [chars] has returned to normal after previous stuck |
IPC to a peer is back to normal after previous stuck |
iosxe-fwdmgr |
check if there is any functional impact after recovery |
FMANRP-3-PEER_IPC_STUCK |
3-Error |
IPC to [chars] is stuck for more than [dec] seconds |
IPC to a peer is stuck, resulting no new messages sent over for a long time |
iosxe-fwdmgr |
Run show platform peer object-manager rp [active|standby] to confirm that no new messages are sent over the Config IPC |
FMANRP-4-INVALID_CCE_POSITION |
4-Warning |
Invalid position '[dec]' prevented [chars] |
A messaging error has occurred during service-policy modification and the configuration could not be downloaded properly |
iosxe-fwdmgr |
LOG_STD_DDTS_TAC_DETAILS |
FMAN_CAPWAP-3-AP_TUNNEL_CLEANUP_PENDING |
3-Error |
AP CAPWAP tunnel cleanup is incomplete. [chars] |
CAPWAP tunnel delete acknowledgement is not yet received from FMAN FP |
ewlc-ap |
LOG_STD_ACTION |
FMAN_CAPWAP-3-AP_TUNNEL_EXIST |
3-Error |
AP CAPWAP tunnel plumb failure. [chars] |
CAPWAP tunnel plumb failure due to MAC or IFID conflict |
ewlc-ap |
LOG_STD_ACTION |
FMAN_IPSEC_NGWC-3-IPSEC_ANTI_REPLAY_ERR |
3-Error |
IPSEC (flow id [dec]) receives anti-replay error. |
traffic being received is not within the IPSec anti-replay window. |
iosxe-fwdmgr |
Check the size of anti-replay window configured. Adjust to maximum 256-bits if needed |
FMAN_IPSEC_NGWC-3-IPSEC_CONFIG_FAIL |
3-Error |
IPSEC fail to configure because [chars]. |
The IPSEC configuration has failed. This could be due to a hardware/software resource limitation or a software defect. |
iosxe-fwdmgr |
Check the logs for information. Reconfigure IPSEC |
FMAN_IPSEC_NGWC-3-IPSEC_INIT_FAIL |
3-Error |
IPSEC fail to initialize because [chars]. |
The IPSEC initialization has failed. This could be due to a hardware/software resource limitation or a software defect. |
iosxe-fwdmgr |
Check the logs for information. Reboot the system if IPSEC needs to be configured |
FMAN_IPSEC_NGWC-3-IPSEC_TTL_NOT_SUPPORT |
3-Error |
IPSEC tunnel ttl configuration ignored because [chars]. |
The IPSEC configuration for tunnel ttl value is not supported and therefore has been ignored. |
iosxe-fwdmgr |
remove tunnel ttl configuration as it is not supported. |
FMAN_IPSEC_NGWC-3-IPSEC_TUNNEL_CONFIG_FAIL |
3-Error |
[chars] SADB [dec] IF_ID [dec] |
The IPSEC configuration has failed. This could be due to a hardware/software resource limitation or a software defect. |
iosxe-fwdmgr |
Check the logs for information. Reconfigure IPSEC |
FMFP-3-DP_NOMEM |
3-Error |
DP not enough memory. [chars] |
An object download to DP failed because the memory of DP is not enough. |
iosxe-fwdmgr |
Run show platform resource to see the memory usage |
FMFP-3-INTERFACE_OBJECT_NOT_FOUND |
3-Error |
Interface object lookup by [chars] not found for interface [dec] |
The desired interface object was not found. |
iosxe-fwdmgr |
Examine the interface state in the operating system, route processor (RP) and forwarding processor (FP) forwarding manager logs. |
FMFP-3-OBJ_ACK_FROM_DP_RESUME |
3-Error |
AOM ack of objects to Data Plane is back to normal |
An object ack from lower layer to FMAN-FP has finished after a temporary stuck. It can be caused by incomplete configuration or software defects |
iosxe-fwdmgr |
check if there is any functional impact after recovery |
FMFP-3-OBJ_ACK_FROM_DP_STUCK |
3-Error |
AOM ack download to Data Plane is stuck for more than [dec] seconds [chars] |
An object ack from lower layer to FMAN-FP has taken long time. It can be caused by incomplete configuration or software defects |
iosxe-fwdmgr |
Run show platform software object-manager fp [active|standby] [pending-ack-update| pending-ack-batch|pending-ack-commands] sorted <min_pending_time> to see the sorted list of update/ batch/command in pending state for more than the min_pending_time. For incomplete configuration, use show platform platform software object fp [active|standby] resolve to see if there is any resolve object |
FMFP-3-OBJ_DWNLD_TO_DP_FAILED |
3-Error |
[chars] download to DP failed |
An object has failed to download to the data plane |
iosxe-fwdmgr |
Examine the list of error objects in the forwarding processor (FP) forwarding manager asynchronous object logs. |
FMFP-3-OBJ_DWNLD_TO_DP_RESUME |
3-Error |
AOM download of objects to Data Plane is back to normal |
An object download from FMAN-FP to lower layer has finished after a temporary stuck. It can be caused by incomplete configuration or software defects |
iosxe-fwdmgr |
check if there is any functional impact after recovery |
FMFP-3-OBJ_DWNLD_TO_DP_STUCK |
3-Error |
AOM download to Data Plane is stuck for more than [dec] seconds [chars] |
An object download from FMAN-FP to lower layer has taken long time. It can be caused by incomplete configuration or software defects |
iosxe-fwdmgr |
Run show platform software object-manager fp [active|standby] [pending-issue-update|pending-issue-batch] sorted <min_pending_time> to see the sorted list of update/batch/ command in pending state for more than the min_pending_time. For incomplete configuration, use show platform platform software object fp [active|standby] resolve to see if there is any resolve object |
FMFP_ACL-3-ACL_LIMIT_EXCEEDED |
3-Error |
ACL [chars] exceeded limitation of [dec] ACEs per ACL |
A software limitation has been exceeded. |
iosxe-fwdmgr |
Reduce the access control list (ACL) configuration. A reboot of the forwarding processor (FP) is recommended. |
FMFP_ACL-3-ACL_MODIFY_FAILED |
3-Error |
ACL:[chars] modification through object group edit failed |
Object-group used in the ACL was modified. Those changes could not be accommodated in the ACL |
asr1k-acl |
Fix the object-group changes. Delete ACL and reconfigure it |
FMFP_ACL-3-ACL_OBJECT_DOWNLOAD |
3-Error |
[chars][chars] fail to download because [chars]. |
The access control list (ACL) object has failed to download. This could be due to a hardware or software resource limitation or a software defect. |
iosxe-fwdmgr |
Check the logs for information on the relevant object download states. Remove the ACL attachment to the interface or delete the ACL. Reboot the forwarding processor (FP). |
FMFP_ACL-3-ACL_PROTOCOL_CHECK |
3-Error |
ACL [chars] protocol does not match what was previously configured |
The error occurs for one of two reasons. An access control list (ACL) reference was made to an ACL of a different protocol; or an ACL was added or edited when there were similarly named ACL references of a different protocol |
iosxe-fwdmgr |
Remove the conflicting ACL or the conflicting ACL references. |
FMFP_ACL-3-OGACL_BINCODE_CHECK |
3-Error |
[chars] OGACL request failed in bincode check: required bits ([dec]) max available bits ([dec]). |
The scaled OGACL failed to download due to the hardware or software resource limitation on bincode. |
asr1k-acl |
Check the logs for information on the relevant object download states. Remove the OGACL configuration and binding, reduce the scaling and reconfigure it |
FMFP_ACL-3-OGACL_PD_RESOURCE |
3-Error |
[chars] OGACL runs out of PD resources. |
The scaled OGACL failed to download due to PD hardware or software resource limitation. |
asr1k-acl |
Check the logs for information on the relevant object download states. Remove the OGACL configuration and binding, reduce the scaling and reconfigure it |
FMFP_ACL-3-SGACL_OBJECT_DOWNLOAD |
3-Error |
SGACL Cell ([dec] [dec]) policy [chars] fail to download because [chars]. |
The SGACL policy has failed to download. This could be due to a hardware or software resource limitation or a software defect. |
iosxe-fwdmgr |
Check the logs for information on the relevant object download states. Remove the SGACL policy for that cell, correct the error and reconfigure it |
FMFP_CCK-4-INCONSISTENCY_FOUND |
4-Warning |
Consistency Checker(CCK) detected inconsistency for [chars]. Check 'show consistency-checker run-id [dec] detail'. |
CCK has detected the inconsistency between the IOSD and fmanFP tables. |
iosxe-fwdmgr |
Find out the entry using the show consistency-checker <> command |
FMFP_CXSC-3-CXSC_DEINITIALIZATION |
3-Error |
[chars] Returned: [chars] |
The CXSC DEINITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect. |
iosxe-cxsc |
Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC. |
FMFP_CXSC-3-CXSC_DOMAIN_CONFIG |
3-Error |
[chars] Returned: [chars] |
The CXSC DOMAIN CONFIG DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect. |
iosxe-cxsc |
Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC. |
FMFP_CXSC-3-CXSC_INITIALIZATION |
3-Error |
[chars] Returned: [chars] |
The CXSC INITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect. |
iosxe-cxsc |
Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC. |
FMFP_CXSC-3-CXSC_POLICY_DOWNLOAD |
3-Error |
[chars] Returned: [chars] |
The CXSC POLICY DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect. |
iosxe-cxsc |
Check memory usage and router configuration and try to re-activate virtual service again. If it shows same results then please contact TAC. |
FMFP_CXSC-6-CXSC_POLICY_DOWNLOAD_SUCCESS |
6-Information |
New policy version: [dec] has now been installed and is active |
The CXSC POLICY DOWNLOAD of the numbered version has succeeded. |
iosxe-cxsc |
This an informational message only, no action is required. Note that policy version is not monotonically increasing so there is nothing to be concerned about if the current installed policy version is less than the previous installed policy version. |
FMFP_QOS-4-QOS_WITHOUT_UPDATING |
4-Warning |
Warning, Qos download AOM without updating [chars] |
qos download aom wihtout updating action. |
iosxe-fwdmgr |
No action is required. |
FMFP_QOS-6-QOS_STATS_PROGRESS |
6-Information |
statistics are progressing |
QoS statistics are now progressing normally. This is an informational message. |
iosxe-fwdmgr |
No action is required. |
FMFP_QOS-6-QOS_STATS_STALLED |
6-Information |
statistics stalled |
QoS statistics are temporarily stalled. This is an informational message. |
iosxe-fwdmgr |
No action is required. |
FMFP_URPF-3-LIST_DOWNLOAD |
3-Error |
Unicast RPF list [chars] for list [dec] fail to download because [chars]. |
The unicast reverse path forwarding (URPF) list failed to download. This can be caused by a hardware or software resource limitation or software defect. |
iosxe-fwdmgr |
Check the logs for information on the relevant download states. Reboot the forwarding processor (FP). |
FMFP_URPF-3-OBJECT_DOWNLOAD |
3-Error |
Unicast RPF [chars] on inteface [chars] fail to download because [chars]. |
The unicast reverse path forwarding (URPF) operation failed to download. This can be caused by a hardware or software resource limitation or a software defect. |
iosxe-fwdmgr |
Check the logs for information on the relevant download states. Remove the uRPF feature enabled on any interface. Reboot the forwarding processor (FP). |
FMRP_CCK-4-INCONSISTENCY_FOUND |
4-Warning |
Consistency Checker(CCK) detected inconsistency for [chars]. Check 'show consistency-checker run-id [dec] detail'. |
CCK has detected the inconsistency between the IOSD and fmanRP tables. |
iosxe-fwdmgr |
Find out the entry using the show consistency-checker <> command |
FPGA_DRV-1-CRC_ERR |
1-Alert |
SEU errors are detected in FPGA\n |
SEU errors are detected in FPGA |
INVALID |
LOG_STD_ACTION |
FPMD-3-ACL_PROGRAM_FAILURE |
3-Error |
Failed to associate access-list: [chars]. Reason: [chars] |
This syslog is generated when FPMD cannot program or partially programmed given access-list in datapath. This error can result into packets flowing through the network without applying access-list as intended |
vip-cedge-policy |
Check btrace for any error logs, collect tech-support and share with Cisco TAC |
FPMD-3-MAX_FILTER_EXCEEDED |
3-Error |
Filter count exceeded Max ([dec]) filters per class for class_id [dec] at filter_id [dec] |
This syslog is generated when maximum number of filters have already been reached for given class |
vip-cedge-policy |
Remove any unused filters from given class |
FPMD-3-POLICY_PROGRAM_FAILURE |
3-Error |
Failed to associate data-policy [chars] with vpn-list: [chars]. Reason: [chars] |
This syslog is generated when FPMD cannot program or partially programmed given data-policy in datapath. This error can result into packets flowing through the network without applying data-policy as intended |
vip-cedge-policy |
Check btrace for any error logs, collect tech-support and share with Cisco TAC |
FPMD-3-SDWAN_POLICE_CONFIRM_BURST_INCREASED |
3-Error |
SDWAN Policer [chars] Conform burst [dec] increased to [dec] |
This syslog is generated when FPMD receives policer config but configured policer burst is less than the default burst tolerance for the CIR |
vip-cedge-policy |
Check btrace for any error logs, collect tech-support and share with Cisco TAC |
FPMD-5-FLOW_LOG |
5-Notice |
FLOW LOG device-vpn: [dec] tenant-vpn: [dec] src: [chars]/[dec] dst: [chars]/[dec] proto: [dec] tos: [dec] direction: [chars], policy: [chars], sequence: [dec], Result: [chars] Pkt count: [dec] bytes: [dec] Ingress-Intf: [chars] Egress-intf: [chars] Tenant: [chars] |
This syslog is generated for every flow that matches data-policy, app-route policy and/or access-list. The log contains information about L3 and L4 headers, along with direction and result |
vip-cedge-policy |
No action is required |
FPMD-6-ACL_PROGRAM_SUCCESS |
6-Information |
Successfully associated access-list: [chars] |
This informative log is generated when access-list is successfully programmed in data-path |
vip-cedge-policy |
No action is required |
FQDN_MESSAGE-3-FQDN_FLEX_ERR |
3-Error |
Error in [chars] |
ewlc fqdn flex push error message. |
iosxe-binos-utils |
LOG_STD_ACTION |
FQDN_MESSAGE-3-FQDN_LISTNAME_ERR |
3-Error |
Error in [chars] |
ewlc FQDN url list name error message. |
iosxe-binos-utils |
LOG_STD_ACTION |
FQDN_MESSAGE-3-FQDN_LOCAL_ERR |
3-Error |
Error in [chars] |
ewlc fqdn urllist forwarding push error message. |
iosxe-binos-utils |
LOG_STD_ACTION |
FTMD-3-FIB_ROUTE_ADD_FAIL |
3-Error |
Route addition failed for prefix [chars], reason [chars] |
This syslog is typically generated when the system is under stress and a route cannot be added in forwarding base |
cedge-forwarding |
Please collect tech-support and share with Cisco TAC, a support ticket should be created to debug this |
FTMD-3-TLOC_ADD_FAIL |
3-Error |
TLOC ([chars]/[chars]) addition failed, reason: [chars] |
This syslog is typically generated when the system is under stress and a TLOC cannot be added in forwarding base or encountered a error |
cedge-forwarding |
No action is required |
FTMD-5-FLOW_LOG |
5-Notice |
**HSL-LOGGING IMPLICIT-ACL** vpn: [dec], source: [chars]/[dec], destination: [chars]/[dec], protocol: [dec], tos: [dec], reason: [chars], packets: [dec], bytes: [dec], ingress-interface: [chars], egress-interface: [chars] |
This syslog is generated whenever a packet hits implicit ACL |
cedge-forwarding |
No action is required |
GEOFENCE-2-DEVICE_LOCATION_INSIDE |
2-Critical |
Device location is inside Geofencing range ([chars]) current latitude/longitude: (%.6f, %.6f) |
This syslog is generated when the device location is inside configured Geofencing range |
geo-fencing |
No action is required |
GEOFENCE-2-DEVICE_LOCATION_LOST |
2-Critical |
Device location unavailable [chars] |
This syslog is generated when the device location is lost |
geo-fencing |
No action is required |
GEOFENCE-2-DEVICE_LOCATION_OUTSIDE |
2-Critical |
Device location is outside Geofencing range, current latitude/longitude: (%.6f, %.6f) |
This syslog is generated when the device location is outside configured Geofencing range |
geo-fencing |
No action is required |
GEOFENCE-5-DEVICE_LOCATION_UPDATE |
5-Notice |
Device location changed by more than 20 meters from last report, current latitude/longitude: (%.6f, %.6f) |
This syslog is generated when the device moves within configured Geofencing range |
geo-fencing |
No action is required |
GEOFENCE-6-DEVICE_TRACKING_STARTED |
6-Information |
Device Tracking started in Geofencing mode ([chars]) |
This syslog is generated when device tracking is started |
geo-fencing |
No action is required |
GEOFENCE-6-DEVICE_TRACKING_STOPPED |
6-Information |
Device Tracking stopped in Geofencing mode |
This syslog is generated when device tracking is stopped while Geofencing feature is enabled |
geo-fencing |
No action is required |
GEO_CLOUDM-5-EXEC_CLI |
5-Notice |
Exec CLI : [chars] |
Information message related to exec cli |
ewlc-ap-location |
LOG_STD_NO_ACTION |
GEO_CLOUDM-5-RANGING_REQUEST |
5-Notice |
Ranging request : [chars] |
Information message related to ranging request |
ewlc-ap-location |
LOG_STD_NO_ACTION |
GNMIB-5-SRV_ADMIN_SCN |
5-Notice |
Component [ [chars] ] administrative state: [chars] |
gnmib component administrative state |
polaris-gnmi-infra |
ACTION_NONE_REQUIRED |
GNMIB-5-SRV_OPER_SCN |
5-Notice |
Component [ [chars] ] operational status: [chars] |
gnmib component operational status |
polaris-gnmi-infra |
ACTION_NONE_REQUIRED |
GNMIB-6-GRPC_CON_STATE |
6-Information |
Received gRPC [chars] from [chars] for RPC [chars] |
gRPC Connection state logging |
polaris-gnmi-infra |
ACTION_NONE_REQUIRED |
GNMIB-6-GRPC_CON_STATE_AUTH |
6-Information |
Received gRPC [chars] from [chars] for RPC [chars] for user [chars] group [chars] |
gRPC Connection state logging with user authentication |
polaris-gnmi-infra |
ACTION_NONE_REQUIRED |
GNMIB-6-GRPC_TUNN_SESS |
6-Information |
Received gRPC Tunnel session request from [chars] for Target Type [chars] |
gRPC Tunnel state logging |
polaris-gnxi-infra |
ACTION_NONE_REQUIRED |
GNMIB-6-GRPC_TUNN_STATE |
6-Information |
Connected to gRPC Destination [chars] ([chars]) with Targets[[chars]] using [chars]:[chars] |
gRPC Tunnel state logging |
polaris-gnxi-infra |
ACTION_NONE_REQUIRED |
HFSLIB-3-HFSINOFAILED |
3-Error |
Inotify failed to initialize : [chars] |
This error occurs when the inotify sub-system is misbehaving |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
HFSLIB-3-HFSINOWATCH |
3-Error |
Inotify failed to add a watch: [chars] |
This error occurs when the inotify sub-system is misbehaving |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
HFSLIB-3-HFSOPEN |
3-Error |
Problem accessing the udev generated file: [chars] |
No explanation. |
iosxe-chassismgr |
LOG_STD_NO_ACTION |
HL_CORE-3-MAY_DEFER_WRAPPER_RESCHEDULE_FAILED |
3-Error |
Failed to (re)schedule CPUHOG protected loop. Operation will be aborted. Please check the logs for more details. |
Hyperlocation was interrupted while trying to defer a looping operation and can not continue. |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
HL_MGR-3-CMX_IPV6_IN_FABRIC |
3-Error |
CMX [chars] connected over IPv6 which is not currently supported for Hyperlocation in Fabric mode. |
Currently the Fabric mode only operates over IPv4. |
iosxe-binos-utils |
Please connect the CMX over IPv4, or change the mode to flex/local. |
HL_MGR-3-NEXTHOP_OUTPUT_INTERFACE_NOT_SVI |
3-Error |
CMX [chars] is reachable through a routed port with MAC address %pM. This deployment configuration is not supported for Hyperlocation |
CMX should be reachable via a SVI (VLAN) interface for traffic forwarding to be operational |
iosxe-binos-utils |
Please rejoin CMX. |
HMAN-2-INITIALIZATION_FAILED |
2-Critical |
Host Manager initialization failed. |
Initialization of the host manager failed. |
iosxe-hostmgr |
Review Host Manager logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
HMAN-3-CONSOLE_SETUP_FAILED |
3-Error |
Failed to setup console service. It should be enabled on [chars] |
Setup of a console service failed. |
iosxe-hostmgr |
Check the host manager launch parameters and correct as required. |
HMAN-3-HOSTNAME_SET_FAILED |
3-Error |
Failed to set hostname: [chars] |
The host manager received notification that the system hostname has been set. The host manager failed to pass this value to the ASR kernel. |
iosxe-hostmgr |
Repeat the process to configure the hostname. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
HMAN-3-VRF_API_FAILED |
3-Error |
[chars], vrf ([chars]) - ret ([dec]) |
The host manager has received notification that the VRF information needs to be modified. The host manager failed to perform the operation due to the error indicated in the log. |
iosxe-hostmgr |
Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
HMAN_CPU-3-PAGE_FAULT_HIGH |
3-Error |
CPU Usage due to Memory Pressure exceeds threshold on [chars]. Below are the top 5 memory consuming processes: [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB) |
When CPU usage due to Major Page Fault exceeds a pre-defined threshold for a CPU core, this error message is emitted. |
iosxe-hostmgr |
No action is needed if system continues to perform as expected. If sytem performance deteriorate (and eventually, system reloads due to unspecified reason) around the time when this message is observed, open a case with the Technical Assistance Center via the following Internet link, or contact your Cisco technical support representative: http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl |
HW_IDPROM_ENVMON-2-ACT2_UDI_DATA_INVALID |
2-Critical |
The act2 udi secure area format mismatch with unsecure area |
This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID |
3-Error |
The idprom contains an invalid checksum in a sensor entry. Expected: %x, calculated: %x |
If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
HW_IDPROM_ENVMON-3-HW_IDPROM_FIELD_INVALID |
3-Error |
The idprom contains an invalid environmental monitoring field. |
If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
HW_IDPROM_ENVMON-3-PS_IDPROM_INVALID_PID |
3-Error |
[chars] in slot PFU[dec] has INVALID PID [chars] and it needs to be replaced immediately |
The PID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate replacement is required |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
HW_PFU-3-PFU_IDPROM_CORRUPT |
3-Error |
The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component |
The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
HW_PFU-3-PFU_IDPROM_INVALID_PID |
3-Error |
The PEM/FM idprom has invalid PID in slot PFU[dec] The system will run without environmental monitoring for this component |
The idprom contains PID information required in order to properly operate the environmental monitoring subsystems. The idprom PID is invalid , therefore no monitoring will take place. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
HW_PFU-3-PFU_IDPROM_READ_ERR |
3-Error |
Could not read the PEM/FM idprom in slot P[dec].The system will run without environmental monitoring for this component |
The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. |
iosxe-chassismgr |
LOG_STD_RECUR_ACTION |
HW_PFU-3-PFU_UNSUPPORTED_PID |
3-Error |
The PEM/FM in slot P[dec] is not supported. The system will run without environmental monitoring for this component |
The PEM/FM inserted in not supported by this platform. Replace with a supported module. |
asr900-system-rsp3 |
LOG_STD_RECUR_ACTION |
ID_MANAGER-3-ID_MANAGER_INTERNAL_ERROR |
3-Error |
Internal erorr occurred: [chars] |
Internal Error occured with ID Manager |
iosxe-binos-utils |
LOG_STD_ACTION |
ID_MANAGER-3-INVALID_ID |
3-Error |
bad id in [chars] (id: 0x%08X) |
An ID Manager error occurred |
iosxe-binos-utils |
LOG_STD_ACTION |
ID_MANAGER-3-INVALID_ID_TABLE_SIZE |
3-Error |
bad new ID table size |
A bad new table request to ID Manager occurred |
iosxe-binos-utils |
LOG_STD_ACTION |
IFM-3-RSRC_L3_LE_ERR |
3-Error |
Interface [chars] creation failed due to L3 Interface hardware resource exhaustion |
Hardware resource for L3 Interface exhausted and the requested interface will not be created. |
INVALID |
Collect output of show platform hardware fed switch <switch number> fwd-asic resource utilization command. Check if RSC_L3IF_LE has exhausted. If yes, free up any unused L3 Interfaces by doing no interface <interface> and retry creating the failed interface. |
ILET-2-AUTHENTICATION_FAIL |
2-Critical |
The system integrity check has failed during the boot-up sequence. Please contact Cisco's Technical Assistance Center for more information. |
Trusted Anchor module detected an invalid SUDI. |
iosxe-hostmgr |
Please contact Cisco's Technical Assistance Center for more information |
IM-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
polaris-infra |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
IM-0-UIPEER_CREATE |
0-Emergency |
Failed to create user interface peer. |
The system failed to create a user interface peer. |
polaris-infra |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
IM-2-ACTIVATION_STATE |
2-Critical |
[chars] '[chars]' [chars] [chars] |
The activation state of the named virtualization service has changed as notified by IOx-manager. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. |
IM-2-ALLOC_VIRT_INST_RCS |
2-Critical |
Virtualization Service[chars] |
A memory allocation request failed to allocate a data structure required to activate the virtualization service. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-CPUSHARES_LIMIT |
2-Critical |
Virtualization Service[chars] |
The virtualization service machine definition file is requesting more CPU shares than the system has available for virtualization services. |
polaris-infra |
Deactivate any other virtualization services to free up CPU share resources and activate this virtualization service. If that does not address the problem, then enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-DEACT_FOR_ISSU |
2-Critical |
[chars] Max ([dec]s) |
An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled. |
polaris-infra |
None. Allow the ISSU to continue and the VMs will restart when the ISSU completes; or cancel the ISSU and IOx-manager will automatically restart the VMs. |
IM-2-DISK_IMAGE_PATH |
2-Critical |
Virtualization Service[chars] |
The virtualization service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-FIND_VIRT_INST_ENTRY |
2-Critical |
Failed to find virtualization service with id [dec] in the IOx-manager list |
The virtualization service with the ID named could not be located in the IOx-manager list. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-GENERAL_FAILURE |
2-Critical |
Virtualization Service[chars] |
The named virtualization service has triggered the log. Please interpret the log in the context of the virtualization services. |
polaris-infra |
No action is required |
IM-2-GUESTSHELL_ENABLED |
2-Critical |
The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it. |
Informs the user that the guest shell virtualization service has been enabled (which is done by default). |
polaris-infra |
The user may use or remove the guest shell with the commands specified. |
IM-2-HA_STATE |
2-Critical |
[chars] [chars] [chars] [chars] |
IOx-manager tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. |
IM-2-HA_SWITCHOVER_STATE |
2-Critical |
[chars] [chars] [chars] [chars] |
IOx-manager HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. |
IM-2-HA_SYNC_ERR |
2-Critical |
[chars] '[chars]' [chars] |
The ha-sync persistent storage disk for the virtualization service cannot be watched for sync to standby RP. |
polaris-infra |
Collect the IOx-manager logs and scan them for the cause. |
IM-2-HA_SYNC_THREAD_STATE |
2-Critical |
HA remote sychronize thread has failed and exited. |
IOx-manager tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same. |
IM-2-INITIALIZATION_FAILED |
2-Critical |
Initialization of [chars] failed for IOx Manager |
Initialization of IOx Manager process failed. |
polaris-infra |
Review ioxman 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. |
IM-2-INSTALL_FAILURE |
2-Critical |
Virtualization Service[chars] |
The installation of the virtualization service failed. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the installation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-INSTALL_LOG |
2-Critical |
[chars] [chars] [chars] [chars] |
The installation log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI |
polaris-infra |
No action is required |
IM-2-INSTALL_MEDIA_RETRY |
2-Critical |
VM install media still unavailable.[chars] |
The install media was not detected. Waiting for udev to complete install media(harddisk) detection. |
polaris-infra |
After IOx-manager exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again. |
IM-2-INSTALL_STATE |
2-Critical |
[chars] '[chars]'[chars] [chars] |
The installation state of the named virtualization service has changed as notified by IOx-manager. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. |
IM-2-INVALID_ACT_MSG |
2-Critical |
Virtualization Service[chars] |
The virtualization service activate message was received, however, the data it contained could not be interpreted |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-INVALID_DEACT_MSG |
2-Critical |
Failed to process virtualization service deactivate message |
The virtualization service deactivate message was received, however, the data it contained could not be interpreted |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-INVALID_UNPROV_MSG |
2-Critical |
Failed to process virtualization service unprovision message |
The virtualization service unprovision message was received, however, the data it contained could not be interpreted |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-IOX_INST_CRIT |
2-Critical |
IOX SERVICE [chars] LOG: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
polaris-infra |
No action is required |
IM-2-IOX_INST_LOG_UNTHROTTLE |
2-Critical |
Failed to unthrottle the log for IOX service [chars] |
The named IOX service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason. |
polaris-infra |
For debugging collect the ioxman logs and scan them for the cause. |
IM-2-MEMORY_LIMIT |
2-Critical |
Virtualization Service[chars] |
The virtualization service machine definition file is requesting more memory than the system has available for virtualization services. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-MOVE_STATE |
2-Critical |
[chars] '[chars]' [chars] [chars] |
The move of the core or log file of the named virtualization service has as been successful or failed as notified by IOx-manager. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. |
IM-2-NETWORK_CONFIG_ERROR |
2-Critical |
Virtualization Service[chars] |
A network configuration error has been detected for the named virtualization service. |
polaris-infra |
No action is required |
IM-2-RESET_FORCE |
2-Critical |
Virtualization Services non-recoverable reset command processed |
A 'virtualization service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked. |
polaris-infra |
Once the command is entered and accepted, there is no recourse but to restart the system. |
IM-2-RESIZE_OPER_STATE |
2-Critical |
Virtualization service '[chars]' [chars][chars] to '[dec]' [chars] |
IOx-manager attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. |
IM-2-RSYNC_STATE |
2-Critical |
[chars] [chars] [chars] [chars] |
IOx-manager tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised. |
polaris-infra |
In the failed case, check IOx-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same. |
IM-2-START_FAILED |
2-Critical |
Virtualization Service[chars] |
The named virtualization service failed to start. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-UNINSTALL_ALL_VMS |
2-Critical |
All Virtualization Services are being uninstalled [chars][chars] [chars] |
All virtualization services are being uninstalled by IOx-manager. |
polaris-infra |
Examine the reason given as to why all virtualization services are being uninstalled for more information. If the reason indicated is due to some error condition, check IOx-manager's logs for the cause of the failure. |
IM-2-UPGRADE_LOG |
2-Critical |
[chars] [chars] [chars] [chars] |
The upgrade log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI |
polaris-infra |
No action is required |
IM-2-VCPU_INVALID |
2-Critical |
Virtualization Service[chars] |
The virtualization service machine definition file is requesting invalid VCPU value. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-VCPU_LIMIT |
2-Critical |
Virtualization Service[chars] |
The virtualization service machine definition file is requesting more VCPUs than the system has reserved for virtualization services. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-VIRT_INST_DISK |
2-Critical |
Virtualization Service[chars] |
The virtualization service requires Disk Storage in excess of the Free Disk Storage available to virtualization services. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-VIRT_INST_LOG_UNTHROTTLE |
2-Critical |
Failed to unthrottle the log for virtualization service [chars] |
The named virtualization service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason. |
polaris-infra |
For debugging collect the iox-manager logs and scan them for the cause. |
IM-2-VIRT_INST_MEMORY |
2-Critical |
Virtualization Service[chars] |
The virtualization service requires physical memory in excess of the free memory available to virtualization services. |
polaris-infra |
Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. |
IM-2-VIRT_INST_MGMT_INTERFACE |
2-Critical |
Virtualization service [chars] has no management interface defined but it is configured in CLI. |
A management interface is configured but none is defined. |
polaris-infra |
Deactivate the virtualization service, remove the management interface configuration CLI, and reactivate the virtual-service. |
IM-2-VIRT_INST_STATE |
2-Critical |
Virtualization Service[chars] |
The named virtualization service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed. |
polaris-infra |
An attempt at restarting the virtualization service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the IOx-manager logs and scan them for the cause. |
IM-3-IOX_INST_ERR |
3-Error |
IOX SERVICE [chars] LOG: [chars] |
The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. |
polaris-infra |
No action is required |
IM-3-IOX_NETMASK_ERR |
3-Error |
app configuration has wrong [chars] netmask. |
The netmask configuration is wrong. |
polaris-infra |
Configure guest-ipaddress with IPV4 or IPV6 netmask. |
IM-3-PSS_ERR |
3-Error |
Purpose: [chars], URI: [chars], errcode: [dec] |
Persistent Storage Service handling error |
polaris-infra |
Collect the IOx-manager logs and scan them for the cause. |
IM-3-PSS_SNAPSHOT_ERR |
3-Error |
Source URI: [chars], Destination URI: [chars], errcode: [dec] |
Persistent Storage Service snapshot error |
polaris-infra |
Collect the IOx-manager logs and scan them for the cause. |
IM-3-SDWRAP_ERR |
3-Error |
Description: [chars], errcode: [dec] |
Debug infrastructure error |
polaris-infra |
Collect the IOx-manager logs and scan them for the cause. |
IM-4-HA_SYNC_NEEDED |
4-Warning |
If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover |
Message notifying user that he needs to manually synchronize the Virtualization service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell |
polaris-infra |
User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired. |
IM-4-IOX_INST_WARN |
4-Warning |
IOX SERVICE [chars] LOG: [chars] |
The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. |
polaris-infra |
No action is required |
IM-4-WATCHDOG_TIMER |
4-Warning |
[chars] '[chars]' [chars] [chars] |
The watchdog timer configured for the named virtual service has expired. |
polaris-infra |
Check any logs produced by the virtualization service to determine the cause. |
IM-5-AUX |
5-Notice |
Virtualization Service[chars] |
The AUX login to a virtualization service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution. |
polaris-infra |
No action is required |
IM-5-IOX_INST_NOTICE |
5-Notice |
IOX SERVICE [chars] LOG: [chars] |
The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. |
polaris-infra |
No action is required |
IM-5-IOX_IPV6_NOTICE |
5-Notice |
guest-interface([dec]), IPV6 address configured with guest-ipaddress is ignored |
The IPV6 address configuration with guest-ipaddress is ignored. 'ipv6-address' has been configured and multiple static IPV6 addresses are not supported |
polaris-infra |
Configure guest-ipaddress with IPV4 address. |
IM-5-IOX_NOTICE |
5-Notice |
app-hosting: [chars] |
The generic IOX notice. Please interpret the log in the context of the information provided. |
polaris-infra |
No action is required |
IM-5-IOX_URL_COPY_MSG |
5-Notice |
URL Copy: [chars] |
Copy a package file from URL |
polaris-infra |
Check if 'ip name-server', 'ip name-server vrf Mgmt-vrf' and 'ip http' are configured properly for the device |
IM-5-IOX_VPG_IPV6_MSG |
5-Notice |
no IPv6 address for VirtualPortGroup[dec] in IOS_Oper_DB |
VirtualPortGroup IPv6 address is not present in IOS_Oper_DB |
polaris-infra |
Check if 'show ip interface brief' displays IPv6 for the VirtualPortGroup |
IM-5-PERMISSION_DENIED |
5-Notice |
Virtualization Service '[chars]' is not owned by client IOSd |
An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected. |
polaris-infra |
No action is required. |
IM-6-ACTIVATE_MSG |
6-Information |
app-hosting: [chars] |
Message for activating an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-DEACTIVATE_MSG |
6-Information |
app-hosting: [chars] |
Message for deactivating an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-INSTALL_MSG |
6-Information |
app-hosting: [chars] |
Message for installing an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-IOX_ENABLEMENT |
6-Information |
IOX is ready. |
Message for IOX enablement. |
polaris-infra |
No action is required |
IM-6-IOX_INST_INFO |
6-Information |
IOX SERVICE [chars] LOG: [chars] |
The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. |
polaris-infra |
No action is required |
IM-6-IOX_MEDIA_MSG |
6-Information |
dynamic media: [chars] |
Message for IOX shared median |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-IOX_RECONCILE_INFO |
6-Information |
App-hosting application reconcile process [chars] |
Indicates stage of reconcile (application recovery) process. |
polaris-infra |
No action is required |
IM-6-IOX_START_FAIL |
6-Information |
[chars] failed to start |
Indicates starting an app after installation. |
polaris-infra |
No action is required |
IM-6-IOX_START_INFO |
6-Information |
[chars] cannot be started because it is not installed |
Indicates starting an app before installation. |
polaris-infra |
No action is required |
IM-6-IOX_START_SUCCESS |
6-Information |
[chars] is in RUNNING state |
Indicates starting an app after installation. |
polaris-infra |
No action is required |
IM-6-START_MSG |
6-Information |
app-hosting: [chars] |
Message for starting an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-STOP_MSG |
6-Information |
app-hosting: [chars] |
Message for stopping an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-UNINSTALL_MSG |
6-Information |
app-hosting: [chars] |
Message for uninstalling an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-UPGRADE_MSG |
6-Information |
app-hosting: [chars] |
Message for upgrading an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-6-VERIFICATION_MSG |
6-Information |
app-hosting: [chars] |
Message for signature verification |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IM-7-IOX_INST_DEBUG |
7-Debug |
IOX SERVICE [chars] LOG: [chars] |
The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. |
polaris-infra |
No action is required |
IMGR-0-FIPS_CPP_CLIENT_BYPASS_TEST |
0-Emergency |
CPP Client FIPS bypass test failed for [chars]\n. |
Forwarding Manager CPP client IPSEC bypass test failed. This could be due to a hardware malfunction or a software defect. |
iosxe-fwdmgr |
If the problem persists reboot the forwarding processor (ESP). |
IMGR-0-FIPS_FMFP_BYPASS_TEST |
0-Emergency |
NIST bypass test failed for [chars].\n |
Forwarding Manager IPsec component detected a discrepancy when adding or deleting a security sensitive object. This could be due to a hardware or software resouce limitation or a software defect. |
iosxe-fwdmgr |
Check the logs for information on the relevant object download states. Remove the object or a parent object in question. If the problem persists reboot the forwarding processor (ESP). |
IMGR-0-FIPS_FMFP_N2_SEVERE_ERR_FAIL |
0-Emergency |
Cryptographic coprocessor severe failure: [chars]\n. |
Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted |
iosxe-fwdmgr |
forwarding processor (ESP) is rebooted automatically. no action needed |
IMGR-6-FIPS_FMFP_CRNG_TEST |
6-Information |
continuous [chars]approved RNG test failed.\n |
Forwarding Manager IPsec component detected two identical random number sequences. This could be due to a hardware mulfunction or a software defect. |
iosxe-fwdmgr |
If the problem persists reboot the forwarding processor (ESP). |
IMGR-6-FIPS_FMFP_KAT_TEST |
6-Information |
power up cryptographic self-test did not run to completion: [chars]\n. |
Forwarding Manager power up known answer self-test (KAT) failed. This could be due to a hardware malfunction or a software defect. |
iosxe-fwdmgr |
If using ipsec, reboot the forwarding processor (ESP). |
IMGR-6-FIPS_FMFP_N2_ERR_FAIL |
6-Information |
Cryptographic coprocessor non-critical failure: [chars]\n. |
Cryptographic coprocessor non-critical operation failed. If the problem persists reboot the forwarding processor(ESP) |
iosxe-fwdmgr |
If the problem persists reboot the forwarding processor (ESP). |
IMGR-6-FIPS_FMFP_OLAP_TEST |
6-Information |
FIPS-approved RNG key seed and state overlap.\n |
Forwarding Manager IPsec component detected an overlap in FIPS-approved RNG key seed and state. This could be due to a hardware mulfunction or a software defect. |
iosxe-fwdmgr |
If the problem persists reboot the forwarding processor (ESP). |
IMGR-6-FMFP_CRYPTO_DEVICE_BUSY |
6-Information |
All Crypto Device cores are busy with data packets.\n |
All ESP crypto device are busy. |
qfp-ipsec |
May need to lower crypto traffic rate. |
IMGR-6-FMFP_IPSEC_CRYPTO_CTRL_THROTTLED |
6-Information |
IPsec Control Plane Overload Crypto Device: [chars]. |
This ESP crypto device is overloaded. |
qfp-ipsec |
May need to config platform ipsec control-plane medium|heavy |
IMGR-6-FMFP_IPSEC_MIN_MTU_INFO |
6-Information |
MTU smaller than minimum IPSec MTU, [chars]\n. |
Minimum MTU supported by crypto processor is 256B, MTU lower than 256B is set to 256B |
iosxe-fwdmgr |
No action needed |
IMGR-6-FMFP_IPSEC_UNSUPPORTED_CIPHER |
6-Information |
Cipher [chars] is not supported on this ESP. |
This ESP does not support this IPSec cipher |
iosxe-fwdmgr |
No action needed |
IMGR-6-FMFP_KAT_TEST_RESULT |
6-Information |
crypto self-test for algorithm: ([chars] ... passed)\n. |
Forwarding Manager power up known answer self-test (KAT) success. This is not an error message |
iosxe-fwdmgr |
No action needed. |
INSTALL-3-INSTANT_ERROR_MESSAGE |
3-Error |
Error Message: [chars] |
This message is used to send a instant erorr message. |
iosxe-binos-utils |
No action required. |
INSTALL-3-OPERATION_ERROR_MESSAGE |
3-Error |
Failed to [chars] package [chars], Error: [chars] |
This message is used to inform the failure reason. |
iosxe-binos-utils |
Please refer to the error message to analyze the cause of failure. |
INSTALL-5-INSTALL_AUTO_ABORT |
5-Notice |
Install auto abort timer expired: initiating abort |
An install operation has been aborted because the auto abort timer has expired. |
iosxe-binos-utils |
No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only. |
INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS |
5-Notice |
Install auto abort timer will expire in [dec] seconds |
An install operation will be aborted after specified seconds of time. |
iosxe-binos-utils |
No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only. |
INSTALL-5-INSTALL_COMPLETED_INFO |
5-Notice |
Completed [chars] [chars] [chars] |
This message is used to indicate the completion of install operations. |
iosxe-p-install |
No action required. This is not an error, it is an indication that the system completed this operation. |
INSTALL-5-INSTALL_SCHEDULE_TIMER_PROGRESS |
5-Notice |
Install schedule timer will expire in [dec] seconds |
An install operation will be started after specified seconds of time. |
iosxe-p-install |
No user action is needed. This is an informational message only. |
INSTALL-5-INSTALL_START_INFO |
5-Notice |
Started [chars] [chars] [chars] |
This message is used to indicate the beginning of install operations. |
iosxe-p-install |
No action required. This is not an error, it is an indication that the system is starting this operation. |
INSTALL-5-OPERATION_COMPLETED_INFO |
5-Notice |
Completed [chars] package [chars] |
This message is used to indicate the completion of operations. |
iosxe-binos-utils |
No action required. This is not an error, it is an indication that the system completed the operation. |
INSTALL-5-OPERATION_START_INFO |
5-Notice |
Started [chars] package [chars] |
This message is used to indicate the beginning of operations. |
iosxe-binos-utils |
No action required. This is not an error, it is an indication that the system is starting the operation. |
IOMD_ETHER_GEIM-2-MAX_LIMIT_XCVR |
2-Critical |
Number of [chars] that can be supported has reached the max limit of [dec], transceiver is err-disabled. Unplug the transceiver in interface [chars] |
Because of power constraints, we can support only limited number of high power transceivers in certain platforms. If we insert more than the limit, it will be disabled. It is recommended to unplug the transceiver |
INVALID |
Unplug the transceiver once the max limit is reached |
IOMD_ETHER_GEIM-3-FIFO_OVERFLOW |
3-Error |
[chars] fifo overflow occurred for port [dec] |
A hardware error in phy has occurred |
asr900-im |
Examine the IOMD logs for Phy driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_ETHER_GEIM-3-INTERRUPT_ERR |
3-Error |
interrupt handling error [chars] |
Interrupt could not be handled because of internal sw error |
INVALID |
Examine the IOMD logs. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_ETHER_GEIM-4-LC_OIR_REQD |
4-Warning |
Found mismatch between the line card Phy firmware versions bundled in software and programmed in hardware in slot [dec]. To upgrade the Phy firmware to version bundled in software, perform physical OIR of the line card or run the CLI: hw-module subslot [dec]/[dec] oir power-cycle. If ISSU is in progress, firmware upgrade should be done only after the completion of ISSU. To check the firmware versions, use the CLI: show firmware version all |
During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software will not be automatically enabled and needs a manual upgrade via power-cycle of the line card |
INVALID |
To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot <slot>/<bay> oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd <slot>/<bay> ethernet_controllers phy <port number> api-version or show firmware version all |
IOMD_ETHER_GEIM-4-NOT_SUPPORTED |
4-Warning |
1G Transceiver is inserted in slot [dec] for ports [chars]. The current linecard phy firmware does not support 1G capability. To upgrade the firmware, perform physical OIR of the line card or use the CLI: hw-module subslot [dec]/0 oir power-cycle. If ISSU is in progress, firmware upgrade should be done only after the completion of ISSU |
During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software like 1G will not be automatically enabled and needs a manual upgrade via power-cycle of the line card |
INVALID |
To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot <slot>/<bay> oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd <slot>/<bay> ethernet_controllers phy <port number> api-version or show firmware version all |
IOMD_ETHER_GEIM-4-NOT_SUPPORTED_XCVR |
4-Warning |
1G Transceiver is inserted in slot [dec] for port [dec]. The current linecard phy firmware does not support 1G capability. To upgrade the firmware, perform physical OIR of the line card or use the CLI: hw-module subslot [dec]/0 oir power-cycle |
During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software like 1G will not be automatically enabled and needs a manual upgrade via power-cycle of the line card |
INVALID |
To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot <slot>/<bay> oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd <slot>/<bay> ethernet_controllers phy <port number> api-version or show firmware version all |
IOMD_ETHER_GEIM-4-QSA28_UNSUPPORTED_MODE |
4-Warning |
On SLOT [dec], QSA28 transceiver plugged into port [dec] configured in 40G mode is not supported. Please remove QSA28 from the port or configure the port as 100G. |
QSA28 is supported only on 100G ports. |
INVALID |
Unplug QSA28 from the port or change the port configuration to 100G. |
IOMD_ETHER_GEIM-4-QSA_UNSUPPORTED_MODE |
4-Warning |
On SLOT [dec], QSA transceiver plugged into port [dec] configured in 100G mode is not supported. Please remove QSA from the port or configure the port as 40G. |
QSA is supported only on 40G ports. |
INVALID |
Unplug QSA from the port or change the port configuration to 40G. |
IOMD_ETHER_GEIM-4-REMOVE_XCVR |
4-Warning |
Unplug the transceiver in interface [chars], keeping transceiver can have impact on other transceiver in the same port-group |
Inserting an incompatible transceiver is not recommended since it can have impact on other transceiver in the same port-group |
INVALID |
Unplug the incompatible transceiver |
IOMD_ETHER_GEIM-4-UNSUPPORTED_TRANSCEIVER |
4-Warning |
On SLOT [dec], Transceiver plugged into port [dec] is not supported. Please remove the transceiver. |
It's not recommended to insert unsupported transceivers. |
INVALID |
Unplug the transeiver. |
IOMD_ETHER_GEIM-5-LINK_INCONSISTENCY |
5-Notice |
Inconsistency detected between hardware and software parameters in slot [dec] for ports [chars], restoring the consistency. Link flap or traffic drop might be observed on these ports during this process |
During switchover or ISSU, if the serdes parameters are different in active and standby, these parameters will be reprogrammed. This may result in link flap or traffic drop momentarily |
INVALID |
No action is required |
IOMD_ETHER_GEIM-5-MODULE_REINIT_REQUIRED |
5-Notice |
Hardware parameters on PHY for slot [dec] need modification, Which may have an impact on link and traffic during switchover. User intervention is required to fix the problem by reloading slot [dec]. Use the command 'hw-module subslot [dec]/0 oir power-cycle' to reset the slot during maintainance |
Hardware parameters need to be updated on PHY. Due to hardware limitation these parameters cannot be applied dynamically. For applying these parameters we need reload linecard |
INVALID |
Perform Linecard reload by using below command so that parameter changes get commited to hardware. If this step is not performed then you may face a link flap and traffic loss during switchover Command : hw-module subslot <slot>/0 oir power-cycle |
IOMD_ETHER_GEIM-6-STBY_PORTS_INITIALIZED |
6-Information |
Interfaces on slot [dec] are initialized on standby and ready for switchover |
All the interfaces on standby for particular slot is initialized and Interface are ready for switchover. |
INVALID |
No action is required. |
IOMD_ETHER_GEIM-6-UNSUPPORTED_MODE |
6-Information |
On SLOT [dec] QSFP transceiver plugged into 40G port [dec] and a QSA module plugged into port [dec] is unsupported combination. To linkup the desired connections, please remove QSFP transceiver from port [dec] as well as QSA module from port [dec] and then insert only the required QSFP transceiver or QSA module in the respective port. |
Due to a hardware limitation in PHY, QSFP Optics on top port and QSA module on bottom port is not supported |
INVALID |
Unplug the error disabled transceiver |
IOMD_INFRA-3-I2C_READ |
3-Error |
An I2C read has failed because [chars] |
An I2C read has failed. This could be due to a hardware or software defect. |
asr900-im |
Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
IOMD_INFRA-3-I2C_WRITE |
3-Error |
An I2C write has failed because [chars] |
An I2C write has failed. This could be due to a hardware or software defect. |
asr900-im |
Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
IOMD_INFRA-3-INTR_EVENT |
3-Error |
IOMd fast thread event ([dec]). |
IOMd fast thread event |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-3-INVALID_BAY_NUM |
3-Error |
An invalid bay number is specified in one of the internal APIs. bay=[dec] max_bay=[dec] |
Invalid bay number to find the TDL domain |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-3-INVALID_SLOT_NUM |
3-Error |
An invalid slot number is specified in one of the internal APIs. slot=[dec] max_slot=[dec] |
Invalid slot number to find the TDL domain |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-3-IPCALLOCFAIL |
3-Error |
Failed to allocate IPC buffer [chars] |
The IM failed to allocate a buffer for communication with RSP |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-3-IPCSENDFAIL |
3-Error |
IOMD failed to send a message [chars] reason: [chars] |
IOMD failed to send message to the RP |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-3-LINECARDDIAGSFAILED |
3-Error |
Module [chars] in Slot [dec] failed online diagnostics. Please use 'show post' for more details |
Online Diag has failed. This could be due to a hardware or software defect. |
asr900-im |
Note the time of the error message and examine the logs for errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
IOMD_INFRA-3-SVL_SPEED_MISMATCH |
3-Error |
Speed of SVL Port [dec] in Slot [dec] does not match with other SVL Links. Please take neccessary action. |
Speed of this SVL Link does not match with the speed of other SVL Links This can be due to replacement of a cable with different Speed on SVL port. |
asr900-im |
Please check the operating speed of this SVL Link and the operating speed of the other SVL Links.If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
IOMD_INFRA-4-BADPOINTER |
4-Warning |
Function [chars] detected an invalid [chars] pointer of %08lX, ignoring |
A software error has occurred, this message is displayed when an invalid pointer is detected. |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-4-FAN_ALARM |
4-Warning |
Interface [chars], fan alarm [chars] |
Fan alarm due to temperature |
INVALID |
For MINOR, action is <fill minor action> For MAJOR, action is <fill major action> For CRITICAL, action is <fill critical action> |
IOMD_INFRA-4-INTR_OVER_LIMIT |
4-Warning |
IOMd main thread disabled interrupt for [dec] msec. |
IOMd main thread process disabled interrupt too long |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-4-LC_OIR_REQD |
4-Warning |
Found mismatch between the line card Phy firmware versions bundled in software and programmed in hardware in slot [dec]. To upgrade the Phy firmware to version bundled in software, perform physical OIR of the line card or run the CLI: hw-module subslot [dec]/[dec] oir power-cycle. If ISSU is in progress, firmware upgrade should be done only after the completion of ISSU. To check the firmware versions, use the CLI: show firmware version all |
During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software will not be automatically enabled and needs a manual upgrade via power-cycle of the line card |
INVALID |
To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot <slot>/<bay> oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd <slot>/<bay> ethernet_controllers phy <port number> api-version or show firmware version all |
IOMD_INFRA-6-BEACON_LED_TURNED |
6-Information |
Slot [dec] Port [dec] Beacon LED turned [chars] |
Beacon LED turned ON/OFF. This is a notification message only.No action is required. |
INVALID |
This is a notification message only. No action is required. |
IOMD_INFRA-6-HIGH_POWER_OPTICS_DETECTED |
6-Information |
The port [chars] supports optics with a max power of [dec].[dec] W, but inserted optics max power is [dec].[dec] W. This can lead to operational issues for these and neighbouring ports. To identify allocated port max power, please execute the CLI: [chars] |
Due to a thermal limitation, insertion of High power QSFP/SFP Optics in this port is not suggested. |
INVALID |
Unplug the high power XCVR. |
IOMD_INFRA-6-HIGH_POWER_OPTICS_PRESENT |
6-Information |
The line card [dec] has optic(s) inserted in port(s) that has power limitations. The optics max power is more than the power recommended. This can lead to operational and thermal issues for these and neighbouring ports. To identify allocated port max power, please execute the CLI: [chars] |
Due to a thermal limitation, insertion of High power QSFP/SFP Optics in some ports is not advised. |
INVALID |
Unplug the high power XCVR. |
IOMD_INFRA-6-STBY_PORTS_INITIALIZED |
6-Information |
Interfaces on slot [dec] are initialized on standby and ready for switchover |
All the interfaces on standby for particular slot is initialized and Interface are ready for switchover. |
INVALID |
No action is required. |
IOMD_INFRA-6-TDLMSG_INCOMPATIBLE |
6-Information |
Failed to copy message [chars] to buffer, not allowed for current domain. |
Failure to marshal a message indicates an incompatibility with the intended recipient. |
asr900-im |
Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
IOMD_INFRA-6-UNSUPPORTED_MODE |
6-Information |
Transceiver module in [chars] going in err-disabled state. |
Breakout optics is not supported in non-breakout port; Non-breakout optics is not supported in breakout port |
INVALID |
Unplug the error disabled transceiver |
IOMD_INFRA-6-UNSUPPORTED_MODE_BREAKOUT |
6-Information |
Transceiver module in [chars] going in err-disabled state. |
Breakout optics is not supported in non-breakout port; Non-breakout optics is not supported in breakout port |
INVALID |
Unplug the error disabled transceiver |
IOMD_INFRA-6-UNSUPPORTED_SPEED_COMBINATION |
6-Information |
On SLOT [dec] QSFP 100G/40G transceiver plugged into port [dec] and a QSA module plugged into port [dec] is unsupported combination. To linkup the desired connections, please remove QSFP transceiver from port [dec] as well as QSA module from port [dec] and then insert only the required QSFP transceiver or QSA module in the respective port. |
Due to a hardware limitation in PHY, QSFP Optics on top port and QSA module on bottom port is not supported |
INVALID |
Unplug the error disabled transceiver |
IOMD_STARFLEET-5-LINK_RECOVERY |
5-Notice |
Interface [chars] link recovery mechanism triggered [Reason: System Side Signal down] |
Link recovery mechanism detected a system side signal issue on UADP transmit. Recovery mechanism was triggered for correcting it. |
INVALID |
No action is required. |
IOSD-3-BIPC_REJECT |
3-Error |
Could not accept ipc connection: [chars] |
This error occurs if shell-manager has denied an ipc connection request from IOS. |
iosxe-shellmgr |
Check the connection request parameters. |
IOSD-3-TDL_PROPERTIES |
3-Error |
Could not set message properties for connection: [chars] |
This error occurs if shell-manager is unable to set message properties for the IOS-sman connection |
iosxe-shellmgr |
Check the connection request parameters. |
IOSXE_UPGRADE_ROMMON-0-ROMMON_LOADTEST_FAIL |
0-Emergency |
ROMMON FIPS_140-3 Load test *FAILED*: file [chars] |
FIPS 140-3 Related Load test failed for the ROMmon. |
iosxe-binos-utils |
Check the system messages to see if any messages appeared that might indicate the source of the ROMmon Load test problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative. |
IOSXE_UPGRADE_ROMMON-0-ROMMON_UPGRADE_FAIL |
0-Emergency |
ROMMON upgrade failed: partition [chars] |
An attempt to upgrade the ROMmon failed. |
iosxe-binos-utils |
Check the system messages to see if any messages appeared that might indicate the source of the ROMmon problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative. |
IOXCAF-5-GUESTSHELL_IPV4_NOTICE |
5-Notice |
guestshell ip address([chars]) of Mgmt-Intf is ignored. |
The ipv4 address configured for guestshell's Mgmt-Intf is ignored. When guestshell is on Mgmt-Intf it is natted and has an internal 192.168 ipv4 address. |
polaris-infra |
No action is required |
IOXCAF-5-GUESTSHELL_IPV6_NOTICE |
5-Notice |
guestshell ipv6 address([chars]) of Mgmt-Intf is ignored. |
The ipv6 address configured for guestshell Mgmt-Intf is ignored. When guestshell is on Mgmt-Intf it is natted and has an internal 192.168 ipv4 address. Therefore there is no need to provide a static ipv6 address to guestshell interfaces. |
polaris-infra |
No action is required |
IOXCAF-6-INSTALL_MSG |
6-Information |
app-hosting: [chars] |
Message for installing an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IOXCAF-6-UPGRADE_MSG |
6-Information |
app-hosting: [chars] |
Message for upgrading an app. |
polaris-infra |
In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. |
IOXMGR-2-DNAC_EGRESS_INTF_NOT_SVI |
2-Critical |
Not supported: egress interface ([chars]) towards Cisco-DNAC server [chars] is not an SVI |
Egress interface to reach the Cisco-DNAC server is restricted to be an SVI |
ewlc-iot-gw |
If this message occurs, the egress interface towards the Cisco-DNAC server needs to be configured as an SVI |
IOXMGR-2-DNAC_EGRESS_INTF_NO_GLOB_IPV6_ADDR |
2-Critical |
Cisco-DNAC configured address is IPv6, but no global IPv6 address configured on egress interface [chars] |
At least one local IPv6 global/routable address is needed to reach the Cisco-DNAC server |
ewlc-iot-gw |
If this message occurs, at least one IPv6 global address needs to be configured on the egress interface towards the Cisco-DNAC server. |
IPC_ERRMSG-4-IPC_WARNING_TRACE |
4-Warning |
Warning, [chars] |
General warning message with traceback |
ewlc-app-infra |
LOG_STD_ACTION |
IPC_LOG-3-IPC_LOGWRITE_FAILED |
3-Error |
ipc log write [dec] bytes failed because [chars] |
An internal logging mechanism failed to write a message. |
iosxe-binos-utils |
No action is required. However, if router performance is noticeably degraded, contact Cisco Technical Assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. |
ISSU-0-BOOT_SYNC_FAIL |
0-Emergency |
Problem with sync of ISSU boot state - [chars] |
The ISSU state between two FRUs is not properly synchronized as a result of a boot error. |
iosxe-binos-utils |
This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
ISSU-0-PKG_INCONSIST |
0-Emergency |
Reason: [chars] |
A software consolidated package or sub-package has an error that indicates the sub-package should not be installed or used. |
iosxe-binos-utils |
If this message is received, the desired consolidated package or sub-package should not be used. Upgrade using a different consolidated package or sub-package, and report the problem consolidated package or sub-package to Cisco technical support. |
ISSU-0-PKG_MNT_SCRIPT_FAIL |
0-Emergency |
Package: [chars] |
A consolidated package or sub-package has encountered an error indicating it is not usable. |
iosxe-binos-utils |
Upgrade your software using a different consolidated package or sub-package. |
ISSU-0-RESET_FRU_FAIL |
0-Emergency |
Problem with ISSU reset of remote FRU - [chars] |
After a sub-package installation, one or more FRUs that were upgraded failed to initialize within the timeout period. |
iosxe-binos-utils |
This problem is more likely to occur in routers with larger configurations, so if your router has a large configuration, you may want to wait a few more minutes to see if your hardware initializes. If the hardware continues to not initialize, reset the FRUs which failed to initialize. If resetting the FRUs fails to resolve the issue, gather the output of show tech-support and contact a Cisco technical support representative. |
ISSU-0-SOFTWARE_INVALID |
0-Emergency |
Package for location [chars]: [chars] |
The sub-packages have encountered an error related to the structure of the loaded software. |
iosxe-binos-utils |
This error is likely caused by a failure of the boot or installation process or a corrupted provisioning file. If the system displays error messages related to the boot that can be addressed, address those messages. Downloading new software, if possible, may also help with the problem. If the problem persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
ISSU-3-BOOT_SYNC |
3-Error |
Problem with sync of ISSU boot state - [chars] |
The ISSU state between two FRUs is not properly synchronized as a result of a boot error. |
iosxe-binos-utils |
This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
ISSU-3-BOOT_UNCLEAN |
3-Error |
Found reload log file, moved to [chars] |
A log file was found at bootup indicating that all shutdown tasks were not performed on a previous reload. |
iosxe-binos-utils |
No user action is necessary. The system will automatically resolve most issues related to the shutdown task as part of the bootup procedure. If a problem related to the tasks that did not shutdown occurs, another error message will occur providing information about that problem. |
ISSU-3-INCOMPAT |
3-Error |
The packages in [chars] are not consistent |
The sub-packages specified for running on the chassis are not compatible with one other. |
iosxe-binos-utils |
Install a compatible set of packages to allow normal operation. This will require booting a known-good package set. |
ISSU-3-ISSU_COMP_CHECK_FAILED |
3-Error |
ISSU compatibility check failed for [chars] |
The image is not ISSU compatible |
polaris-issu-infra |
Please add another ISSU compatible image to start ISSU |
ISSU-3-SYNC_ERR |
3-Error |
Problem with sync of state - [chars] |
The software state between two FRUs or switches is not properly synchronized as a result of a boot error. |
iosxe-binos-utils |
This message may appear during certain events, such as during a FRU or switch removal or if the FRU or switch loses connectivity. In most cases, the router will resynchronize the software state between the FRUs or switches without any user intervention. If the software state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
ISSU-3-UCODE_INCOMPAT |
3-Error |
Found mismatch for ucode feature - [chars] |
During boottime microcode feature version check, a version mismatch was found for this feature. |
iosxe-binos-utils |
Please ensure that versions of features in microcode are compatible by provisioning a different set of microcode files. |
ISSU-5-ISSU_AUTO_ROLLBACK |
5-Notice |
ISSU rollback timer expired: initiating rollback |
An ISSU upgrade has been rolled back because the rollback timer has expired. |
iosxe-binos-utils |
No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only. |
ISSU-5-ISSU_STAGE_INFO |
5-Notice |
STAGE [chars]: [chars] [chars]\n |
This message is used to indicate the start/completion of ISSU stages. |
polaris-issu-infra |
No action required. This is an indication that ISSU stage has started or completed |
ISSU-5-ISSU_STATE_INVALID |
5-Notice |
ISSU stored state found invalid and cleaned up: [chars] |
The RP has corrected a failed ISSU install state that was detected at bootup. |
iosxe-binos-utils |
No user action is necessary. This is an informative message indicating that the failed ISSU state has been corrected. |
K to O
Facility-Severity-Mnemonic |
Severity-Meaning |
Message |
Message-Explanation |
Component |
Recommended-Action |
---|---|---|---|---|---|
LA_ACL_ERRMSG-3-ACL_EDIT_ERROR |
3-Error |
Failed to program modified [chars] [chars] [chars] [chars] ACL in hardware. The number of ACEs exceeded hardware limit.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of ACE entries. Delete the ACL first and then modify the acl by reducing number of ACEs and re-configure the ACL on the box.\n |
LA_ACL_ERRMSG-3-ACL_NOT_SUPPORTED |
3-Error |
ACL is not supported on this interface [chars].\n |
Unsupported configuration |
INVALID |
ACL is not supported on this interface %s.Remove the ACL from interface on IOS\n |
LA_ACL_ERRMSG-3-EPC_EOMPLS_ERROR |
3-Error |
EPC is not supported on EOMPLS port. To recover, stop the capture from [chars] interface.\n |
Unsupported configuration |
INVALID |
Stop the capture from %s interface..\n |
LA_ACL_ERRMSG-3-OGACL_EGRESS_ERROR |
3-Error |
OGACL is not supported in egress dir. To recover, Delete [chars] ACL [chars] proto , correct mistake and re-create ACL.\n |
Invalid configuration |
INVALID |
Delete ACL , correct mistake and re-create ACL.\n |
LA_ACL_ERRMSG-4-UNLOADED |
4-Warning |
[chars] [chars] [chars] [chars] ACL on interface [chars] could not be programmed in hardware.Either number of ACLs or number of ACES in acl exceeded hardware limit.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of entries, use a simpler configuration which uses less entries.It can be either number of ACLs or number of ACES in the acl.\n |
LA_ACL_ERRMSG-6-SUB_INTF_BIND_WARNING |
6-Information |
[chars] [chars] [chars] ACL on interface [chars] could not be programmed in hardware. VLAN is not ready in hardware. Once VLAN is ready, ACL will be attached to vlan automatically in hardware.\n |
Invalid configuration. |
INVALID |
VLAN is not ready in hardware.Once VLAN is ready, ACL will be attached to vlan automatically in hardware. Worst case, first detach ACL from sub-interface. Configure vlan on this sub-interface if not already done and then reattach ACL \n |
LA_L2_ERRMSG-3-MCID_EMDB_RSC_ERR |
3-Error |
Failed to allocate replication entry to do flooding for vlan: [dec], vp_if_id: 0x%lx - reason: [chars] |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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. |
LA_L2_MCAST_ERRMSG-3-MCID_EMDB_RSC_ERR |
3-Error |
Failed to allocate replication entry for vlan: [dec], Group: [chars], vp_if_id: 0x%lx - reason: [chars] |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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. |
LA_L2_MCAST_ERRMSG-3-MCID_RSC_ERR |
3-Error |
Failed to allocate mcid for vlan: [dec], Group: [chars] - reason: [chars] |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
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. |
LA_L3TUNNEL_ERRMSG-3-EXIST_ERROR |
3-Error |
Duplicate Tunnel config not supported\n |
Same tunnel source and destination |
INVALID |
Delete the tunnel and move to unique src/dst combination\n |
LA_L3TUNNEL_ERRMSG-3-OOR_ERROR |
3-Error |
Unique 16 sources and 1K Tunnels only supported\n |
Too many tunnels |
INVALID |
Delete unwanted tunnels\n |
LA_L3TUNNEL_ERRMSG-3-TUN_MOD_ERROR |
3-Error |
Please delete the tunnel and recreate it. Set the tunnel mode first and then configure the tunnel src and tunnel destination. Dynamic change to Tunnel mode not allowed.\n |
Dynamic Tunnel mode change not allowed |
INVALID |
Delete Tunnel. Set the correct mode and then configure tunnel src and tunnel dst\n |
LA_L3_ERRMSG-6-UNSUPPORTED_LB |
6-Information |
Mixed Mode of Tunnel and Normal ADJ Unsupported in LB, lbal_obj_id: 0x%x.\n |
Mixed Mode of Tunnel and Normal ADJ is Unsupported in LB. We are printing the lbal_obj_id which is effected |
INVALID |
Normal Adj will be removed from LB if Tunnel is present. Only Tunnel adj will be present for LB |
LA_QOS_ERRMSG-3-LA_QOS_SCH_BANDWIDTH_REMAINING_RATIO_IGNORED |
3-Error |
Ignoring Non-default[Ratio=1], Interface level Bandwidth remaining ratio([dec]) on Main-interface [chars] for policy [chars]. Reason: No support\n |
Interface level(HQOS) Bandwidth remaining ratio is supported only across sub-interface on same main-interface or among main-interface with sub-interface priority propagation mode enabled and its sub-interface. |
bigbang-qos |
No Specific action required. However, for clarity user can consider installing different policy without Bandwidth remaining ratio in parent policy. |
LA_QOS_ERRMSG-3-LA_QOS_TCAM_OOR |
3-Error |
No TCAM availabe to program policy [chars] on interface [chars] on [chars] direction.\n |
TCAM is full on the slice where the interface is on. |
bigbang-qos |
Reduce the number of ACE in the policy. Remove the policy and attach again. |
LA_QOS_ERRMSG-3-LA_QOS_VOQ_CGM_PROFILE_EXHAUSTED |
3-Error |
VOQ Congestion Mangement(CGM) profiles exhausted.\n |
All the available 32 VOQ CGM Profiles have been used up and a new profile creation was attempted |
bigbang-qos |
Check all queueing policies for unique CGM Configuration. See if some can be combined to free some CGM Profiles |
LA_QOS_ERRMSG-4-LA_QOS_SCH_PORT_SHAPER_GREATER_THAN_INTERFACE_SPEED |
4-Warning |
For [chars], User configured port shaper speed[[dec]] is greater than physical port speed [[dec]]. Limiting the same to physical port speed\n |
User configured port shaper in H-QOS policy is higher than physical interface speed. User needs to revisit the policy. |
bigbang-qos |
No Specific action required. However, user needs to revisit the policy. |
LA_SGACL_ERRMSG-3-SGACL_CELL_BIND_ERROR |
3-Error |
SGACL [chars] on cell ([dec] [dec]) is not allowed. SGACL policy of default cell is not allowed to be shared with any other cells \n |
Invalid configuration. |
INVALID |
SGACL policy associated with default cell is non-sharable with other cells. Maintain a separate policy for default permission. \n |
LA_SGACL_ERRMSG-3-SGACL_CELL_MONITOR_WARNING |
3-Error |
This platform supports only one counter per cell. User attached both V4 & V6 policies to cell [[dec], [dec]] but monitor mode is set to only one protocol. This may lead to inaccurate Hw-Deny, HW-Monitor cell counters. There will be no effect on functionality\n |
Invalid configuration. |
INVALID |
Configure monitor mode for both IPv4 & IPV6 \n |
LA_SGACL_ERRMSG-3-SGACL_DEFAULT_CONFIG_ERROR |
3-Error |
TCAM Resource Error. Default permission configuration failed. Delete default sgacl permissib ons, free up some TCAM resources and configure default permission again\n |
Configuration is too big |
INVALID |
Delete sgacl default permissions. Free up some TCAM resources and configure default permissions again\n |
LA_SGACL_ERRMSG-3-SGACL_EDIT_ERROR |
3-Error |
Failed to program modified [chars] [chars] [chars] [chars] ACL in hardware. The number of ACEs exceeded hardware limit.\n |
The configuration is too large. |
INVALID |
You have exceeded the system limit of ACE entries. Delete the ACL first and then modify the acl by reducing number of ACEs and re-configure the ACL on the box.\n |
LISP_AGENT_MESSAGE-3-LISP_AGENT_DB_ERROR |
3-Error |
DB-Error: [chars] |
An internal error occurred due to which unable to update the oper DB records |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REGISTER_MSG_SEND_FAIL |
3-Error |
Error: Failed to send [chars] to MAP Server for [chars]: %02x%02x.%02x%02x.%02x%02x |
An internal error occurred due to which unable to send Map Register message to MAP server |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REGISTRATION_REJECT_MSG |
3-Error |
Error: [chars] %02x%02x.%02x%02x.%02x%02x with rejection code [dec] - [chars], MS IP: [chars], VNID: [chars] |
Received MAP Registration Reject Message |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REPLY_NACK_MSG |
3-Error |
Error: [chars] %02x%02x.%02x%02x.%02x%02x |
Received MAP reply NACK Message |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REQUEST_MSG_SEND_FAIL |
3-Error |
Error: Failed to send [chars] to MAP Server for [chars]: %02x%02x.%02x%02x.%02x%02x |
An internal error occurred due to which unable to send Map Request message to MAP server |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LISP_AGENT_MESSAGE-3-LISP_AGENT_MS_IP_ERROR |
3-Error |
LISP AGENT clear [chars] |
Map Server msg stats not exists error |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LISP_AGENT_MESSAGE-3-LISP_AGENT_RECEIVE_ERROR_NOTIFICATION_MSG |
3-Error |
Error: Received reliable error notification msg with [chars] [dec] |
the Error Notification message received from the MAP Server |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LISP_AGENT_MESSAGE-6-LISP_AGENT_TRANSPORT_MS_CONNECTION |
6-Information |
[chars] with map server IP [chars] |
re-establishment of connection with map server got success |
ewlc-wlss-lisp |
LOG_STD_ACTION |
LI_CORE-2-EGRESS_INTF_NOT_SVI |
2-Critical |
Not supported: egress interface ([chars]) towards LI host [chars] is not an SVI |
Egress interface to reach the LI host is restricted to be an SVI |
ewlc-spwifi |
If this message occurs, the egress interface towards the LI host server needs to be configured as an SVI |
LI_CORE-2-EGRESS_INTF_NO_GLOB_IPV6_ADDR |
2-Critical |
LI host address configured is IPv6, but no global IPv6 address configured on egress interface [chars] |
At least one local IPv6 global/routable address is needed to reach the LI host server |
ewlc-spwifi |
If this message occurs, at least one IPv6 global address needs to be configured on the egress interface towards the LI host server. |
LMLIB_RTU_LICENSE-1-AP_INSUFFICIENT_PERM_APCOUNT |
1-Alert |
APs connected exceed the permanent licenses available by [dec]. |
The number of APs connected is greater than the number of permanent licenses. |
iosxe-fwdmgr |
Purchase adder licenses to add to your existing permanent licenses. |
LMLIB_RTU_LICENSE-1-AP_USAGE_EXCEEDED |
1-Alert |
AP-count license usage has exceeded the available AP-count by [dec]. |
AP-count license usage has exceeded the available AP-count. |
iosxe-fwdmgr |
Remove the excess APs from the controller. |
LMLIB_RTU_LICENSE-1-EVAL_EXP |
1-Alert |
Evaluation period of [chars] license expired [dec] days ago. Purchase a permanent license. |
The evaluation license has expired. |
iosxe-fwdmgr |
Purchase a permanent license. |
LMLIB_RTU_LICENSE-1-EXCESS_AP_LIC |
1-Alert |
Total AP-count licenses available have exceeded the maximum supported AP-count by [dec]. |
The number of AP-count licenses available is greater than the maximum number of supported AP-count. |
iosxe-fwdmgr |
The extra AP-count licenses can be moved to another controller. |
LMLIB_RTU_LICENSE-1-PRIMARY_REMOVED |
1-Alert |
The current stack does not support the applied AP License Count. Reconnect a Catalyst 5760 SKU running valid AP License Count within 90 days. |
AIR-CT5760-HA-K9 does not support the same licensing as AIR-CT5760-HA-K9. So an AIR-CT5760-HA-K9 SKU is needed in the stack to support this licensing. |
iosxe-fwdmgr |
Reconnect a Catalyst 5760 SKU running valid AP License Count within 90 days. |
LMLIB_RTU_LICENSE-1-RTU_DISABLED |
1-Alert |
Cannot proceed. Right-to-use Licensing is diabled. Switch is in Smart Licensing mode. |
RTU functionality is disabled when switch in SL mode. |
iosxe-fwdmgr |
Enable RTU licensing with CLI: no license smart enable. |
LMLIB_RTU_LICENSE-1-SKU_INCOMPAT |
1-Alert |
Both the switches in the stack are AIR-CT5760-HA-K9 SKUs. Replace one of the switches with another Catalyst 5760 SKU running valid AP License Count |
Two AIR-CT5760-HA-K9 SKUs are not supposed to stack. |
iosxe-fwdmgr |
Replace the license mismatch switch with a Catalyst 5760 SKU running valid AP License Count. |
LMLIB_RTU_LICENSE-1-TERM_EXP |
1-Alert |
Subscription term period of [chars] license expired [dec] days ago. Please renew your license. |
The subscription license has expired. |
iosxe-fwdmgr |
Renew your subscription license. |
LMLIB_RTU_LICENSE-3-FILE_ERR |
3-Error |
[chars]: License file update failed. Reapply the configuration. |
Failed to update the license file. |
iosxe-fwdmgr |
Reapply the configuration. |
LMLIB_RTU_LICENSE-3-FILE_READ_ERR |
3-Error |
[chars]: License file read failed. |
Failed to read the license file. |
iosxe-fwdmgr |
Reapply the configuration. |
LMLIB_RTU_LICENSE-4-EVAL_WARN |
4-Warning |
Evaluation period of [chars] license is about to expire in [dec] days. Purchase a permanent license. |
The evaluation license is about to expire. |
iosxe-fwdmgr |
Purchase a permanent license. |
LMLIB_RTU_LICENSE-4-TERM_WARN |
4-Warning |
Subscription term period of [chars] license is about to expire in [dec] days. Please renew your license. |
The subscription license is about to expire. |
iosxe-fwdmgr |
Renew your subscription license. |
LMLIB_RTU_LICENSE-6-AP_ADD |
6-Information |
[dec] adder AP-count licenses are added |
AP-count licenses have been added. |
iosxe-fwdmgr |
More APs can be supported. |
LMLIB_RTU_LICENSE-6-AP_DEL |
6-Information |
[dec] adder AP-count licenses are removed. |
AP-count licenses have been removed. |
iosxe-fwdmgr |
Fewer APs are supported. |
LMLIB_RTU_LICENSE-6-DISABLE_RTU |
6-Information |
[chars]: Right-to-use Licensing is disabled. Switch is in Smart Licensing mode. |
User enables Smart Licensing. |
iosxe-fwdmgr |
Request image license license if needed. |
LMLIB_RTU_LICENSE-6-ENABLE_RTU |
6-Information |
[chars]: Right-to-use Licensing is enabled. Switch is in RTU mode. |
User configures RTU licensing by disabling Smart Licensing. |
iosxe-fwdmgr |
Configure image license and ap count license if needed. |
LMLIB_RTU_LICENSE-6-FACTORY_DEFAULT_ERROR |
6-Information |
Factory Default License File [chars] on [chars]. |
An error occured when trying to create the factory default file. |
iosxe-fwdmgr |
Fix the issue and try again. |
LMLIB_RTU_LICENSE-6-IOSD_LIC_MISMATCH |
6-Information |
Switch #[dec]: Current IOSd runs on [chars] license while RTU active license is [chars]. Please configure RTU license to current IOSd license. |
When customer switches license mode from Smart Licensing to RTU Licensing, current IOSd license might mismatch with RTU active license. |
iosxe-fwdmgr |
Configure RTU license level to current IOSd license. |
LMLIB_RTU_LICENSE-6-LIC_ACT |
6-Information |
[chars] license is activated successfully on [chars]. |
The license level is activated. |
iosxe-fwdmgr |
Reboot the switch to invoke the activated license. |
LMLIB_RTU_LICENSE-6-LIC_ACTVED |
6-Information |
[chars] license was already activated. |
The license level was already activated. |
iosxe-fwdmgr |
Reboot the switch to invoke the activated license. |
LMLIB_RTU_LICENSE-6-LIC_CHANGE |
6-Information |
[chars] reboot license level changed from [chars] to [chars]. Reboot the switch to invoke the new license level. |
Reboot license level has been changed. |
iosxe-fwdmgr |
Reboot the switch to invoke the activated license level. |
LMLIB_RTU_LICENSE-6-LIC_EULA_CLEAR |
6-Information |
EULA for [chars] license has been cleared on [chars]. |
License level has been deactivated. |
iosxe-fwdmgr |
The end user license agreement (EULA) needs to be accepted while activating this license level. |
LMLIB_RTU_LICENSE-6-LIC_EVAL_TO_PERM |
6-Information |
License level upgraded from [chars] [chars] to [chars]; [chars] license is in-use without reboot |
A license has been upgraded to a permanent or subscription license. A reboot is NOT required for the new license level to be effective. |
iosxe-fwdmgr |
No action is required |
LMLIB_RTU_LICENSE-6-LIC_EXPED |
6-Information |
[chars] evaluation license has expired; you cannot activate it again. |
You cannot use an expired evaluatoin license. |
iosxe-fwdmgr |
Purchase a permanent license level or activate another license level. |
LMLIB_RTU_LICENSE-6-LIC_IMAGE_INVALID |
6-Information |
Switch #[dec]: The license boot level string is invalid. Boot up with the highest activated license. |
The license boot level string is invalid. The RTU highest activated license is used. |
iosxe-fwdmgr |
Use 'license boot level' to configure a valid license level |
LMLIB_RTU_LICENSE-6-LIC_INCOMPAT |
6-Information |
Switch [dec] has an incompatible license level. Activate a compatible license on the switch so that the switch can join the stack. |
The added switch has an incompatible license level. |
iosxe-fwdmgr |
Activate a new license and reboot the switch. |
LMLIB_RTU_LICENSE-6-LIC_INVALID_DEACT |
6-Information |
[chars] license is not active on [chars]; therefore, it cannot be deactivated. |
The license level is not activated. |
iosxe-fwdmgr |
No need to deactivate this license. |
LMLIB_RTU_LICENSE-6-PLAT_INCOMPAT |
6-Information |
Switch [dec] has an incompatible platform level. Activate a compatible platform on the switch so that the switch can join the stack. |
The added switch has an incompatible platform level. |
iosxe-fwdmgr |
Run in compatible scaled mode and reboot the switch. |
LMRP-0-CHASFS_LOCATION_TRANSLATE |
0-Emergency |
Failed to translate a location to a chasfs object name because [chars] |
The license manager failed to translate a location to a chasfs object name. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASFS_OBJECT_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] because [chars] |
The hardware failed to create a chassis filesystem object. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASFS_OBJECT_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] not present. |
A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASFS_OBJECT_WATCH |
0-Emergency |
Failed to watch chassis filesystem object [chars] because [chars] |
A chassis filesystem object was not watched because of the reason stated in the error message. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASFS_PROPERTY_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly created. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASFS_PROPERTY_GET |
0-Emergency |
Failed to read chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly read by the system. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASFS_PROPERTY_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] property [chars] not present. |
A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASFS_PROPERTY_SET |
0-Emergency |
Failed to write chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property failed to write. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASSIS_STATUS |
0-Emergency |
Failed to get chassis hardware status because [chars] |
The system failed to get the chassis hardware status. |
iosxe-csl |
Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-CHASSIS_TYPE |
0-Emergency |
The chassis type [chars] is invalid. |
The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-csl |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-INVALID_ARGUMENT |
0-Emergency |
A system function was given an invalid argument. |
A system function was given an invalid argument. This is due to a software defect. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-IPC_CONNECTION_INVALID |
0-Emergency |
An IPC connection has invalid state. |
An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-IPC_CONNECT_MASTER |
0-Emergency |
IPC connection to the active RP failed because [chars] |
IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-IPC_INITIALIZATION |
0-Emergency |
IPC initialization failed because [chars] |
IPC initialization failed. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-MESSAGE_REGISTER |
0-Emergency |
Failed to register with active RP because [chars] |
The active RP failed to register. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-MESSAGE_RELAY |
0-Emergency |
Failed to relay a message because [chars] |
Failed to relay a message. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-MESSAGE_RESPONSE |
0-Emergency |
An invalid message response was received because [chars] |
An invalid message response was received. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-MQIPC_ADVANCE |
0-Emergency |
Failed to advance MQIPC queue because [chars] |
The MQIPC initialization failed. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-MQIPC_INITIALIZATION |
0-Emergency |
MQIPC initialization failed because [chars] |
MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-PEER_TABLE |
0-Emergency |
A peer table initialization or maintenance function failed because [chars] |
A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-PLATFORM_FAMILY_TYPE |
0-Emergency |
The platform family type [chars] is invalid. |
The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. |
iosxe-csl |
Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-RESOLVE_FRU |
0-Emergency |
Failed to determine [chars] card because [chars] |
The router failed to determine a FRU state. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-SERVICES_INITIALIZATION |
0-Emergency |
Failed to initialize general application services because [chars] |
The system failed to initialize application services. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-SIGNAL_INITIALIZATION |
0-Emergency |
Failed to initialize signals because [chars] |
The system failed to initialize signals. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-SLOTS_INITIALIZATION |
0-Emergency |
Failed to initialize chassis slot information because [chars] |
The system failed to initialize the chassis slot information. |
iosxe-csl |
Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-SLOT_INVALID |
0-Emergency |
A card absolute slot number cannot be determined for this chassis type |
An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content. |
iosxe-csl |
Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-0-UIPEER_CREATE |
0-Emergency |
Failed to create user interface peer. |
The system failed to create a user interface peer. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-3-CHASFS_OBJECT_DESTROY |
3-Error |
Failed to destroy chassis filesystem object [chars] because [chars] |
A chassis filesystem object that should have been destroyed was not destroyed. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-3-CHASFS_PROPERTY_DESTROY |
3-Error |
Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] |
A chassis filesystem property that should have been destroyed was not destroyed. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-3-LICENSE_SERVICE_SETUP |
3-Error |
Failed to setup the licensing proxy service |
License Manager failed to set itself up as a proxy for licensable features. |
iosxe-csl |
Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-3-PEER_INVALID |
3-Error |
A peer table entry has invalid state. |
A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion. |
iosxe-csl |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
LMRP-3-RTU_UNINITIALIZED |
3-Error |
RTU not yet initialized: stack enabled [dec] |
License manager has not initialized RTU, but manager got RTU enable/disable request |
iosxe-csl |
No user action is necessary. Reloading might work |
LMRP-3-THROUGHPUT_LICENSE_APPLY_FAILED |
3-Error |
Throughput license look-up failed due to '[chars]' |
This message is to notify the user that a license look-up did not succeed because license manager process could not be contacted. This is a rare case but is due to either a crashed license daemon(licensed) or it encountered an internal error. |
iosxe-csl |
No user action is necessary. However, it is possible that a re-boot of the box may correct this behavior. |
LMRP-3-UDI_AUTH |
3-Error |
Quack Unique Device Identifier authentication failed |
This chassis seems to be compromised or tampered with. UDI burned on to the Quack chip and the one read from chassis EEPROM do not match. It can also be a case of either EEPROM or Quack device failure. More details about which specific field failed to match are logged in license daemon log file (licensed_R0.log). |
iosxe-csl |
User immediately needs to contact Cisco support. This device appears to be tampered with or is a counterfeit device or had a system failure. |
LMRP-6-THROUGHPUT_LICENSE |
6-Information |
Throughput license [chars], throughput set to [chars] |
Status indicating whether throughput license is found and the corresponding througput the CPP hardware is configured to provide. |
iosxe-csl |
No user action is necessary. This is an informational message indicating throughput configured. |
LOADBALANCE_TRACE_MESSAGE-3-AP_SW_UPDATE_ERR_LOG_MSG |
3-Error |
AP SW update [chars] |
AP Software Update logging |
ewlc-ap |
AP software update failed. ISSU image upgrade or SMU patching could be aborted. The user needs to initiate ISSU upgrade/SMU patch again. If the error occured during manual operation, operation can be initiated again |
LOADBALANCE_TRACE_MESSAGE-5-AP_SW_UPDATE_LOG_MSG |
5-Notice |
AP SW update [chars] |
AP Software Update logging |
ewlc-ap |
No action required |
LOADBALANCE_TRACE_MESSAGE-5-LB_LOG_MSG |
5-Notice |
Loadbalancer Log : [chars] |
Generic loadbalancer message |
ewlc-ap |
No action required |
LOADBALANCE_TRACE_MESSAGE-5-LB_NOTICE_MSG |
5-Notice |
Loadbalancer : [chars] |
Loadbalancer informational message |
ewlc-app-infra |
LOG_STD_ACTION |
LUA_VM-2-INITIALIZATION |
2-Critical |
Cannot initialize the Lua Virtual Machine |
The Lua Virtual Machine is a critical component of the shell-manager process. It is used to render responses to user commands. If this component cannot be initialized then the shell-manager will be unable to process any commands directed at the IOS-XE daemons. |
iosxe-shellmgr |
The shell-manager process could not be started. Check the trace log files for more details as to why the virtual machine failed to initialize correctly. This may be an out of memory condition so rebooting the chassis may resolve the problem. |
MAB-5-FAIL |
5-Notice |
Authentication failed for client ([chars]) with reason ([chars]) on Interface [chars] AuditSessionID [chars] |
MAB Authentication was unsuccessful. |
polaris-smd |
No action is required. |
MAB-5-RESULT_OVERRIDE |
5-Notice |
Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars] |
Authentication result was overridden |
polaris-smd |
No action is required. |
MAB-5-SUCCESS |
5-Notice |
Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars] |
MAB Authentication was successful. |
polaris-smd |
No action is required. |
MATM-3-CONSISTENCY_CHECK_RESULT |
3-Error |
No Inconsistency detected for Address %02x:%02x:%02x:%02x:%02x:%02x, vlan [dec] |
Consistency checker execution completed |
polaris-l2 |
No Inconsistency detected |
MATM-3-HWERROR |
3-Error |
Hardware [chars] failed |
A hardware API access error message occurred. |
polaris-l2 |
Find out more about the error by using the commands show platform matm recon_state and show tech-support 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. |
MATM-3-INVALID_EVENT |
3-Error |
An invalid event :[dec] received in [chars], expected event:[dec] |
MATM feature received invalid event on it's event handler |
polaris-l2 |
The condition is being recovered, no action is required |
MATM-3-MAC_INCONSISTENCY |
3-Error |
Inconsistency detected: Address :%02x:%02x:%02x:%02x:%02x:%02x, Vlan [dec] |
There is a difference between mac address entry in software and hardware |
polaris-l2 |
Try clearing the mac or run recovery mechanism |
MATM-3-MAX_ENTRIES |
3-Error |
The maximum number of MAC addresses has been reached:[dec] |
The maximum number of MAC entries that can be programmed has been reached. |
polaris-l2 |
New MAC addresses will not be learned. Stop any redundant MAC incrementing traffic for extra streams. |
MATM-3-RECONCILIATION |
3-Error |
Reconciliation post switchover failed : [chars] |
Consistency check across modules shows inconsistency in data. |
polaris-l2 |
Find out more about the error by using the commands show platform matm recon_state and show tech-support 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. |
MCAST_ERROR_MESSAGE-3-MCAST_AVL_DB_MISMATCH |
3-Error |
DB Mismatch: [chars] |
Previous joins and leaves have corrupted the database. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_CLIENT_DATA_ERR |
3-Error |
Client %02X%02X.%02X%02X.%02X%02X multicast data is NULL. |
Internal multicast database client entry should contain multicast data when a multicast join request comes from below service layer |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_CLIENT_ENTRY_ERR |
3-Error |
Client %02X%02X.%02X%02X.%02X%02X does not exist in internal database. |
internal multicast database must contain the client entry when a multicast join request comes from below service layer |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_CLNT_ENT_ERR |
3-Error |
(S,G) count is zero whereas multicast data of client %02X%02X.%02X%02X.%02X%02X is not NULL |
when client disassociates (S,G) count is zero but client's multicast entry is not NULL. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_CLTMAC_LOOKUP_ERR |
3-Error |
Mismatch between two database while [chars] mgid = [dec] client mac = %02X%02X.%02X%02X.%02X%02X |
Two different databases have different values for the client. Multicast functionality will be affected due to mismatch of database values. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_DETELE_AVL_MGID |
3-Error |
Deletion of mgid [dec] from internal multicast databases failed |
Mgid entry deletion from the internal database fails |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_GRP_JOIN_LEAVE_FAILED |
3-Error |
[chars] for client %02X%02X.%02X%02X.%02X%02X multicast group [chars], mgid [dec] |
Failure occurred while handling multicast group join or leave. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_INSERT_MGID_FAIL |
3-Error |
insertion of mgid into database failed for some unknown reason - for source [chars] - group [chars] - vlan [dec] |
Internal multicast database corrupted. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_IP_MISMATCH |
3-Error |
[chars] IP Value already inserted for mgid [dec] mismatches. saved value [chars] expected [chars] |
the IP of the stored database and incoming database mismatches |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_MGID_CLIENT_TREE_DESTROY_FAIL |
3-Error |
Mgid [dec] client tree destroy in internal multicast database failed |
Mgid client tree destroy in internal database failed |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_MGID_CLIENT_TREE_WALK_FAIL |
3-Error |
Mgid [dec] client tree walk in internal multicast database failed |
Mgid client tree walk in internal database failed |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_MGID_DATA_MISMATCH |
3-Error |
There is some data mismatch between two databases for mgid [dec]. |
some database in multicast code is having unexpected null data |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_MGID_MISMATCH |
3-Error |
mgid value mismatch in database value found [dec] - expected mgid [dec] |
the stored mgid value in the database is not same as expected. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_MGID_NULL_DATA |
3-Error |
multicast database is having unexpected [chars] NULL value for mgid [dec] |
some database in multicast code is having unexpected null data |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_MGID_SGV_DATA_MISMATCH |
3-Error |
There is some data mismatch between two databases for source [chars] group [chars] vlan [dec] mgid [dec] |
some database in multicast code is having unexpected null data |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_MOBILITY_HANDOFF_FAILED |
3-Error |
[chars] [chars] mobility multicast handoff for client %02X%02X.%02X%02X.%02X%02X |
Failure occurred while handling mobility multicast handoff. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_SG_MAXMGID_ERR |
3-Error |
Multicast group count [dec] is greater than maximum mgids [dec] per client for client %02X%02X.%02X%02X.%02X%02X |
This and further new mgid entries for this client will be ignored Multicast functionality will be affected for those mgids. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_SG_NONZERO_ERR |
3-Error |
[chars] (S,G) count [dec] is greater than zero whereas client %02X%02X.%02X%02X.%02X%02X multicast data is NULL |
Two different databases have different values for the client. Multicast functionality will be affected due to mismatch of database values. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-MCAST_SPAM_UPDATE_FAILED |
3-Error |
[chars] for mgid type [dec], client %02X%02X.%02X%02X.%02X%02X multicast group info [chars] to AP %02X%02X.%02X%02X.%02X%02X |
Failure occurred while sending multicast info to AP. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-3-TASK_CREATE_ERR |
3-Error |
ERROR: Failed to create client-multicast library |
An internal error occurred due to which the client multicast subsystem could not be initialized. APs may not be able to join the controller. |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-4-MCAST_MOM_NOT_CONFIGURED_ON_MOM_ONLY_PLATFORM |
4-Warning |
Multicast-over-Multicast (wireless multicast <ipv4Addr>/ipv6 <ipv6Addr>) is not configured on Multicast-over-Multicast Only platform. Wireless multicast will not work until MOM is configured |
Wireless multicast is configured without MOM on MOM-Only platform |
ewlc-multicast |
LOG_STD_ACTION |
MCAST_ERROR_MESSAGE-6-MCAST_MOM_CONFIG_CHANGE |
6-Information |
Capwap multicast mode [chars] [chars]. IPv4 [[chars]:[chars]] and IPv6 [[chars]:[chars]] with Wireless multicast status [chars]. [chars] |
Wireless capwap multicast mode changed |
ewlc-multicast |
LOG_STD_ACTION |
MCP_SYS-0-ASSERTION_FAILED |
0-Emergency |
Assertion failed: [chars] |
An internal state consistency check failed.Correct operation cannot be guaranteed, and the system has been halted. |
INVALID |
LOG_STD_ACTION |
MDNS_SYSLOG-3-EXCESS_SERVICE |
3-Error |
number of responses([dec]) for query ([chars]) is limited to ([dec]) due to query response threshold |
An MDNS Service Query resulted in too many services in the response, user experience for MDNS may be suboptimal. This may also consume more CPU cycles |
mdns-binos |
Check the service policy configuration and consider moving to a more restrictive location if the problem persists |
MDNS_SYSLOG-3-EXCESS_SERVICE_WIDE_AREA_BONJOUR |
3-Error |
Number of services in the response ([dec]) for query [chars] has exceeded threshold [dec] |
An MDNS Service Query resulted in too many services in the response, user experience for MDNS may be suboptimal and may take up more CPU |
mdns-binos |
re-check the service policy on the Wide area bonjour side and Controller. Move to more restrictive location filter if problem persists |
MDR-3-NODE_ISSU_SIP_WAIT |
3-Error |
Could not wait for [chars] to complete Minimal Disruptive Restart |
An unexpected error has occured where the specified linecard was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This linecard was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-NODE_ISSU_SPA_WAIT |
3-Error |
Could not wait for [chars] in [chars] to complete Minimal Disruptive Restart |
An unexpected error has occured where the specified module was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This module was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-NO_ACTIVE_ESP |
3-Error |
No active ESP was found when initiating Minimal Disruptive Restart |
An unexpected error has occured where no active ESP was found to continue forwarinding traffic during the Minimal Disruptive Restart. All requested linecards and or modules were reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR. |
MDR-3-NO_SPAS_IN_SIP |
3-Error |
No Minimal Disruptive Restart compatible SPAs found in [chars] |
An unexpected error has occured where the specified linecard that was to undergo Minimal Disruptive Restart did not contain any compatible SPAs. This linecard was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-READ_COMPAT_INFO |
3-Error |
Failed to read valid Minimal Disruptive Restart compatibility information for [chars] |
An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however valid compatibility information could not be read prior to commencing Minimal Disruptive Restart. If the linecard itself was to go through Minimal Disruptive Restart, it and the modules within it were reset as normal. If only modules were going through Minimal Disruptuve Restart, all modules were reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors. |
MDR-3-READ_SIP_RESET |
3-Error |
Failed to read a valid Minimal Disruptive Restart reset value for [chars] |
An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however a valid SIP reset value could not be read. This linecard was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors. |
MDR-3-RESTART_FAILED |
3-Error |
Failed to perform Minimal Disruptive Restart on [chars] |
An unexpected error has occured where the specified linecard or module failed to undergo a Minimal Disruptive Restart. This linecard or module was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors. |
MDR-3-SIP_OFFLINE |
3-Error |
[chars] is not online to perform Minimal Disruptive Restart |
An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not found to be online. The linecard was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR. |
MDR-3-SOFTWARE_TRANSFER |
3-Error |
Failed to receive upgrade software for [chars] |
An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not able to receive the upgrade software prior to commencing Minimal Disruptive Restart. The linecard was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors. |
MDR-3-SPA_BAY_INVALID |
3-Error |
Could not perform Minimal Disruptive Restart on invalid [chars] in [chars] |
An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was invalid. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-SPA_IS_NOT_READY |
3-Error |
[chars] in [chars] is not ready to perform Minimal Disruptive Restart |
An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready. The module was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-SPA_NOT_FOUND |
3-Error |
[chars] in [chars] could not be found to perform Minimal Disruptive Restart |
An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found. The module was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-SPA_OFFLINE |
3-Error |
[chars] in [chars] is not online to perform Minimal Disruptive Restart |
An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be online. The module was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-SPA_TYPE_MISMATCH |
3-Error |
Could not perform Minimal Disruptive Restart on [chars] in [chars] due to a SPA type mismatch |
An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module's SPA type was found to be different to what was expected. The module was reset as normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-3-SPA_WAS_NOT_READY |
3-Error |
[chars] in [chars] was not ready to perform Minimal Disruptive Restart |
An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready at the time it was checked. The module was reset was normal. |
iosxe-binos-utils |
Review the IOSd, RP and CC chassis manager logs for errors or module OIR. |
MDR-5-CARD_RESTART |
5-Notice |
Minimal Disruptive Restart [chars] to acquire provisioned software |
The FRU specified was not running the currently provisioned software, which it will acquire on Minimal Disruptive Restart. |
iosxe-binos-utils |
No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. |
MDR-5-SIP_UNSUPPORTED |
5-Notice |
[chars] does not support Minimal Disruptive Restart |
The linecard specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or there are no SPA's that support Minimal Disruptive Restart inserted. This linecard was reset as normal. |
iosxe-binos-utils |
No user action is necessary. |
MDR-5-SPA_UNSUPPORTED |
5-Notice |
[chars] does not support Minimal Disruptive Restart |
The module specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or software version. This module was reset as normal. |
iosxe-binos-utils |
No user action is necessary. |
MDT_CONNECTION-6-STATE_CHANGED |
6-Information |
Connection state changed (id [chars] - [chars]): [chars] |
The connection state has been changed. |
polaris-mdt-infra |
Notification for connection state changed. No action required. |
MDT_SUBSCRIPTION-4-EXCEEDED_ACTIVE_SUB_LIMIT |
4-Warning |
Active subscription limit exceeded (stream [chars], id [chars], client [chars]): [chars] |
The specified subcription will not be connected due to exceeding the maximum number of active subscriptions on this platform. |
polaris-mdt-infra |
Reduce the number of active subscriptions by either removing configured subscriptions or terminating dynamic subscriptions that are not needed. |
MDT_SUBSCRIPTION-4-INVALID_ARGUMENTS |
4-Warning |
Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] |
The value of the given parameter is invalid or not specified. |
polaris-mdt-infra |
Correct the invalid parameter and try the subscription again. |
MDT_SUBSCRIPTION-4-NOT_SUPPORTED |
4-Warning |
Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] |
The value of the given parameter is not supported. |
polaris-mdt-infra |
Try the subscription again with a supported value. |
MDT_SUBSCRIPTION-4-OUTSIDE_LIMIT |
4-Warning |
Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] |
The value of the parameter is outside of the allowable range. |
polaris-mdt-infra |
Try the subscription again with a value within the allowable range. |
MDT_SUBSCRIPTION-4-RESUMED |
4-Warning |
Subscription resumed (stream [chars], id [chars], client [chars]): [chars] |
The specified subscription was resumed from run-time error. |
polaris-mdt-infra |
Try to slow down the data source or check if the connection is stable. |
MDT_SUBSCRIPTION-4-TERMINATED |
4-Warning |
Subscription terminated (stream [chars], id [chars], filter [chars], client [chars]): [chars] |
The specified subscription was terminated due to run-time error. |
polaris-mdt-infra |
Try the subscription again |
MDT_SUBSCRIPTION-4-XPATH_INVALID |
4-Warning |
Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] |
The specified XPath filter is invalid. |
polaris-mdt-infra |
Correct the XPath filter and try the subscription again. |
MERAKI_MGRD-3-MERAKI_INTFC_SETUP_ERR |
3-Error |
Meraki interface setup error: [dec] |
Initial meraki interface setup failed - cannot bringup config updater |
polaris-aurora |
Retry reconfiguring service meraki connect |
MERAKI_MGRD-5-CONFIG_MONITOR_ERR |
5-Notice |
Config Monitor ERR: [chars] |
Config monitor err message |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-CONFIG_MONITOR_NOTIF |
5-Notice |
Config Monitor: [chars] |
Config monitor message |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-CONFIG_UPDATER_ERR |
5-Notice |
Config Updater ERR: [chars] |
Config Updater err message |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-CONFIG_UPDATER_NOTIF |
5-Notice |
Config Updater: [chars] |
Config Updater message |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-CURL_FETCH_ERR |
5-Notice |
Curl Fetch ERR: [chars] |
Curl Fetch error message |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-MERAKI_FSM_START_FAILED |
5-Notice |
Meraki FSM failed to start |
Meraki mgrd FSM failed to start |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-MERAKI_RESET_NOTIFICATION |
5-Notice |
: Reset Notification [chars] |
Reset recovery message |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-MERAKI_RESET_RECOVERY |
5-Notice |
: Reset recovery [chars] |
Reset recovery message |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-PRI_TUNNEL_STATE |
5-Notice |
Primary Tunnel State: [chars] |
Primary tunnel state change notification |
polaris-aurora |
No action is required |
MERAKI_MGRD-5-SEC_TUNNEL_STATE |
5-Notice |
Secondary Tunnel State: [chars] |
Secondary tunnel state change notification |
polaris-aurora |
No action is required |
MERAKI_NCMD-5-NODE_CERT_RENEW_STATE |
5-Notice |
Node Cert Renew State: [chars] |
Node Cert renew state change notification |
polaris-aurora |
No action is required |
MERAKI_NCMD-5-NODE_CERT_STATE |
5-Notice |
Node Cert State: [chars] |
Node Cert state change notification |
polaris-aurora |
No action is required |
MERAKI_NCMD-5-NODE_CLOUD_ID_STATE |
5-Notice |
Node Cloud_ID State: [chars] |
Node Cloud_ID state change notification |
polaris-aurora |
No action is required |
MERAKI_NCMD-5-NODE_TOKEN_STATE |
5-Notice |
Node Token State: [chars] |
Node Token state change notification |
polaris-aurora |
No action is required |
MESH_DB_TRACE_MESSAGE-3-EWLC_MESH_DB_EXEC_MSG |
3-Error |
%% Error: [chars] |
Improper arguments or config |
iosxe-binos-utils |
Arguments to be changed |
MESH_DB_TRACE_MESSAGE-6-EWLC_MESH_DB_INFO_MSG |
6-Information |
%% Info: [chars] |
Info level logs |
iosxe-binos-utils |
No action required |
MESH_TRACE_MESSAGE-3-EWLC_MESH_AP_DISCONNECT_MSG |
3-Error |
%% Error: [chars] |
Failed to Disconnect AP for Mesh config changes |
iosxe-binos-utils |
Reboot the AP for the mesh configs to be applied |
MESH_TRACE_MESSAGE-3-EWLC_MESH_AP_RESET_MSG |
3-Error |
%% Error: [chars] |
Failed to reboot AP for Mesh config changes |
iosxe-binos-utils |
Reboot the AP for the mesh configs to be applied |
MESH_TRACE_MESSAGE-3-EWLC_MESH_EXEC_MSG |
3-Error |
%% Error: [chars] |
Improper arguments or config |
iosxe-binos-utils |
Arguments to be changed |
MESH_TRACE_MESSAGE-3-EWLC_MESH_PROFILE_CHANGE_MSG |
3-Error |
%% Error: [chars] |
Mesh profile change for AP did not get Applied |
iosxe-binos-utils |
Reboot the AP for the mesh configs to be applied |
MESH_TRACE_MESSAGE-4-EWLC_MESH_DCA_INTERVAL_MSG |
4-Warning |
DCA interval is too long. Configure it to 10min to make sure algorithm will run |
The DCA algorithm might not run during that channel update period |
iosxe-binos-utils |
Configure DCA interval to a 10min period to make sure that the algorithm will run |
ME_APMGR_TRACE_MESSAGE-2-EWC_APMGR_CFG_SYNC_FAIL |
2-Critical |
Failed to synchronize configuration to EWC-capable APs on the network |
Failed to synchronize configuration to EWC-capable APs on the network |
ewcap-image |
A switchover to the standby followed by reconfiguration is recommended. |
ME_APMGR_TRACE_MESSAGE-6-EWC_APMGR_RESET |
6-Information |
AP Event: Controller Image Download is successful, reset AP mac [chars] |
Controller Image Download is successful, reset AP |
ewcap-image |
LOG_STD_NO_ACTION |
MMIF_LOG-2-WLAN_CRIT_ERR |
2-Critical |
WLAN Error : [chars] |
Critical issue seen with WLAN config. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. |
ewlc-mobility |
Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. |
MMIF_LOG-3-BUFF_ALLOC_FAILED |
3-Error |
Failed to allocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MMIF_LOG-3-BUFF_DEALLOC_FAILED |
3-Error |
Failed to deallocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MMIF_LOG-3-MSG_PAYLOAD_ALLOCATE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot allocate [chars] for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MMIF_LOG-3-MSG_PAYLOAD_BUILD_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot build [chars] for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MMIF_LOG-3-MSG_PAYLOAD_BUILD_GENERAL_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Failed to build [chars]: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MMIF_LOG-3-MSG_PAYLOAD_PROCESS_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot process [chars] for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MMIF_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: [chars] received is missing payload [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MMIF_LOG-4-ANCHOR_RESP_LOCAL_DELETE |
4-Warning |
Export anchor required but internal error occurred (e.g.: out of resources), sending export anchor deny for: Wlan-Profile: [chars], Policy Profile: [chars], client mac: %02x:%02x:%02x:%02x:%02x:%02x |
Export anchor required but internal error occurred (e.g.: out of resources) |
ewlc-guest |
If this message occurs, it implies that internal error occurred and needs further debugging. |
MMIF_LOG-4-ANCHOR_RESP_PROFILE_MISMATCH |
4-Warning |
Export anchor required but config is incorrect, sending export anchor deny mismatch for: Wlan-Profile: [chars], Policy Profile: [chars], client mac: %02x:%02x:%02x:%02x:%02x:%02x |
Export anchor required but config is incorrect: sending export anchor deny mismatch |
ewlc-guest |
If this message occurs, it implies that configuration should be checked for wlan and policy profile |
MMIF_LOG-7-MSG_PAYLOAD_SIZE_ERROR |
7-Debug |
The payload size has exceeded the limit. [chars] |
Available buffer cannot hold IPV6 NDP pkt payload. |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_APLIST_LOG-3-APENTRY_DEL_FAILED |
3-Error |
Could not delete an AP from the AP list. |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_APLIST_LOG-3-INVALID_APLISTUPD_RECVD |
3-Error |
Received an invalid ap-list-update from [chars]. Entries: [dec], Expected: [dec]. [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_APLIST_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR |
3-Error |
[chars] message received is missing payload [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_APLIST_LOG-4-APENTRY_ADD_FAILED |
4-Warning |
Unable to create an ApList entry for AP %02x%02x.%02x%02x.%02x%02x. ApList table is full |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-0-MOBILITY_TASK_FAILED_TO_START |
0-Emergency |
[chars] task could not be started. The system will be rebooted |
LOG_EXPL_SYSERR |
ewlc-mobility |
The mobility services failed to start correctly |
MM_INFRA_LOG-0-MSG_RECV_FAILED |
0-Emergency |
[chars]: msg revd failed |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-0-QUEUE_CREATE_FAILED |
0-Emergency |
[chars]: queue creation failed |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-1-MOBILITYUSER_STATECREATE_FAILED |
1-Alert |
Unable to create mobility state for user [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-1-USER_NOT_ALLOWED |
1-Alert |
Unable to allow user [chars] into the system. [chars] |
Unable to allow the user into the system for the reported reason |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_INFRA_LOG-2-INIT_FAILED |
2-Critical |
Error while initializing mobility daemon. [chars] |
Error while initializing mobility daemon |
ewlc-mobility |
If this error is seen, it is recommended that the controller's mobility configuration be redone as it may have been lost. If you still require assistance, open a case with the Technical Assistance Center via the Internet or contact your Cisco technical support |
MM_INFRA_LOG-3-BUFF_ALLOC_FAILED |
3-Error |
Failed to allocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-BUFF_DEALLOC_FAILED |
3-Error |
Failed to deallocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-CONFIGDOWNLOAD_FAILED |
3-Error |
Failed to send a config download [chars] paket to [dec].[dec].[dec].[dec] |
Failed to send a configdownload packet |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-DGRAM_SEND_FAILED |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Unable to send [chars] to [chars]. |
Unable to send a mobility packet |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-INVALID_PKT_RECVD |
3-Error |
Received an invalid packet from source endpoint: [chars]. [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
Please check mobility configuration to see if it needs correction. If the problem persists, open a case with the TAC via the Internet action, or contact your Cisco technical support representative and provide the representative with the gathered information. |
MM_INFRA_LOG-3-MSG_PAYLOAD_ALLOCATE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot allocate [chars] for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PAYLOAD_BUILD_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot build [chars] for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PAYLOAD_BUILD_GENERAL_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Failed to build [chars]: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PAYLOAD_DECODE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: [chars] cannot decode mobility payload/s for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PAYLOAD_ENCODE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: [chars] cannot encode mobility payload/s for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PAYLOAD_PROCESS_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot process [chars] for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: [chars] received is missing payload [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PROC_FAILED |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Unable to process the received mobility message [chars] from [chars]. reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PROC_FAILED_GROUP_NAME_HASH |
3-Error |
Pkt group name hash: [chars] Peer group name hash: [chars] [chars]. reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_PROC_FAILED_MAC_ADDR |
3-Error |
Pkt MAC: %02x%02x.%02x%02x.%02x%02x Peer MAC: %02x%02x.%02x%02x.%02x%02x [chars]. reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-MSG_TIMER_ERROR |
3-Error |
Timer error: failed to [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-RECV_FAILED |
3-Error |
Unable to receive mobility message [chars] from [chars]. reason: [chars] |
Unable to receive a mobility packet |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-3-SEND_FAILED |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Unable to send [chars] to [chars]. Reason: [chars]. |
Unable to send a mobility packet |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-4-MOBILITY_OUTGOING_MSG_ERROR |
4-Warning |
Invalid outgoing msg |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_INFRA_LOG-7-MSG_PAYLOAD_SIZE_ERROR |
7-Debug |
The payload size has exceeded the limit. [chars] |
Available buffer cannot hold IPV6 NDP pkt payload. |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_INFRA_LOG-7-MSG_PROC_UNEXISTING_CLIENT |
7-Debug |
%02x%02x.%02x%02x.%02x%02x: Unable to process the received mobility message [chars] from [chars]. reason: [chars] |
LOG_STD_NO_ACTION |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_LOG-2-MAX_SUPPORTED_CLIENTS_90PCT_EXCEEDED |
2-Critical |
90%% ([dec]) of maximum supported number of joined client [dec] exceeded |
Exceeded 90% of maximum supported client join limit |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_LOG-2-MAX_SUPPORTED_CLIENTS_EXCEEDED |
2-Critical |
Maximum supported number of joined clients [dec] exceeded |
Maximum supported number of joined clients exceeded. |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_LOG-3-ANCHOR_GENERIC_ERR |
3-Error |
Anchor: [chars]. client mac: %02x:%02x:%02x:%02x:%02x:%02x |
Anchor has detected and error. |
ewlc-guest |
LOG_STD_RECUR_ACTION |
MM_LOG-3-BUFF_ALLOC_FAILED |
3-Error |
Failed to allocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-BUFF_DEALLOC_FAILED |
3-Error |
Failed to deallocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MIP_READ_ERROR |
3-Error |
[chars]. Encountered memory error, please report the error if you experience a crash. |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MSG_PAYLOAD_ALLOCATE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot allocate [chars] for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MSG_PAYLOAD_BUILD_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot build [chars] for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MSG_PAYLOAD_BUILD_GENERAL_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Failed to build [chars]: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MSG_PAYLOAD_ENCODE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: cannot encode mobility payload/s for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MSG_PAYLOAD_PROCESS_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: Cannot process [chars] for [chars]. Reason: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR |
3-Error |
%02x%02x.%02x%02x.%02x%02x: [chars] received is missing payload [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-3-MSG_TIMER_ERROR |
3-Error |
[chars] Timer: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_LOG-4-EXPORT_ANCHOR_DENY |
4-Warning |
Export anchor required, but received export anchor deny for: WLAN Profile: [chars], Client MAC: %02x:%02x:%02x:%02x:%02x:%02x, Error: [chars] |
Export anchor required: received export anchor deny |
ewlc-guest |
If this message occurs, depending on the error code appropriate action is required. |
MM_LOG-4-RETRIES_FAILED |
4-Warning |
MAC: %02x:%02x:%02x:%02x:%02x:%02x: All retries of [chars] (XID: [dec]) to [chars] have been exhausted |
All retries for packet are exhaused |
ewlc-mobility |
LOG_STD_ACTION |
MM_LOG-6-ANCHOR_GENERIC_INFO |
6-Information |
Anchor: [chars]. client mac: %02x:%02x:%02x:%02x:%02x:%02x |
Anchor has detected a protocol issue and recovered. |
ewlc-guest |
LOG_STD_NO_ACTION |
MM_LOG-6-MAX_CLIENTS_PER_WLAN_REACHED |
6-Information |
Maximum number of Clients on wlan [chars] with Limit: [dec] Reached |
Maximum number of Clients per wlan Join Limit Reached. |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_LOG-6-MAX_CLIENTS_THRESHOLD_REACHED |
6-Information |
Maximum number of Client Join Limit: [dec] Reached |
Maximum number of Client Join Limit Reached. |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_LOG-6-MM_EXPORT_ANCHOR_FULL |
6-Information |
Export Anchor not responding, back off condition set (Client MAC: %02x:%02x:%02x:%02x:%02x:%02x, AnchorIP: [chars]) |
LOG_EXPL_SYSINFO |
ewlc-guest |
LOG_STD_NO_ACTION |
MM_LOG-6-WLAN_CLIENT_LIMIT |
6-Information |
Client limit reached on [chars]. Denied client mac: %02x:%02x:%02x:%02x:%02x:%02x |
Client limit reached on wlan on anchor. |
ewlc-mobility |
LOG_STD_ACTION |
MM_LOG-7-EXPORT_ANCHORS_DOWN |
7-Debug |
MAC:%02x:%02x:%02x:%02x:%02x:%02x: All Export-Anchors are down. |
All Export-Anchors are down. |
ewlc-guest |
If this message occurs, it implies that there is loss of network connectivity between the WLC and the export anchors for this guest LAN. It is recommended that the network and the status of the anchors be debugged for connectivity issues. |
MM_LOG-7-MSG_PAYLOAD_SIZE_ERROR |
7-Debug |
The payload size has exceeded the limit. [chars] |
Available buffer cannot hold IPV6 NDP pkt payload. |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-0-MULTICAST_GROUP_IP_SET_ERROR |
0-Emergency |
Error in [chars] while setting local mobility group multicast IP address [dec].[dec].[dec].[dec]. Please disable mobility multicast-mode if this error continues |
Mobility is unable to use multicast for messaging |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-1-ANCHORS_DOWN |
1-Alert |
All Export-Anchors are down |
All Export-Anchors are down on WLAN |
ewlc-guest |
If this message occurs, it implies that there is loss of network connectivity between the WLC and the export anchors for this WLAN. It is recommended that the network and the status of the anchors be debugged for connectivity issues. |
MM_NODE_LOG-1-KEEP_ALIVE |
1-Alert |
Mobility [chars] tunnel to peer [chars] changed state to [chars] |
Mobility tunnel state change message. |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-3-BUFF_ALLOC_FAILED |
3-Error |
Failed to allocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-BUFF_DEALLOC_FAILED |
3-Error |
Failed to deallocate memory for [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-INTFCHANGE_REGISTER_FAILED |
3-Error |
Failed to register callback for interface changes |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-3-INVALID_NONCE_RECVD |
3-Error |
Received an invalid Nonce-update from [chars]. [chars]. |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-INVALID_PMKDEL_RECVD |
3-Error |
Received PMK-delete from [chars] with no Station address TLV. |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-INVALID_PMKUPD_RECVD |
3-Error |
Received an invalid PMK-update from [chars]. [chars]. |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-MEMBER_ADD_FAILED |
3-Error |
Could not add Mobility Member. Reason: [chars], IP: [chars] |
Could not add Mobility Member for the given reason. |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-MEMBER_DEL_FAILED |
3-Error |
Could not delete Mobility Member. Reason: [chars], IP: [chars] |
Mobility Member deletion from the list failed |
ewlc-mobility |
Please check if the mobility member to be deleted exists |
MM_NODE_LOG-3-MEMBER_UPDATE_FAILED |
3-Error |
Could not update Mobility Member. Reason: [chars], IP: [chars] |
Could not update Mobility Member for the given reason. |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR |
3-Error |
[chars] message received is missing payload [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-MULTICAST_GROUP_SEND_ERROR |
3-Error |
Unable to send multicast mobility message. [chars] |
Mobility is unable to use multicast for messaging |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-3-PEER_PING_FAILED |
3-Error |
Mobility ping to [chars] rejected. [chars] |
Mobility ping rejected |
ewlc-mobility |
Please check the ping command issued |
MM_NODE_LOG-3-PEER_PING_VERSION_UNKNOWN |
3-Error |
Mobility ping to [chars] rejected. [chars] |
Mobility ping version unknown |
ewlc-mobility |
Please check if the controllers in the mobility list can interOp and |
MM_NODE_LOG-3-PING_DROPPED |
3-Error |
Drop [chars] ping from [chars]. [chars] |
Mobility ping response Dropped |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-3-PING_SEND_FAILED |
3-Error |
Failed to send a [chars] ping to [chars] . Reason: [chars]. |
Failed to send a ping |
ewlc-mobility |
Please check mobility configuration to see if it needs correction |
MM_NODE_LOG-3-SOCK_INVALID_MULTICAST_ADDRESS |
3-Error |
Mobility group local multicast address has invalid setting: [dec].[dec].[dec].[dec]. Resetting it to 0.0.0.0 and disabling mobility multicast |
Mobility multicast group address configuration was found invalid. It may have been corrupted during config transfer |
ewlc-mobility |
Configure the address again by using cmd: config mobility multicast-mode enable multicast_address |
MM_NODE_LOG-3-SOCK_OPER_FAILED |
3-Error |
Failed to [chars] a socket. [chars] |
A Socket operation is failed |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-3-SOCK_SET_ADDRESS_OPTION_FAILED |
3-Error |
Failed to [chars] a socket. Reason: [chars]. |
A Socket operation is failed. Multicast mode will not work for mobility |
ewlc-mobility |
Try setting the local group multicast address again. If the same error is seen, disable the multicast-mode for mobility and |
MM_NODE_LOG-3-SYSTEM_IP |
3-Error |
Peer IP conflicts with system IP [chars] |
Peer Ip is conflicting with System Management Ip. |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-3-SYSTEM_MAC |
3-Error |
Member [chars] is configured with a MAC that conflicts with system mobility MAC addres (%02x%02x.%02x%02x.%02x%02x) |
Peer MAC is conflicting with System Mobility MAC. |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-4-DTLS_HANDSHAKE_FAIL |
4-Warning |
[chars] handshake failed for [chars] HB is down, need to re-initiate DTLS handshake |
Error during DTLS handshake |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-4-HB_MEMBER_ADD_BY_IP_ERROR |
4-Warning |
Error adding Mobility member to heartbeat list (IP: [chars]) |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-4-HB_MEMBER_ADD_ERROR |
4-Warning |
Error adding Mobility member to heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x, IP: [chars]) |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-4-HB_MEMBER_DELETE_BY_IP_ERROR |
4-Warning |
Error deleting Mobility member from heartbeat list (IP: [chars]) |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-4-HB_MEMBER_DELETE_ERROR |
4-Warning |
Error deleting Mobility member from heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x, IP: [chars]) |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-4-HEARTBEAT_LIST_MEMBER_UPDATE_ERROR |
4-Warning |
Error updating Mobility member IP in heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x,, oldIP: [chars], newIP: [chars]) |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_ACTION |
MM_NODE_LOG-4-MEMBER_DOWN |
4-Warning |
[chars] path to mobility member [chars] is DOWN |
A path to mobility member is DOWN |
ewlc-mobility |
If this message occurs, it implies that there is loss of network connectivity between the WLC and one of its mobility peers. It is recommended that the network and the status of the peers be debugged for connectivity issues. |
MM_NODE_LOG-4-PMTU_FAILED |
4-Warning |
Capwap path MTU discovery error: [chars] |
Mobility path MTU discovery failure |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-4-PMTU_SET_FAILED |
4-Warning |
Failed to set path MTU to fast path for peer IP: [chars] |
LOG_EXPL_SYSERR |
ewlc-mobility |
LOG_STD_RECUR_ACTION |
MM_NODE_LOG-6-HEARTBEAT_LIST_MEMBER_UPDATED |
6-Information |
Updating Mobility member IP in heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x,, oldIP: [chars], newIP: [chars]) |
LOG_EXPL_SYSINFO |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-6-MEMBER_ADDED |
6-Information |
Adding Mobility member (IP: [chars]: [chars]) |
LOG_EXPL_SYSINFO |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-6-MEMBER_DELETED |
6-Information |
Deleting Mobility member (IP: [chars]) |
LOG_EXPL_SYSINFO |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-6-MEMBER_UP |
6-Information |
[chars] path to mobility member [chars] is UP |
A path to mobility member is UP |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-6-MEMBER_UPDATED |
6-Information |
Updating Mobility member (IP: [chars]: [chars]) |
LOG_EXPL_SYSINFO |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-6-MM_EXPORT_ANCHOR_FULL_RESET |
6-Information |
Export Anchor back off condition cleared (AnchorIP: [chars]) |
LOG_EXPL_SYSINFO |
ewlc-guest |
LOG_STD_NO_ACTION |
MM_NODE_LOG-6-PING_RECEIVER_ENTRY_DELETED |
6-Information |
Deleted ping receiver entry ([chars]) from heartbeat list for WLAN ([dec]) |
LOG_EXPL_SYSINFO |
ewlc-mobility |
LOG_STD_NO_ACTION |
MM_NODE_LOG-6-SOCK_SET_ADDRESS_OPTION |
6-Information |
Setting [chars] multicast group [chars] on the mobility sockets. |
Multicast group membership was set on the socket. |
ewlc-mobility |
LOG_STD_NO_ACTION |
MOBILITYD_LOG-2-INIT_FAILED |
2-Critical |
Error while initializing mobility daemon. [chars] |
Error while initializing mobility daemon |
ewlc-mobility |
If this error is seen, it is recommended that the controller's mobility configuration be redone as it may have been lost. If you still require assistance, open a case with the Technical Assistance Center via the Internet or contact your Cisco technical support |
NDBMAN-3-CONFIG_COMMIT_FAIL |
3-Error |
Commit failed for feature '[chars]' from [chars]:[dec] via [chars] user [chars] session [dec], transaction-id [dec]i error [chars] |
A failed attempt to change running configuration was made via one of the model-based interfaces NETCONF/RESTCONF/GNMI. Configuration was successfully validated by the feature during the validation phase of the transaction but failed during the commit phase |
ddmi-infra |
Check the device cnfiguration. Collect device logs. Reinitialize the model-based component |
NDBMAN-4-CONFIG_REJECT_W |
4-Warning |
Config rejected by feature '[chars]' from [chars]:[dec] via [chars] user [chars] session [dec], transaction-id [dec] error [chars] |
A failed attempt to change running configuration was made via one of the model-based interfaces NETCONF/RESTCONF/GNMI. Either the feature validation logic rejected the config change as invalid or an error occured during an attempt to validate the config modification |
ddmi-infra |
Informational only. No action required. |
NDBMAN-5-ACTIVE |
5-Notice |
All data providers active. |
All data providers active. |
ddmi-infra |
Informational only. No action required. |
NDBMAN-5-CONFIG_I |
5-Notice |
Configured feature '[chars]' from [chars]:[dec] via [chars] user [chars] session [dec], transaction-id [dec] |
A change to the running configuration was performed via one of the model-based interfaces NETCONF/RESTCONF/GNMI. |
ddmi-infra |
Informational only. No action required. |
NDBMAN-5-MODEL_RPC_I |
5-Notice |
RPC '[chars]:[chars]' invoked from [chars]:[dec] via [chars] user [chars] session [dec] |
A model remote procedure call was performed via one of the model-based interfaces NETCONF/RESTCONF/GNMI. |
ddmi-infra |
Informational only. No action required. |
NDBMAN-5-RESET |
5-Notice |
A data provider has stopped. |
At least one data provider has stopped. |
ddmi-infra |
Informational only. No action required. |
NDBUTIL-4-OUT_OF_RANGE_FOR_DECIMAL64_AND_FD |
4-Warning |
Double (%1$s) with value (%2$lf) is out-of-range (-%3$ld to %3$ld, exclusive) for a Decimal64 with fraction-digits = %4$d. |
The value of the EI double cannot be reliably converted to Yang Decimal64 with the specified fraction-digits with the proper precision, so the EI to Yang conversion is intentionally failing. The EI value should not be this big, so there's an error with the module setting the attribute's value. |
ddmi-infra |
Report an error to the Cisco engineering team responsible for the module that's setting the attribute. |
NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_APPLY |
5-Notice |
AP neighborhood based algorithm applied. [dec] number of APs have been load-balanced across WNCd instances. |
RF based AP neighborhood algorithm is applied |
ewlc-ap |
If this message occurs, it implies that number of APs required load-balanced as per the load-balancing output |
NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_DONE |
5-Notice |
AP clustering and WNCD assignment algorithm completed. [dec] number of AP neighborhoods formed and ready to load-balance across WNCD instances. |
RF based AP clustering formation is done and sub-neighborhoods have been allocated the WNCD instances |
ewlc-ap |
If this message occurs, it implies that all AP can be loadbalanced by using exec apply CLI or reload of the controller |
NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_START |
5-Notice |
Starting AP clustering and WNCD assignment algorithm. Total number of APs collected for calculation: [dec]. |
Notification to start the neighborhood calcultion |
ewlc-ap |
If this message occurs, Neighborhood algorithm is in progress. |
NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_TIMER_EVENT |
5-Notice |
RRM based AP neighborhood algorithm cannot be started within 1 hour of system boot on calendar profile timer expiry event. |
Calander profile start timer expiry event is ignored |
ewlc-ap |
If this message occurs, it implies that AP neighborhood algorithm is not started on timer expiry event. |
NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_UNSUPPORTED |
5-Notice |
RF based AP neighborhood load-balancing is not applicable to this platform. Please unconfigure calendar profile from ap neighborhood global configuration. |
Calander profile timer event callback handling error |
ewlc-ap |
If this message occurs, it implies that a calander profile is attached to ap neighborhood config on an unsupported platform |
NIF_MGR-6-DAD |
6-Information |
Dual Active detected: [chars]\n |
Dual Active detected print on console. |
iosxe-fwdmgr |
No action. Action is only after recovery mode |
NIF_MGR-6-DAD_RECOVERY_MODE |
6-Information |
Dual Active detected: Switch going into recovery mode [chars].\n |
Dual Active detected print on console. |
iosxe-fwdmgr |
This switch need to be reloaded once user finishes debugging |
NIF_MGR-6-DAD_RECOVERY_RELOAD_ALERT |
6-Information |
Switch is in recovery mode, needs Reload now. [chars].\n |
Switch is in recovery mode, needs Reload now |
iosxe-fwdmgr |
This switch need to be reloaded since some correction is noticed |
NIF_MGR-6-DOMAIN_NUMBER_MISMATCH |
6-Information |
Stackwise virtual domain number mismatch on stackwise virtual link [dec]\n |
A port associated with a stackwise virtual link is connected to a peer with a different domain number than the local switch |
iosxe-fwdmgr |
For the switch to form a stack please configure same domain numbers on both the switches |
NIF_MGR-6-PORT_CONNECTION_STATUS_CHANGE |
6-Information |
PORT:[chars] changed state from [chars] to [chars].\n |
FSS Stack Port status change message. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-PORT_CONN_DISCONNECTED |
6-Information |
[chars] on front side stack link [dec] connection has DISCONNECTED: [chars]\n |
A port associated with a front side stack link has disconnected connection. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-PORT_CONN_ERR |
6-Information |
[chars] on front side stack link [dec] connection is in ERR-DISABLE: [chars]\n |
A port associated with a front side stack link has reached err-disable state. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-PORT_CONN_PENDING |
6-Information |
[chars] on front side stack link [dec] connection is PENDING.\n |
A port associated with a front side stack link has a pending connection. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-PORT_CONN_READY |
6-Information |
[chars] on front side stack link [dec] connection is READY.\n |
A port associated with a front side stack link has a ready connection. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-PORT_CONN_TIMEOUT |
6-Information |
[chars] on front side stack link [dec] connection has TIMEOUT: [chars]\n |
A port associated with a front side stack link has disconnected connection. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-PORT_LINK_DOWN |
6-Information |
[chars] on front side stack link [dec] is DOWN.\n |
A port associated with a front side stack link has come up. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-PORT_LINK_UP |
6-Information |
[chars] on front side stack link [dec] is UP.\n |
A port associated with a front side stack link has come up. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-STACK_LINK_DOWN |
6-Information |
Front side stack link [dec] is DOWN.\n |
A port associated with a front side stack link has come up. |
iosxe-fwdmgr |
No action is required |
NIF_MGR-6-STACK_LINK_UP |
6-Information |
Front side stack link [dec] is UP.\n |
A port associated with a front side stack link has come up. |
iosxe-fwdmgr |
No action is required |
NIM_XXD-3-DISK_ERROR |
3-Error |
Error detected on disk [dec] in module [chars] in subslot [dec]/[dec]. [chars]. |
Disk error detected in the SPA (NIM-SSD/NIM-HDD). Refer to comment for details. |
iosxe-chassismgr |
Back-up any data and replace the disk. |
NIM_XXD-3-DISK_REMOVAL |
3-Error |
One or more disks in SPA ([chars]) in subslot [dec]/[dec] can not be detected. Please power down this SPA and insert disk(s). |
Disks have been removed from SPA |
iosxe-chassismgr |
Power down the SPA, insert disks and power up the SPA. |
NIM_XXD-5-DISK_MONITOR |
5-Notice |
Disk [dec] in module [chars] in subslot [dec]/[dec] is detected but monitoring is not available. |
Monitoring of disk in SPA (NIM-SSD/NIM-HDD) is unavailable. |
iosxe-chassismgr |
Add a database file with monitoring information for this disk model and manufacturer. |
NMSP_SYSLOG-3-NMSP_DB_LOCK_NOT_ACQUIRED |
3-Error |
NMSP client application is expected to acquire lock for NMSP local database before calling NMSP API: [chars] |
Locking sequence for the DB's is defined in this application. The locking order of DB's needs to be followed as per the application set order, where local DB come first. NMSP client application must acquire local DB lock before calling NMSP API |
ewlc-nmsp |
LOG_STD_ACTION |
NMSP_SYSLOG-3-NMSP_HTTPS_ERROR_CONFIG |
3-Error |
nmspd cloud service config error: [chars] |
Configuration error prevented successful connection to CMX cloud service. |
ewlc-nmsp |
Check configuration of cmx cloud service, e.g. server URL and token. |
NMSP_SYSLOG-3-NMSP_HTTPS_ERROR_CRYPTO |
3-Error |
nmspd HTTPS error: [chars] |
Peer verification of CMX cloud service failed. |
ewlc-nmsp |
Check that server certificate can be verified by root CA certificates in trustpool of crypto PKI. |
NMSP_SYSLOG-3-NMSP_SSL_ERROR_CERT |
3-Error |
nmspd TLS certificate error: [chars] |
Error validating TLS certificate for incoming CMX connection |
ewlc-nmsp |
Check that certificates and SHA2 key are properly setup on eWLC. Contact TAC if issue persists. |
NMSP_SYSLOG-3-NMSP_SSL_ERROR_DISCONNECT |
3-Error |
nmspd TLS disconnection: [chars] |
Remote CMX connection over TLS protocol had been dropped. |
ewlc-nmsp |
Check connectivity with CMX, CMX service status and AAA configuration. |
NMSP_SYSLOG-3-NMSP_SSL_ERROR_INTERNAL |
3-Error |
nmspd internal error occured when handling TLS connection: [chars] |
Internal eWLC error prevented successful establishment of CMX connection over TLS protocol |
ewlc-nmsp |
Check availability of the system resources of the eWLC controller: memory, open files, sockets. Contact TAC if issue persists |
NMSP_SYSLOG-5-NMSP_HTTPS_INTERFACE_NOTICE |
5-Notice |
nmspd HTTPS info: [chars] |
Wireless management interface notification. |
ewlc-nmsp |
No action required. |
NMSP_SYSLOG-5-NMSP_HTTPS_NOTICE |
5-Notice |
nmspd HTTPS info: [chars] |
This is an informational message. |
ewlc-nmsp |
No action required. |
NMSP_SYSLOG-5-NMSP_SSL_NOTICE |
5-Notice |
nmspd TLS notice: [chars] |
This is an informational message. |
ewlc-nmsp |
No action required. |
NPI_L3TUNNEL_ERRMSG-3-MAX_TUNNEL |
3-Error |
The maximum number of Tunnel has been reached\n |
Hardware resource allocation has failed and the entry will not be programmed. |
INVALID |
New Tunnels will not be working as expected. |
ODM_SERVER_ERRMSG-3-ODM_TABLE_REGISTER_DB_NOT_CONFIG |
3-Error |
Client ([chars]/[dec]) table [[chars]/[chars]] registration DB [[chars]] is not found in server configuration |
ODM client is registering its monitored TDL database tables to ODM server daemon. But ODM server daemon doesn't have requested (consolidated) database information. |
iosxe-p-db |
LOG_STD_ACTION |
ODM_SERVER_ERRMSG-3-ODM_TABLE_REGISTER_TABLE_NOT_CONFIG |
3-Error |
Client ([chars]/[dec]) table [[chars]/[chars]] registration table is not found in server DB [[chars]] configuration |
ODM client is registering its monitored TDL database tables to ODM server daemon. But ODM server daemon doesn't have requested table information in consolidated database. |
iosxe-p-db |
LOG_STD_ACTION |
ODM_SERVER_ERRMSG-4-ODM_TABLE_REGISTER_CONFIG_MISMATCH |
4-Warning |
Client ([chars]/[dec]) table [[chars]/[chars]] registration table configuration (0x%x) mis-matched with server configuration (0x%x) |
ODM client is registring its monitored TDL database tables to ODM server daemon. But ODM table configuration is not matched between client and server. |
iosxe-p-db |
LOG_STD_ACTION |
OMPD-3-PEER_STATE_INIT |
3-Error |
[chars] peer [chars] state changed to Init |
This syslog is generated when OMP peer state changes to INIT |
vip-omp |
No action is required |
OMPD-3-STATE_DOWN |
3-Error |
Operational state changed to [chars] |
This syslog is generated when Cisco SD-WAN Overlay Management Protocol (OMP) goes DOWN |
vip-omp |
No action is required |
OMPD-5-PEER_STATE_UP |
5-Notice |
[chars] peer [chars] state changed to Up |
This syslog is generated when OMP peer state changes to UP |
vip-omp |
No action is required |
OMPD-5-STATE_UP |
5-Notice |
Operational state changed to [chars] |
This syslog is generated when Cisco SD-WAN Overlay Management Protocol (OMP) comes UP |
vip-omp |
No action is required |
OMPD-6-NUMBER_OF_VSMARTS |
6-Information |
Number of vSmarts connected : [dec] |
This info log is generated whenever SD-WAN edge device either establishes (or) looses connection with SD-WAN Controller nodes |
vip-omp |
No action is required |
OMPD-6-PEER_STATE_HANDSHAKE |
6-Information |
[chars] peer [chars] state changed to Handshake |
This syslog is generated when OMP peer state changes to HANDSHAKE |
vip-omp |
No action is required |
OOM-0-NO_MEMORY_RESET |
0-Emergency |
The system is completely out of available memory. The board will be reset. |
The system has exhausted all available memory and the hardware component will be reset. |
iosxe-binos-utils |
Review other messages related to low memory states and see if those messages contain any information about an issue that can be addressed. If this problem persists, copy all the output from the console as well as the output of show tech-support, and provide the gathered information to your Cisco technical support representative. |
OOM-3-NO_MEMORY_AVAIL |
3-Error |
The system is very low on available memory. Operations will begin to fail. |
The system has exhausted all available memory. It is not possible to continue stable operation. |
iosxe-binos-utils |
The system has exhausted all available memory and stable operation is no longer possible. |
P to T
Facility-Severity-Mnemonic |
Severity-Meaning |
Message |
Message-Explanation |
Component |
Recommended-Action |
---|---|---|---|---|---|
PAE_CORE_TEST-6-REPORT_ID |
6-Information |
Created report id: [chars] |
Result of the test report request |
iosxe-ui |
LOG_STD_NO_ACTION |
PAM_UPDB-3-NOENVIRONMENT_SET |
3-Error |
Error setting user in application environment: [chars] |
The user has succesfully authenticated, but the user information could not be saved to the application environment. The user session will not proceed. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
PAM_UPDB-3-NOPROMPT_READ |
3-Error |
Error reading [chars] prompt: [chars] |
The authentication module was unable to read the specified prompt file. The default prompt will be used. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
PCGW_HA_LIB_MESSAGE-3-BULK_SYNC_STATE_ERR |
3-Error |
Error: Bulk sync status : [chars] |
Bulk sync status Error message. TERMINATED - Bulk-sync terminated |
pcgw-ha |
LOG_STD_NO_ACTION |
PCGW_HA_LIB_MESSAGE-3-PCGW_CONFIG_SYNC_FAIL |
3-Error |
Error: pcgw config sync not complete. Reloading the PCGW! |
Switchover happens before pcgw config sync is complete! |
pcgw-ha |
LOG_STD_ACTION |
PCGW_HA_LIB_MESSAGE-6-BULK_SYNC_STATE_INFO |
6-Information |
INFO: Bulk sync status : [chars] |
Bulk sync status INFO message. COLD - Bulk-sync ongoing. CONFIG_DONE - critical DB sync complete. WARM - Most of the DB's synced. HOT - Bulk-sync completed |
pcgw-ha |
LOG_STD_NO_ACTION |
PEER_SELECTION-5-EWC_PEER_SELECTION_ADD_EV |
5-Notice |
ADD event: [chars] |
Reports an important HA peer (a.k.a. standby) selection ADD event |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
PEER_SELECTION-5-EWC_PEER_SELECTION_PREFER_EV |
5-Notice |
Preferred master event: [chars] |
Reports an important HA peer (a.k.a. standby) selection preferred master event |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
PEER_SELECTION-5-EWC_PEER_SELECTION_REMOVE_EV |
5-Notice |
REMOVE event: [chars] |
Reports an important HA peer (a.k.a. standby) selection REMOVE event |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
PEER_SELECTION-5-EWC_PEER_SELECTION_SELECT_EV |
5-Notice |
SELECT event: [chars] |
Reports an important HA peer (a.k.a. standby) selection SELECT event |
iosxe-binos-utils |
LOG_STD_NO_ACTION |
PLATFORM-2-S1_ASIC_FABRIC_BW_ABOVE_THRESHOLD |
2-Critical |
S1 ASIC EVENT: The number of fabric ports in the S1 ASIC [dec] are above the system threshold.\n |
Silicon one ASIC fabric port threshold event |
INVALID |
Check the fabric info for the S1 ASIC |
PLATFORM-2-S1_ASIC_FABRIC_BW_BELOW_THRESHOLD |
2-Critical |
S1 ASIC EVENT: The number of fabric ports in the S1 ASIC [dec] are below the system threshold.\n |
Silicon one ASIC fabric port threshold event |
INVALID |
Check the fabric info for the S1 ASIC |
PLATFORM-2-S1_ASIC_THROTTLING_DISABLE |
2-Critical |
S1 ASIC EVENT: S1 ASIC [dec] temperature is back to normal. Traffic throttling is disabled now.\n |
Silicon one ASIC overheating event |
INVALID |
Copy the message exactly as it appears on the console or in the system log |
PLATFORM-2-S1_ASIC_THROTTLING_ENABLE |
2-Critical |
S1 ASIC EVENT: A high temperature condition is detected in S1 ASIC [dec]. The system will automatically enable traffic throttling in an attempt to restore temperatures and prevent permanent damage to the ASIC. Traffic drops are expected in this scenario and normal traffic behaviour will resume after the ambient ASIC temperatures are restored.\n |
Silicon one ASIC overheating event |
INVALID |
Check the ambient temperature of the room and check for blockages in airflow |
PLATFORM-3-ELEMENT_CRITICAL |
3-Error |
[chars]: [chars] value [chars] [chars] critical level [chars] |
The Shell Manager monitors the health of each board and emits an error message when a value has passed a critical level. |
iosxe-shellmgr |
Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services. |
PLATFORM-3-ELEMENT_TMPFS_CRITICAL |
3-Error |
[chars]: TMPFS value [dec]%% above critical level [dec]%% |
The Shell Manager monitors the tmpfs usage of each board and emits an error message when a value has passed warning level. The critical level is computed based on total DRAM memory. Currently the critical level is 50% of total DRAM memory |
iosxe-shellmgr |
Emit syslog message with current tmpfs usage, warning level along with location of the board in which the error is happening |
PLATFORM-3-ELEMENT_TMPFS_WARNING |
3-Error |
[chars]: TMPFS value [dec]%% above warning level [dec]%% |
The Shell Manager monitors the tmpfs usage of each board and emits an error message when a value has passed warning level.The warning level is computed based on total DRAM memory. Currently the warning level is 40% of total DRAM memory |
iosxe-shellmgr |
Emit syslog message with current tmpfs usage, warning level along with location of the board in which the error is happening |
PLATFORM-4-ELEMENT_WARNING |
4-Warning |
[chars]: [chars] value [chars] [chars] warning level [chars]. [chars] |
The Shell Manager monitors the health of each board and emits a warning message when a value has passed a critical level. |
iosxe-shellmgr |
Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services. |
PLATFORM-5-RESETCARD |
5-Notice |
[chars] reset to acquire provisioned software |
The linecard specified was not running the currently provisioned software, which it will acquire on restart. |
iosxe-binos-utils |
No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. |
PLATFORM_MGR-1-PLATMGR_INIT_FAIL |
1-Alert |
Platform Manager: [chars]\n |
Platform Manager Initialization has failed. |
polaris-platform_mgr |
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. |
PMAN-0-PROCESS_NOTIFICATION |
0-Emergency |
The process lifecycle notification component failed because [chars] |
The process lifecycle notification component failed, preventing proper detection of a process start and stop. This problem is likely the result of a software defect in the software sub-package. |
iosxe-chassismgr |
Note the time of the message and investigate the kernel error message logs to learn more about the problem and see if it is correctable. If the problem cannot be corrected or the logs are not helpful, copy the error message exactly as it appears on the console along with the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PMAN-0-PROCFAILCRIT |
0-Emergency |
A critical process [chars] has failed (rc [dec]) |
A process important to the functioning of the router has failed. |
iosxe-chassismgr |
Note the time of the message and investigate the error message logs to learn more about the problem. If the problem persists, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support with the gathered information. |
PMAN-3-PROCFAIL |
3-Error |
The process [chars] has failed (rc [dec]) |
The process has failed as the result of an error. |
iosxe-chassismgr |
This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. |
PMAN-3-PROCFAILOPT |
3-Error |
An optional process [chars] has failed (rc [dec]) |
A process that does not affect the forwarding of traffic has failed. |
iosxe-chassismgr |
Note the time of the message and investigate the kernel error message logs to learn more about the problem. Although traffic will still be forwarded after receiving this message, certain functions on the router may be disabled as a result of this message and the error should be investigated. If the logs are not helpful or indicate a problem you cannot correct, copy the error message as it appears on the console and the output of show tech-support and provide the information to a Cisco technical support representative. |
PMAN-3-PROCFAIL_IGNORE |
3-Error |
[chars] process exits and failures are being ignored due to debug settings. Normal router functionality will be affected. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly. |
A process exit or failure is being ignored due to the user-configured debug settings. |
iosxe-chassismgr |
If this behavior is desired and the debug settings are set according to the user's preference, no action is needed. If the appearance of this message is viewed as a problem, change the debug settings. The router is not expected to behave normally with this debug setting. Functionality like SSO switchover, router reloads, FRU resets, etc. will be affected. This setting should only be used in a debug scenario. It is not normal to run the router with this setting |
PMAN-3-PROCHOLDDOWN |
3-Error |
The process [chars] has been helddown (rc [dec]) |
The process was restarted too many times with repeated failures and has been placed in the holddown state. |
iosxe-chassismgr |
This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. |
PMAN-3-PROC_BAD_COMMAND |
3-Error |
Non-existent executable or bad library used for process [chars] |
The executable file used for the process is missing or a dependent library is bad |
iosxe-chassismgr |
Make sure that the named executable is present and dependent libraries are good |
PMAN-3-PROC_BAD_EXECUTABLE |
3-Error |
Bad executable or permission problem with process [chars] |
The executable file used for the process is bad or has permission problem |
iosxe-chassismgr |
Make sure that the named executable is replaced with correct executable |
PMAN-3-PROC_EMPTY_EXEC_FILE |
3-Error |
Empty executable used for process [chars] |
The executable file used for the process is empty |
iosxe-chassismgr |
Make sure that the named executable is of non-zero size |
PMAN-3-PROC_RESTART_CNT_EXCEEDED |
3-Error |
The process [chars] restart count ([dec]) has exceeded the configured limit ([dec]) |
The process was restarted many times and has exceeded the configured limit. |
iosxe-chassismgr |
This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. |
PMAN-3-RELOAD_FRU_IGNORED |
3-Error |
All [chars]/[dec] reloads are being ignored. This is being done for debugging purposes and will be changed at a later time to allow the reload. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly. |
A supervisor failure is being ignored due to debugging purposes. |
iosxe-chassismgr |
This will be removet at a later point in time |
PMAN-3-RELOAD_RP |
3-Error |
Reloading: [chars] |
The RP is being reloaded |
iosxe-chassismgr |
Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages |
PMAN-3-RELOAD_RP_SB_NOT_READY |
3-Error |
Reloading: [chars] |
The RP is being reloaded since there is no ready standby instance |
iosxe-chassismgr |
Make sure this is not due to an error condition |
PMAN-3-RELOAD_SYSTEM |
3-Error |
Reloading: [chars] |
The system is being reloaded |
iosxe-chassismgr |
Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages |
PMAN-3-RPSWITCH |
3-Error |
RP switch initiated. Critical process [chars] has failed (rc [dec]) |
A RP switchover has been initiated due to a critical fault |
iosxe-chassismgr |
Make sure this is not due to an error condition. If it is due to an error condition, collect debug information like all console output and log files |
PMAN-5-EXITACTION |
5-Notice |
Process manager is exiting: [chars] |
The process manager is exiting |
iosxe-chassismgr |
Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages |
PMAN-6-PROCSHUT |
6-Information |
The process [chars] has shutdown |
The process has gracefully shutdown. |
iosxe-chassismgr |
No user action is necessary. This message is provided for informational purposes only. |
PMAN-6-PROCSTART |
6-Information |
The process [chars] has started |
The process has launched and is operating properly. |
iosxe-chassismgr |
No user action is necessary. This message is provided for informational purposes only. |
PMAN-6-PROCSTATELESS |
6-Information |
The process [chars] is restarting stateless |
The process has requested a stateless restart. |
iosxe-chassismgr |
No user action is necessary. This message is provided for informational purposes only. |
PMAN-6-PROC_PATCH |
6-Information |
Process [chars] restarted to apply/remove a patch |
Process will be relaunched to apply/remove a patch |
iosxe-chassismgr |
No user action is necessary. This message is provided for informational purposes only. |
POLICY-3-DATA_POLICY_COMMIT_FAILURE |
3-Error |
Data policy commit failure error, reason: [chars] ([chars]) |
This error syslog is generated when OMP daemon is not able to commit data policies config, received from SD-WAN Controller, into config database. This can happen when there multiple commits (writes) happening in parallel. SD-WAN edge device will not be able to apply centralized data policies to traffic |
vip-omp |
No action is required, the system should recover after sometime when OMP daemon would retry committing data policy config into CDB |
POLICY-3-TAG_INSTANCES_COMMIT_FAILURE |
3-Error |
Tag instances commit failure error, reason: [chars] ([chars]) |
This error syslog is generated when OMP daemon is not able to commit tag instances config, received from SD-WAN Controller, into config database. This can happen when there multiple commits (writes) happening in parallel SD-WAN edge device will not be able to apply centralized data policies to traffic |
vip-omp |
No action is required, the system should recover after sometime when OMP daemon would retry committing tag instance config into CDB |
POLICY-5-EMPTY_POLICY_FROM_PEER |
5-Notice |
Using empty policy from peer [chars] |
This syslog is generated when Cisco SD-WAN Controller does not push (or) removes centralized data policy from cEdge device |
vip-omp |
No action is required |
POLICY-5-NO_POLICY |
5-Notice |
Not using any policy |
This syslog is generated when there are no OMP connections to Cisco SD-WAN Controller and Graceful Restart timer has also expired. Existing centralized data policy is removed |
vip-omp |
No action is required |
POLICY-5-POLICY_FROM_PEER |
5-Notice |
Using policy from peer [chars] |
This syslog is generated whenever data-policy config received from Cisco SD-WAN Controller is programmed into data path |
vip-omp |
No action is required |
PRELIB_DL-3-UNREGISTERED_DLOPEN |
3-Error |
Unregistered request to dlopen library [chars] |
The program is attempting to dynamically open a library that has not been explicitly listed on its list of dynamically opened libraries. This represents a potential security threat as well as creates potential run-time instabilities |
iosxe-binos-utils |
File a DDTS against the listed program to register the library in question. If this was an unexpected call to dlopen then the source of the call should be root-caused and closed |
PSD_MOD-3-DMI_DIR_CREATE_FAIL |
3-Error |
PSD/DMI: Failed to create directory: [chars] ([chars]) |
An error has occurred when attempting to create a directory. |
ddmi-infra |
Log a message |
PSD_MOD-3-DMI_DIR_DELETE_FAIL |
3-Error |
PSD/DMI: Failed to delete directory: [chars] ([chars]) |
An error has occurred when attempting to delete a directory. |
ddmi-infra |
Log a message |
PSD_MOD-3-DMI_FILE_CREATE_FAIL |
3-Error |
PSD/DMI: Failed to create file: [chars] ([chars]) |
An error has occurred when attempting to create a file. |
ddmi-infra |
Log a message |
PSD_MOD-3-DMI_FILE_DELETE_FAIL |
3-Error |
PSD/DMI: Failed to delete file: [chars] ([chars]) |
An error has occurred when attempting to delete a file. |
ddmi-infra |
Log a message |
PSD_MOD-3-SD_ROUTING_DMI_REQUIRED |
3-Error |
PSD/SD-ROUTING: Please configure netconf-yang to activate the sd-routing feature |
SD-Routing depends upon DMI |
cntrl-mng-rtg |
Not applicable |
PSD_MOD-5-DMI_NOTIFY_NETCONF_START |
5-Notice |
PSD/DMI: netconf-yang server has been notified to start |
A specific informational message from psd_mod |
ddmi-infra |
Not applicable |
PSD_MOD-5-DMI_NOTIFY_NETCONF_STOP |
5-Notice |
PSD/DMI: netconf-yang server has been notified to stop |
A specific informational message from psd_mod |
ddmi-infra |
Not applicable |
PSD_MOD-5-DMI_NOTIFY_RESTARTING |
5-Notice |
PSD/DMI: netconf-yang and/or restconf will now be restarted, and any sessions in progress will be terminated |
A specific informational message from psd_mod |
ddmi-infra |
Not applicable |
PSD_MOD-5-DMI_NOTIFY_RESTCONF_START |
5-Notice |
PSD/DMI: restconf server has been notified to start |
A specific informational message from psd_mod |
ddmi-infra |
Not applicable |
PSD_MOD-5-DMI_NOTIFY_RESTCONF_STOP |
5-Notice |
PSD/DMI: restconf server has been notified to stop |
A specific informational message from psd_mod |
ddmi-infra |
Not applicable |
PSD_MOD-5-DMI_NOTIFY_USER |
5-Notice |
PSD/DMI: [chars] |
An informational message from psd_mod |
ddmi-infra |
Not applicable |
PSD_MOD-5-PSID_NOTIFY_SYSTEM_INTEGRITY_START |
5-Notice |
SYSTEM INTEGRITY: pistis daemon has been notified to start |
A specific informational message from psd_mod |
polaris-infra |
Not applicable |
PSD_MOD-5-PSID_NOTIFY_SYSTEM_INTEGRITY_STOP |
5-Notice |
SYSTEM INTEGRITY: pistis daemon has been notified to stop |
A specific informational message from psd_mod |
polaris-infra |
Not applicable |
PSD_MOD-5-SD_ROUTING_NOTIFY_START |
5-Notice |
PSD/SD-ROUTING: SD-Routing server has been notified to start |
A specific informational message from psd_mod |
cntrl-mng-rtg |
Not applicable |
PSD_MOD-5-SD_ROUTING_NOTIFY_STOP |
5-Notice |
PSD/SD-ROUTING: SD-Routing server has been notified to stop |
A specific informational message from psd_mod |
cntrl-mng-rtg |
Not applicable |
PTHUTIL-3-EVENT_HANDLER |
3-Error |
Task [chars] has no [chars] event handler |
The task specified has failed to install a handler for the specified event. This implies that the event has been dropped. |
iosxe-binos-utils |
LOG_STD_ACTION |
PTHUTIL-3-SCHED_EMPTY |
3-Error |
Scheduler has no tasks available |
The Pth scheduler has detected that there is no task available to run. This is an error condition for the process itself is a task. |
iosxe-binos-utils |
LOG_STD_ACTION |
PTHUTIL-3-SCHED_FD_OVERFLOW |
3-Error |
Scheduler has more than [dec] FDs |
The are too many FDs for the Pth scheduler. This is an error condition for the process itself. |
iosxe-binos-utils |
LOG_STD_ACTION |
PTHUTIL-3-STACK_OVERFLOW |
3-Error |
Task [chars] stack overflow |
A Pth task has overflowed its stack. This has been detected by the Pth scheduler and reported. |
iosxe-binos-utils |
LOG_STD_ACTION |
PTHUTIL-3-TIMER_THRASHING |
3-Error |
Timer [chars] is thrashing on [chars] |
The Pth scheduler has detected that an event has remained on the ready queue after being notified of requiring processing. |
iosxe-binos-utils |
LOG_STD_ACTION |
PTHUTIL-3-TIMER_UPDATE |
3-Error |
Timer [chars] update of [chars] not updated [dec] |
The attempt to update a watched timer has failed due to either the timer not existing or the inability to move the timer to its new position post update. |
iosxe-binos-utils |
LOG_STD_ACTION |
PTPD-0-CHASFS_OBJECT_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] because [chars] |
The hardware failed to create a chassis filesystem object. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-CHASFS_OBJECT_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] not present. |
A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-CHASFS_OBJECT_WATCH |
0-Emergency |
Failed to watch chassis filesystem object [chars] because [chars] |
A chassis filesystem object was not watched because of the reason stated in the error message. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-CHASFS_PROPERTY_CREATE |
0-Emergency |
Failed to create chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly created. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-CHASFS_PROPERTY_GET |
0-Emergency |
Failed to read chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property was not properly read by the system. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-CHASFS_PROPERTY_NOT_PRESENT |
0-Emergency |
Expected chassis filesystem object [chars] property [chars] not present. |
A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-CHASFS_PROPERTY_SET |
0-Emergency |
Failed to write chassis filesystem object [chars] property [chars] because [chars] |
A chassis filesystem property failed to write. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-IPC_CONNECTION_INVALID |
0-Emergency |
An IPC connection has invalid state. |
An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-IPC_CONNECT_MASTER |
0-Emergency |
IPC connection to the active RSP failed because [chars] |
IPC connection to the active RSP failed. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-IPC_INITIALIZATION |
0-Emergency |
IPC initialization failed because [chars] |
IPC initialization failed. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-MESSAGE_REGISTER |
0-Emergency |
Failed to register with active RSP because [chars] |
The active RSP failed to register. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-MESSAGE_RELAY |
0-Emergency |
Failed to relay a message because [chars] |
Failed to relay a message. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-MESSAGE_RESPONSE |
0-Emergency |
An invalid message response was received because [chars] |
An invalid message response was received. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-MQIPC_ADVANCE |
0-Emergency |
Failed to advance MQIPC queue because [chars] |
The MQIPC initialization failed. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-MQIPC_INITIALIZATION |
0-Emergency |
MQIPC initialization failed because [chars] |
MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-PEER_TABLE |
0-Emergency |
A peer table initialization or maintenance function failed because [chars] |
A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-0-RESOURSE |
0-Emergency |
Resource allocation failed in [chars] because [chars] |
The system is unable to allocate the requested resource. |
asr900-ptp |
In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command. |
PTPD-3-CHASFS_OBJECT_DESTROY |
3-Error |
Failed to destroy chassis filesystem object [chars] because [chars] |
A chassis filesystem object that should have been destroyed was not destroyed. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
PTPD-3-CHASFS_PROPERTY_DESTROY |
3-Error |
Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] |
A chassis filesystem property that should have been destroyed was not destroyed. |
asr900-ptp |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
QOS_ERROR_MESSAGE-3-QOS_CLIENT_POLICY_AP_INSTALL_FAIL |
3-Error |
ERROR: Failed to install policy: [chars] for Client: %02x%02x.%02x%02x.%02x%02x on AP: [chars] with status: [chars] |
Client policy install on AP failed. |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_CLIENT_POLICY_AP_SEND_FAIL |
3-Error |
ERROR: For Client mac %02x%02x.%02x%02x.%02x%02x, failed to send policy [chars] to AP due to reason: [chars] |
Error Binding Client Policy. Policy not sent to AP |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_CLIENT_POLICY_AP_UNINSTALL_FAIL |
3-Error |
ERROR: Failed to uninstall policy: [chars] for Client: %02x%02x.%02x%02x.%02x%02x on AP: [chars] with status: [chars] |
Client policy unbind operation on AP failed. |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_CREATE_POLICY_DB_FAIL |
3-Error |
ERROR: Unable to allocate resources for QoS Policy Content DB |
Internal Error. Unable to allocate resources for QoS Policy Content DB |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_DOT11_CLIENT_RECORD_NOT_FOUND |
3-Error |
ERROR: Failed to get dot11 client record for Client: %02x%02x.%02x%02x.%02x%02x |
QoS get function for dot11 client record failed. |
ewlc-client |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_INVALID_POLICY |
3-Error |
ERROR: Policy [chars] is invalid in [chars] direction for vapid:[dec] |
QoS policy validation failed. Policy will not be installed |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_MEM_ALLOC_FAIL |
3-Error |
Error: Failed to allocate memory [chars] |
An internal error occurred due to which memory allocation failed |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_MODIFY_POLICY_DB_FAIL |
3-Error |
ERROR: Unable to modify QoS Policy due to Reason:[chars] |
Internal Error. Unable to modify QoS Policy Content in DB |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_MSG_BLKLIST_CLIENT |
3-Error |
Blacklisting client %02x%02x.%02x%02x.%02x%02x. Error installing client QOS policy: [chars] in [chars] direction. |
Failure occured while installing QoS client policy. Client will be deleted. |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_POLICY_EXCEED_MAX |
3-Error |
[dec] policy maps sent to AP [chars], exceeds the recommended [dec] |
Number of policies exceeds limit warning. |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_POLICY_MISSING |
3-Error |
ERROR: Policy [chars] in [chars] direction for vapid:[dec] has no content |
QoS policy validation failed. Policy will not be installed |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_SSID_INVALID_POLICY |
3-Error |
ERROR: Policy [chars] is invalid in [chars] direction for vapid:[dec]. Once the policy is modified, the bssid needs to be reset before the new policy-map definition can take effect |
QoS BSSID policy validation failed. Policy will not be installed |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_SSID_POLICY_BIND_ON_AP_FAIL |
3-Error |
ERROR: Failed to bind SSID policy on AP: [chars] for wlan: [dec], Slot id: [dec] in [chars] direction with status: [chars] |
SSID policy bind operation failed. |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-3-QOS_SSID_POLICY_UNBIND_ON_AP_FAIL |
3-Error |
ERROR: Failed to unbind SSID policy on AP: [chars] for wlan: [dec], Slot id: [dec] in [chars] direction with status: [chars] |
SSID policy unbind operation on AP failed. |
ewlc-qos |
LOG_STD_ACTION |
QOS_ERROR_MESSAGE-6-QOS_HA_NO_BSSID_RECORD_SYNC_AP_DELETE |
6-Information |
Deleting AP %02x%02x.%02x%02x.%02x%02x because BSSID record sync for slotId [dec] wlan_id [dec] pm_dir [chars] failed |
QoS BSSID record sync pre-switchover failed. Hence deleting the AP. |
ewlc-qos |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-ALL_SOURCE_PORT_EXHAUSTED |
3-Error |
[chars] : Dynamic socket pool limit reached Max : [dec] |
All Source ports are exhausted |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-ALL_SOURCE_PORT_EXHAUSTED_AFTER_CLEANUP |
3-Error |
[chars] : Dynamic socket pool limit is still at Maximmum [dec] after clean up |
All Source port are exhausted even after cleanup |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-BUFFER_OVERFLOW |
3-Error |
Radius I/O buffer has overflowed for [chars] with length [dec] |
An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer. |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-RADIUS_PARSE_FAIL |
3-Error |
Radius Parse FAIL due to op decode/bad packet |
When Radius Parse response op decode/bad packet |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-RADIUS_TIMER_FAILED_TO_START |
3-Error |
Failed to start radius timer. |
Radius timer failed to start |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-RADIUS_TIMER_FAILED_TO_STOP |
3-Error |
Failed to stop radius timer. |
Radius timer failed to stop |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-SECRETDEFINEFAILED |
3-Error |
Key definition ignored. |
The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved. |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-3-SOCKET_OPERATION_FAILURE |
3-Error |
Cannot open UDP socket for service [chars] |
The router is unable to open a socket for UDP communications by the indicated service. Most of the time another service might be using the same port. |
polaris-aaa |
LOG_STD_ACTION |
RADIUS_AUDIT_MESSAGE-6-ALLDEADSERVER |
6-Information |
Group [chars]: No active radius servers found. Id [dec]. |
This error message occurs when all the servers configured in a server group are found to be unresponsive. |
polaris-aaa |
LOG_STD_NO_ACTION |
RADIUS_AUDIT_MESSAGE-6-BADATTRLIST |
6-Information |
Unable to process attribute list. |
The attribute list is syntactically incorrect. |
polaris-aaa |
LOG_STD_NO_ACTION |
RADIUS_AUDIT_MESSAGE-6-INVALID_PACKET |
6-Information |
Invalid packet posted to RADIUS. |
Radius not able to process a packet as it is invalid |
polaris-aaa |
LOG_STD_NO_ACTION |
RADIUS_AUDIT_MESSAGE-6-RADIUS_ALIVE |
6-Information |
RADIUS server [chars]:[dec],[dec] is being marked alive. |
A RADIUS server that previously was not responding has responded to a new request or the deadtimer has expired. |
polaris-aaa |
LOG_STD_NO_ACTION |
RADIUS_AUDIT_MESSAGE-6-RADIUS_DEAD |
6-Information |
RADIUS server [chars]:[dec],[dec] is not responding. |
The server might not be available to serve request. server has not responded to repeated requests. |
polaris-aaa |
LOG_STD_NO_ACTION |
RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_DTLSC_DTLS_REPLAY_ATTACK |
3-Error |
DTLS replay attack for hostname: [chars] |
Detected DTLS replay attack |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_DTLSC_EXT_2_DTLS_SESSION_ESTABLISHED_FAILURE |
3-Error |
User ID: [chars] Failure to establish a DTLS session with RadSec server, reason: [chars] |
Failure to establish a DTLS session with RadSec server |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_RADSEC_SERVER_CERTIFICATE_VALIDATION_FAILURE |
3-Error |
RADSEC server certificate validation failed with server [chars] |
RADSEC server certificate validation failed |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_RADSEC_SERVER_IDENTITY_CHECK_FAILURE |
3-Error |
RADSEC server identity check failed with server [chars] |
RADSEC server identity Check failed |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_TLSC_EXT_2_TLS_SESSION_ESTABLISHED_FAILURE |
3-Error |
User ID: [chars] Failure to establish a TLS session with RadSec server, reason: [chars] |
Failure to establish a TLS session with RadSec server |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSC_DTLS_NEGOTIATED_CIPHER |
6-Information |
Negotiated Cipher is [chars] |
Negotiated Cipher during RADSEC HS SUCCESS |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSC_DTLS_SESSION_CLOSED |
6-Information |
RADSEC DTLS connection closed with peer [chars] |
RADSEC DTLS connection closed |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSC_DTLS_SESSION_ESTABLISHED |
6-Information |
RADSEC DTLS connection established with peer [chars] |
DTLS session established message after RADSEC HS SUCCESS |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_TLSC_TLS_SESSION_CLOSED |
6-Information |
RADSEC TLS connection closed with peer [chars] |
RADSEC TLS connection closed |
ewlc-qos |
LOG_STD_ACTION |
RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_TLSC_TLS_SESSION_ESTABLISHED |
6-Information |
RADSEC TLS connection established with peer [chars] |
TLS session established message after RADSEC HS SUCCESS |
ewlc-qos |
LOG_STD_ACTION |
REGISTRY-3-FASTCASE_OUT_OF_BOUNDS |
3-Error |
Attempt made in [chars] to register with out of bounds key |
In the FASTCASE registry the key has to be smaller than the size specified when the registry was created. This message indicates that an attempt was made to register with a key which is out of bounds. |
iosxe-binos-utils |
LOG_STD_ACTION |
REGISTRY-3-SEQ_LIST_OVERWRITE |
3-Error |
Attempt to overwrite a set sequence function ([chars]) |
A single function can be set as a callback for a specified sequence number for a sequenced list registry. This message indicates that an attempt to set a new callback has failed because a callback function has already been set for this sequence number. |
iosxe-binos-utils |
LOG_STD_ACTION |
REGISTRY-3-STUB_CHK_OVERWRITE |
3-Error |
Attempt made to overwrite a set stub function in [chars] |
A single function can be set as a callback for when a stub with check registry is invoked. This message indicates that an attempt to set a new callback has failed because a callback function has already been set. |
iosxe-binos-utils |
LOG_STD_ACTION |
RFMGR_SYSLOG-4-DCA_CHANNEL_LIST_EMPTY |
4-Warning |
The DCA Channel list is empty for rf profile [chars] |
DCA Channel list is empty It affects Channel Assignment to AP |
ewlc-rrm |
Please add channels to DCA List |
RFMGR_SYSLOG-4-MULTI_BSSID_PROFILE_NOT_FOUND |
4-Warning |
Invalid Multi bssid profile [chars], applying default-multi-bssid-profile |
Invalid multi-bssid-profile is applied, 802.11ax specific payloads are not pushed to AP |
ewlc-rrm |
Please assign a valid Multi bssid profile |
RFMGR_SYSLOG-4-NO_REM_NON_AUTO_RF_CHAN_DCA |
4-Warning |
WARNING: RF Profile [chars] - Deleting channel [dec] from remove channel list, please add the channel to allowed channel list directly for adding it to DCA Used/Allowed channel list. |
Deleting channel from remove channel list adds it to DCA Used/Allowed channel list, but the right way of adding a channel to DCA Used/Allowed channel list is to add the channel directly to allowed channel list by not adding it to remove channel list and then deleting. |
ewlc-rrm |
Please add the channel directly to allowed channel list for making it part of DCA Used/Allowed channel list |
RIF_MGR_FSM-6-GW_REACHABLE_ACTIVE |
6-Information |
Gateway reachable from Active |
Gateway reachable from Active |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-GW_REACHABLE_STANDBY |
6-Information |
Gateway reachable from Standby |
Gateway reachable from Standby |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-GW_UNREACHABLE_ACTIVE |
6-Information |
Gateway not reachable from Active |
Gateway not reachable from Active |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-GW_UNREACHABLE_STANDBY |
6-Information |
Gateway not reachable from Standby |
Gateway not reachable from Standby |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_ACTIVE_RECOVERY_MODE |
6-Information |
Going to Active(Recovery) from Active state |
Going to Active(Recovery) From Active |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_GW_DECISION_DEFERRED |
6-Information |
High CPU utilisation on active or standby, deferring action on gateway-down event |
High CPU utilisation on active or standby, deferring action on gateway-down event |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_LINK_DOWN |
6-Information |
The RMI link is DOWN. |
The redundancy mgmt intf link was down. |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_LINK_UP |
6-Information |
The RMI link is UP. |
The redundany mgmt intf link came up |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_STBY_REC_TO_STBY |
6-Information |
Going from Standby(Recovery) to Standby state |
Going from Standby(Recovery) to Standby on GW reachable |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_STBY_TO_STDBY_REC |
6-Information |
Going from Standby to Standby(Recovery) state |
Going from Standby to Standby(Recovery) on GW unreachable |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_STBY_TO_STDBY_REC_REASON |
6-Information |
Going from Standby to Standby(Recovery) state, Reason: [chars] |
Going from Standby to Standby(Recovery) on RP Down event |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RMI_STDBY_REC_TO_ACTIVE |
6-Information |
Going from Standby(Recovery) to Active state |
Going from Standby(Recovery) to Active on RP DOWN |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RP_LINK_DOWN |
6-Information |
Setting RP link status to DOWN |
RP link status set to DOWN |
ewlc-ha |
No action is required |
RIF_MGR_FSM-6-RP_LINK_UP |
6-Information |
The RP link is UP. |
The redundany port link came up |
ewlc-ha |
No action is required |
RLDP_INITIATE_MESSAGE-6-EWLC_RLDP_INITIATE |
6-Information |
RLDP initiate [chars] |
General ewlc RLDP initiate startup status |
iosxe-binos-utils |
LOG_STD_ACTION |
RM_ERRS-2-ERR_FREE_MEM_CRITICAL |
2-Critical |
Insufficient free memory for service to work: [dec] |
Insufficient free memory for service to handle new connection. |
polaris-htx |
Disable not required features. |
RM_ERRS-4-ERR_INSUFFICIENT_FREE_MEM |
4-Warning |
Insufficient free memory [dec] |
Free memory is lesser than configured for service. |
polaris-htx |
Disable not required features. |
RM_ERRS-6-ERR_RECOVERED_FREE_MEM |
6-Information |
Recovered, sufficient free memory available [dec] |
Required free memory is available now for the service. |
polaris-htx |
No action is requried |
ROGUE_SYSLOG-6-ADHOC_AUTOCONTAIN |
6-Information |
Adhoc rogue AP with MAC address [chars] has been automatically contained as per WPS policies. |
Adhoc Rogue has been automatically contained |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ADHOC_AUTOCONTAIN_CLEAR |
6-Information |
Auto-containment for adhoc rogue AP with MAC address [chars] has been stopped. |
Adhoc Rogue auto-containment has been stopped |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_AUTOCONTAINED |
6-Information |
Rogue AP with MAC address [chars] has been automatically contained as per WPS policies |
Rogue AP has been auto-contained |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_AUTOCONTAINED_CLEARED |
6-Information |
Automatic containment for rogue AP with MAC address [chars] has been cleared. |
Rogue AP autocontainment has been stopped |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_BEING_CONTAINED |
6-Information |
Managed AP [chars] with radio MAC [chars] slot [dec] is contained by another AP. |
A managed AP is contained by another AP |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_BEING_CONTAINED_CLEAR |
6-Information |
Managed AP [chars] with radio MAC [chars] slot [dec] is no longer contained by another AP. |
A managed AP is no longer contained by another AP |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_CONTAINED_BY_RULE |
6-Information |
Rogue AP with MAC address [chars] has been contained due to rule [chars] with containment level [dec] |
Rogue AP has been contained due to a rule match |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_HONEYPOT |
6-Information |
Potential Honeypot AP detected with Rogue AP MAC [chars] with SSID [chars] by AP with Radio MAC [chars], slot [dec]. |
Potential Honeypot AP detected |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_HONEYPOT_CLEAR |
6-Information |
Potential Honeypot AP MAC address [chars] is cleared. This Rogue AP is no longer advertising an SSID that is configured on this controller. |
Potential Honeypot AP cleared |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-AP_IMPERSONATION |
6-Information |
Impersonation of AP with Radio MAC [chars] using source MAC address [chars] has been detected by AP [chars] with Radio MAC [chars], Slot [dec] |
AP impersonation attack has been detected |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-MAX_NUM_ROGUE_AP |
6-Information |
Rogue AP count for the system has reached the maximum limit of [dec] entries. |
Rogue AP maximum scale has been reached |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-MAX_NUM_ROGUE_AP_CLEAR |
6-Information |
Rogue AP count for the system is within the limit of [dec] entries. |
Number of Rogue APs is below system limit |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-MAX_ROGUE_PER_AP |
6-Information |
The average number of Rogue APs per detecting AP radio has crossed the threshold of [dec] on AP [chars] with radio MAC [chars]. |
The average number of Rogue APs per detecting AP radio has crossed the threshold. |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-MAX_ROGUE_PER_AP_CLEAR |
6-Information |
The average number of Rogue APs per detecting AP radio is below the threshold of [dec] on AP [chars] with radio MAC [chars]. |
The average number of Rogue APs per detecting AP radio is below the threshold. |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-RLDP_ASSOC_FAIL |
6-Information |
RLDP failed with error code [dec] while trying to associate to Rogue AP [chars] using AP [chars] with Radio MAC [chars], slot [dec]. |
RLDP failed while trying to associate to Rogue AP |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ROGUE_AP_CLEARED |
6-Information |
Rogue AP [chars] removed from Radio MAC [chars], Slot [dec] |
The Rogue AP has been removed |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ROGUE_AP_DETECTED |
6-Information |
Rogue AP [chars] detected on Radio MAC [chars], Slot [dec], band [chars], Channel [dec], RSSI [dec], SNR [dec], Classification: [chars], State: [chars][chars] |
A new Rogue AP has been detected |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ROGUE_AP_ON_WIRED_NETWORK |
6-Information |
Rogue AP with MAC address [chars] has been detected on the wired network. |
A Rogue AP has been detected on the wired network |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ROGUE_AP_ON_WIRED_NETWORK_CLEAR |
6-Information |
Rogue AP with MAC address [chars] is no longer on the wired network. |
Rogue AP is not anymore on the wired network |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ROGUE_CLIENT_DETECTED |
6-Information |
Rogue client with MAC address [chars] has been detected by [dec] APs, rogue client BSSID [chars], state [chars], last detecting AP [chars], rogue client gateway MAC [chars]. |
Rogue client detected |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ROGUE_CLIENT_THRESHOLD_CLEAR |
6-Information |
Rogue Client [chars] removed from Rogue AP [chars], state [chars], channel [dec], detected by AP [chars], slot [dec], current channel [dec], band [chars]. Rogue client count is now below the threshold for this Rogue AP. |
Number of rogue clients per Rogue AP is below the threshold |
ewlc-wips |
LOG_STD_NO_ACTION |
ROGUE_SYSLOG-6-ROGUE_CLIENT_THRESHOLD_EXCEED |
6-Information |
Rogue Client count threshold exceeded for Rogue AP [chars] by client address [chars] detected by AP [chars], slot [dec], current channel [dec], band [chars], state [chars], rogue AP channel [dec]. |
Number of rogue clients per Rogue AP threshold has been exceeded |
ewlc-wips |
LOG_STD_NO_ACTION |
ROMMON-5-CPLD_UPGRADE_STATUS |
5-Notice |
CPLD upgrade: [chars], install-id: [chars], message: [chars] |
This syslog provides the result of the CPLD upgrade |
cedge-srvcability |
No action is required |
ROMMON-5-ROMMON_UPGRADE_STATUS |
5-Notice |
ROMMON upgrade: [chars], install-id: [chars], message: [chars] |
This syslog provides the result of the ROMMON upgrade |
cedge-srvcability |
No action is required |
RRM_CLIENT-0-FAILEDTIMERCREATE |
0-Emergency |
RRM failed to create [chars] timer |
Failed to create timer |
ewlc-rrm |
LOG_STD_ACTION |
RRM_CLIENT-3-CHD_INV_RF_PROF |
3-Error |
Coverage message received profile from [chars] |
CHD message was received for a radio which has a non existent RF Profile Configured. |
ewlc-rrm |
Can be seen during configuration changes,if seen otherwise LOG_STD_ACTION |
RRM_CLIENT-3-EWLC_EXEC_ERR |
3-Error |
%% Error: AP [chars] MAC: %02x%02x.%02x%02x.%02x%02x Slot-id [dec] - [chars] |
Improper arguments or config |
ewlc-rrm |
Arguments to be changed |
RRM_CLIENT-3-FAILEDCOVERAGEPROFILE |
3-Error |
Coverage profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Failed client count: [dec] Total client count: [dec] |
Coverage profile violation |
ewlc-rrm |
LOG_STD_ACTION |
RRM_CLIENT-3-FAILEDINTPROFILE |
3-Error |
Interference profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Interference in percentage: [dec] On channel: [dec] |
Interference profile violation |
ewlc-rrm |
LOG_STD_ACTION |
RRM_CLIENT-3-FAILEDLOADPROFILE |
3-Error |
Load profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Channel load in percentage: [dec] Number of stations: [dec] |
Load profile violation |
ewlc-rrm |
LOG_STD_ACTION |
RRM_CLIENT-3-FAILEDNOISEPROFILE |
3-Error |
Noise profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Noise: [dec] dBm On channel: [dec] |
Noise profile violation |
ewlc-rrm |
LOG_STD_ACTION |
RRM_CLIENT-3-HA_CONFIG_SYNC |
3-Error |
RRM HA Config tables not yet synced: [chars] |
Some critical RRM configuration was found to be missing, immediately after switchover. |
ewlc-rrm |
If the message appears persistently, RRM may not function as configured. System reboot will be required to restore RRM function |
RRM_CLIENT-3-RRM_AP_DB_ERR |
3-Error |
Unable to find AP %02x%02x.%02x%02x.%02x%02x entry in the database, could not process [chars] |
The operation being performed for the AP failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller. |
ewlc-rrm |
Use the 'show ap summary' command to determine if the AP is still joined to the controller. If it is not, the message may be ignored. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs. |
RRM_CLIENT-3-RRM_AP_INV_SLOT |
3-Error |
Invalid slot number [dec] for AP %02x:%02x:%02x:%02x:%02x:%02x could not process [chars] |
AP included wrong slot number |
ewlc-rrm |
LOG_STD_ACTION |
RRM_CLIENT-3-RRM_AP_TBL_ERR |
3-Error |
Unable to find AP %02x%02x.%02x%02x.%02x%02x slot [dec] [chars] entry in the database, could not process [chars] event |
The operation being performed for the AP failed because the measurement or coverage entry for the radio was not found. recreating the records. |
ewlc-rrm |
Collect the controller logs and contact technical assistance. |
RRM_CLIENT-3-RRM_CHANNEL |
3-Error |
RRM Channel Config Notification: Radio Role is AUTO. So, channel change is not allowed for AP [chars] on slot [dec]. |
Channel configuration is not allowed. |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-3-RRM_CONFIG |
3-Error |
RRM Config Notification: [chars] |
Some critical RRM configuration still not populated. |
ewlc-rrm |
If the message appears persistently, for more than 8 times for each phy type, RRM may not function as configured. System reboot will be required to restore RRM function |
RRM_CLIENT-5-PASSEDCOVERAGEPROFILE |
5-Notice |
Coverage profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] |
Coverage profile recovery |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-5-PASSEDINTPROFILE |
5-Notice |
Interference profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x: Slot: [dec] |
Interference profile recovery |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-5-PASSEDNOISEPROFILE |
5-Notice |
Noise profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] |
Noise profile recovery |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-5-RRM_CAC_IN_PROG |
5-Notice |
AP [chars] slot [dec] [chars] is deferred, till pre-CAC is complete |
Setting channel/channel width/channel mode are deferred until pre-CAC is done. |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-5-RRM_NON_PSC_CHANNEL |
5-Notice |
RRM Channel Config Notification: Non-PSC channel [dec] is configured for 6 GHz radio on slot [dec], Clients might fail to connect. |
When non PSC channel is used for 6GHz radio, it is possible that 6GHz clients may not be able to join the AP. |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-6-MODE_SWITCH_LPI_TO_SP |
6-Information |
6GHZ Power mode switch from LPI to SP AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Channel: [dec] Channel Width: [dec] |
6GHZ Power mode switch from LPI to SP |
ewlc-afc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-6-MODE_SWITCH_SP_TO_LPI |
6-Information |
6GHZ Power mode switch from SP to LPI AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Channel: [dec] Channel Width: [dec] |
6GHZ Power mode switch from SP to LPI |
ewlc-afc-rrm |
LOG_STD_NO_ACTION |
RRM_CLIENT-6-PASSEDLOADPROFILE |
6-Information |
Load profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] |
Load profile recovery |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_COMMON_TRACE_MESSAGE-3-RRM_COMMON_INVALID_SLOT |
3-Error |
Error encountered: [chars] |
Invalid slot identifier is found while processing RRM packet |
ewlc-rrm |
Please report the error to technical support representative |
RRM_MGR_DB-5-DUPLICATE_IP_WLC |
5-Notice |
WLC: [chars] having duplicate IP: [dec].[dec].[dec].[dec] detected while processing RRM pkt. IP address of the conflicting WLC: [chars] should be changed immediately to avoid impact on RRM functionality |
Another WLC in the rf-network is having duplicate IP, it will impact RRM functionality for the conflicting controllers |
ewlc-rrm |
IP address of the conflicting controller should be changed immediately |
RRM_MGR_TRACE_MESSAGE-0-FAILEDTIMERCREATE |
0-Emergency |
RRM failed to create [chars] timer |
Failed to create timer |
ewlc-rrm |
LOG_STD_ACTION |
RRM_MGR_TRACE_MESSAGE-3-EWLC_EXEC_ERR |
3-Error |
%% Error: [chars] |
Improper arguments or config |
ewlc-rrm |
Arguments to be changed |
RRM_MGR_TRACE_MESSAGE-3-EWLC_GEN_ERR |
3-Error |
Error in [chars] |
General ewlc Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
RRM_MGR_TRACE_MESSAGE-3-HA_CONFIG_SYNC |
3-Error |
RRM HA Config tables not yet synced: [chars] |
Some critical RRM configuration was found to be missing, immediately after switchover. |
ewlc-rrm |
If the message appears persistently, RRM may not function as configured. System reboot will be required to restore RRM function |
RRM_MGR_TRACE_MESSAGE-3-REG_IP_CHG_NOTIFY_FAIL |
3-Error |
Unable to register with platform to get Management IP Address Change Notification - error [dec]. |
Unable to register with platform to get Management Interface IP Address Change Notification. |
ewlc-rrm |
LOG_STD_ACTION |
RRM_MGR_TRACE_MESSAGE-3-REG_RX_PKT_FAIL |
3-Error |
Unable to register with platform to receive packets - error [dec] |
Unable to register with platform to receive packets |
ewlc-rrm |
LOG_STD_ACTION |
RRM_MGR_TRACE_MESSAGE-3-RRM_IPC_EP_ERR |
3-Error |
IPC Failure: [chars] |
Failed to find IPC endpoint for AP |
ewlc-rrm |
If the message appears persistently, RRM will not function as expected. AP should be disconnected to restore RRM function |
RRM_MGR_TRACE_MESSAGE-5-RRM_DUPLICATE_IP_WLC |
5-Notice |
WLC: [chars] having duplicate IP: [chars] detected while processing RRM Hello pkt. IP address of the conflicting WLC: [chars] should be changed immediately to avoid impact on RRM functionality |
Another WLC in the rf-network is having duplicate IP, it will impact RRM functionality for the conflicting controllers |
ewlc-rrm |
IP address of the conflicting controller should be changed immediately |
RRM_UTIL-4-INVALIDCHANNELCONFIG |
4-Warning |
Warning: Update of the channel list caused invalid pair in DCA list for [chars] band |
Invalid channel configuration |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_UTIL-6-SETCHANNEL |
6-Information |
Set channel on cell %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] chanwidth [dec] to reduce co-channel interference from [dec] to [dec] Reason [chars] |
Set channel to reduce co-channel interference |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_UTIL-6-SETCHANNELWIDTH |
6-Information |
Set channel width on 802.11a for AP %02x%02x.%02x%02x.%02x%02x: failed 160MHz channel width supported only for 4x4 antenna mode |
Channel width configuration change |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_UTIL-6-SETCHANNEL_DUALBAND |
6-Information |
Set channel [chars] for AP %02x%02x.%02x%02x.%02x%02x on dual band radio slot: [dec] due to [chars] |
Set channel because of Dualband Radio Role/band change |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_UTIL-6-SETCHANNEL_ED |
6-Information |
Set channel on cell %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] due to Air Quality voilation reason [chars] |
Set channel because of Air Quality Violation |
ewlc-rrm |
Investigate the cause of bad air quality on the channel and eliminate if possible |
RRM_UTIL-6-SETCHANNEL_NONOPTIMAL |
6-Information |
Set non-optimal channel on cell %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] because of lack of information |
Set channel on user input (non-optimal) |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_UTIL-6-SETTXPOWER |
6-Information |
Tx power changed from [dec] to [dec] for AP %02x%02x.%02x%02x.%02x%02x slot [dec] band [chars] due to [chars] |
Set transmit power |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_UTIL-6-UPDATECHANNEL |
6-Information |
Set channel on [chars] AP %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] by configuration change due to [chars] |
Channel configuration change |
ewlc-rrm |
LOG_STD_NO_ACTION |
RRM_UTIL-6-UPDATETXPOWER |
6-Information |
Tx power changed from [dec] to [dec] for AP %02x%02x.%02x%02x.%02x%02x slot [dec] band [chars] due to [chars] |
Transmit power configuration change |
ewlc-rrm |
LOG_STD_NO_ACTION |
RULE_ENGINE-3-EWLC_GEN_ERR |
3-Error |
Error in [chars] |
General Wireless LAN Controller Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
RULE_ENGINE-3-EWLC_RULE_ENGINE_REGEX_CREATE_ERR |
3-Error |
Error in [chars] |
Rule regular expression error |
iosxe-binos-utils |
Recreate regular expression correctly |
RULE_ENGINE-4-EWLC_RULE_ENGINE_PRIORITY_UPDATE_WARN |
4-Warning |
Warning: [chars] |
rule_engine priorities are overridden, old rule_engine will be invalid |
iosxe-binos-utils |
LOG_STD_ACTION |
SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR |
0-Emergency |
Reloading [chars] due critical event %#x in block [chars]/[dec] of serial bridge [dec] |
A critical serial bridge I/O event has occurred. |
asr1k-infra-intrnl |
The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR_RATE |
0-Emergency |
Reloading [chars] due to critically high serial bridge error rate. |
A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect. |
asr1k-infra-intrnl |
Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
SCOOBY-0-SERIAL_BRIDGE_DRIVER_ERROR |
0-Emergency |
Kernel Module failed in [chars] |
A Serial Bridge has experienced a Init failure. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect. |
asr1k-infra-intrnl |
Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
SCOOBY-2-FPGA_VERSION_CHECK_ERR |
2-Critical |
LEDA FPGA version does not meet minimum required version. [chars] |
LEDA FPGA minimum version requirement not met. |
asr1k-ether-lc |
Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
SCOOBY-5-SERIAL_BRIDGE_BLOCK_EVENT |
5-Notice |
Block [chars]/[dec] of serial bridge [dec] had I/O event %#x |
A serial bridge I/O event has occurred. This event is not serious but is logged for diagnostic purposes. |
asr1k-infra-intrnl |
No user action is required. |
SCOOBY-5-SERIAL_BRIDGE_EVENT_RATE |
5-Notice |
The [chars] event rate of [dec] has exceeded the threshold of [dec] on serial bridge [dec] interconnect [dec] |
A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect. |
asr1k-infra-intrnl |
No user action is required. If this message persists, a serial bridge critical message that needs to be addressed will appear. |
SERDES-3-SERDES_CRITICAL_ERROR |
3-Error |
Critial error [chars] in FRU [chars] when [chars] |
A critical error was occurred. The condition is serious and the card must be reloaded. This could be due to bad or unknown hardware (chassis or modules). Chassis Manager could also initialize the Serdes library with incorrect input parameters. |
asr1k-infra-intrnl |
Copy the message exactly as it appears on the console or in the system log. Collect the output of show platform, show verson, show log, sh diag chassis eeprom detail, show diagnostic slot <slot#> eeprom detail, and any other relevant logs. Contact your Cisco technical support representative. |
SERDES-5-SERDES_NOTICE |
5-Notice |
from FRU [chars], [chars]. |
CMAN sends a significant Serdes event to IOSD to log it |
asr1k-infra-intrnl |
No action is required for this notice. |
SERVICES-0-INVALID_OWNERSHIP |
0-Emergency |
Error using service handle %p - invalid ownership (%p, %p) |
A multi-thread application is trying to incorrectly use the services library. Applications must follow thread confinement strategy with the services library. Each thread of the application must initialize private managed context of the service library. |
iosxe-binos-utils |
Copy the error message, tracebacks and version information and contact a Cisco representative. |
SERVICES-2-NOINIT |
2-Critical |
Error initializing services: [chars] |
An application failed to initialize the core services library. The application will not be able to communicate with other modules on the system. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
SERVICES-2-NORESOLVE_ACTIVE |
2-Critical |
Error resolving active FRU: [chars] |
An application was not able to determine the active FRU. The application was likely started incorrectly. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
SERVICES-2-NORESOLVE_LOCAL |
2-Critical |
Error resolving local FRU: [chars] |
An application was not able to determine its local FRU. The application was likely started incorrectly. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
SERVICES-2-NORESOLVE_STANDBY |
2-Critical |
Error resolving standby FRU: [chars] |
An application was not able to determine the standby FRU. The application was likely started incorrectly. |
iosxe-binos-utils |
LOG_STD_RECUR_ACTION |
SERVICES-3-INVALID_CHASFS |
3-Error |
Thread %p has no global chasfs context |
A multi-thread application is trying to incorrectly use the services library. Applications must follow thread confinement strategy with the services library. Each thread of the application must initialize private managed context of the service library. |
iosxe-binos-utils |
Copy the error message, tracebacks and version information and contact a Cisco representative. |
SESSION_MGR-0-CONFIG_CORRUPT |
0-Emergency |
Checksummed interface configuration corruption detected. |
Interface configuration field was modified unexpectedly. |
polaris-smd |
No action is required. |
SESSION_MGR-4-ILLEGAL_TRACE_REQ |
4-Warning |
Component ID [dec] not registered. |
Component ID %d not registered. |
polaris-smd |
No action is required. |
SESSION_MGR-4-TERMINATE |
4-Warning |
Authentication session terminated for client ([chars]) on Interface [chars] AuditSessionID [chars] Reason [chars] |
Session is being terminated. |
polaris-smd |
No action is required. |
SESSION_MGR-4-UNAUTH_MOVE |
4-Warning |
[chars] MAC address ([chars]) from [chars] to [chars] |
Move while not authenticated on old IDB |
polaris-smd |
No action is required. |
SESSION_MGR-5-FAIL |
5-Notice |
Authorization failed or unapplied for client ([chars]) on Interface [chars] AuditSessionID [chars]. [chars] [chars] |
Authorization was unsuccessful. |
polaris-smd |
Authorization was unsuccessful for the client. Collect the smd logs and system console logs |
SESSION_MGR-5-MACMOVE |
5-Notice |
MAC address ([chars]) moved from Interface [chars] to Interface [chars] AuditSessionID [chars] |
Client has moved to a new interface without logging off on the previous one. |
polaris-smd |
No action is required. |
SESSION_MGR-5-MACREPLACE |
5-Notice |
MAC address ([chars]) on Interface [chars] is replaced by MAC ([chars]) AuditSessionID [chars] |
A new client has triggered a violation causing an existing client to be replaced |
polaris-smd |
No action is required. |
SESSION_MGR-5-SECURITY_VIOLATION |
5-Notice |
Security violation on the interface [chars], new MAC address ([chars]) is seen. AuditSessionID [chars] |
A host on the specified interface is attempting to gain access into the network or is trying to authenticate in a host mode that does not support the number of hosts attached. This is treated as a security violation and the port has been error-disabled. |
polaris-smd |
Ensure that the port is configured to support the host count attached. Enter the <cmdbold>shutdown<nocmdbold> command followed by <cmdbold>no shutdown<nocmdbold> command to restart the port. |
SESSION_MGR-5-START |
5-Notice |
Starting '[chars]' for client ([chars]) on Interface [chars] AuditSessionID [chars] |
Starting an authentication method |
polaris-smd |
Message notification informing about the session manager client is being started to authenticate the endpoint attached to the interface |
SESSION_MGR-5-SUCCESS |
5-Notice |
Authorization succeeded for client ([chars]) on Interface [chars] AuditSessionID [chars] |
Authorization was successful. |
polaris-smd |
Client connected to the switch has been successfully authorized by the session manager framework |
SESSION_MGR-5-VLANASSIGN |
5-Notice |
VLAN [dec] assigned to Interface [chars] AuditSessionID [chars] |
VLAN assignment to an interface for the session |
polaris-smd |
No action is required. |
SESSION_MGR-7-NOMOREMETHODS |
7-Debug |
Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars] |
All available authentication methods have been tried |
polaris-smd |
No action is required. |
SESSION_MGR-7-STOPPING |
7-Debug |
Stopping [chars] for client [chars] on Interface [chars] AuditSessionID [chars] |
Stopping the current authentication method |
polaris-smd |
No action is required. |
SHFWD-6-PACKET_TRACE_DONE |
6-Information |
Packet Trace Complete: [chars] |
Packet trace cmd initiated by admin is complete |
polaris-platform_mgr |
No action is required |
SHFWD-6-PACKET_TRACE_FAIL |
6-Information |
Show fwd is failed at [chars] |
Packet trace cmd initiated by admin is fail |
polaris-platform_mgr |
Collect the trace from all the switch using the cli (show platform software trace fed switch <> ) |
SHFWD-6-PACKET_TRACE_FLOW_ID |
6-Information |
Packet Trace Flow id is [dec] |
Packet trace instance can be tracked by flowid |
polaris-platform_mgr |
No action is required |
SIF_MGR-1-FAULTY_CABLE |
1-Alert |
High hardware interrupt seen on switch [dec]\n |
The specified stack cable is experiencing high hardware interrupts |
iosxe-fwdmgr |
Replace the stack cable connected to the stack port. |
SIF_MGR-1-FAULTY_STACK_CABLE |
1-Alert |
High hardware interrupt seen on switch [dec] on stack port [dec]\n |
The specified stack cable is experiencing high hardware interrupts |
iosxe-fwdmgr |
Replace the stack cable connected to the stack port. |
SIF_MGR-6-STACK_ADAPTER_INSERTED |
6-Information |
stack_mgr: Stack adapter [dec] on switch [dec] is inserted |
The specific adapter has been inserted from the mentioned switch. |
iosxe-fwdmgr |
No action is required |
SIF_MGR-6-STACK_ADAPTER_REMOVED |
6-Information |
stack_mgr: Stack adapter [dec] on switch [dec] is removed |
The specific adapter has been removed from the mentioned switch. |
iosxe-fwdmgr |
No action is required |
SIG-2-SIG_TUNNEL_EVENT_FAILURE |
2-Critical |
Cisco Umbrella SIG tunnel: [chars] event failure, [chars] |
This syslog is generated when a IPSEC tunnel to Cisco Umbrella Secure Internet Gateway runs into failure(s) during state transition |
cedge-sig |
No action is required |
SIG-2-TUNNEL_TRACKER_STATUS_DOWN |
2-Critical |
Tracker associated with SIG tunnel [chars] is [chars] |
This syslog is generated when tracker(s) associated with SIG tunnel goes DOWN |
cedge-sig |
No action is required |
SIG-2-ZIA_LOCATION_EVENT_FAILURE |
2-Critical |
Zscaler location: [chars] event failure, [chars] (additional info: [chars]) |
This syslog is generated when various REST API(s) to setup ZIA encounter errors |
cedge-sig |
No action is required |
SIG-2-ZIA_TUNNEL_EVENT_FAILURE |
2-Critical |
Zscaler SIG tunnel: [chars] event failure, [chars] (additional info: [chars]) |
This syslog is generated when a IPSEC/GRE tunnel to Zscaler Secure Internet Gateway runs into failure(s) during state transition |
cedge-sig |
No action is required |
SIG-5-SIG_TUNNEL_EVENT_SUCCESS |
5-Notice |
Cisco Umbrella SIG tunnel: [chars] event success, [chars] |
This syslog is generated when a IPSEC tunnel to Cisco Umbrella Secure Internet Gateway transitions to different states successfully |
cedge-sig |
No action is required |
SIG-5-TUNNEL_TRACKER_STATUS_UP |
5-Notice |
Tracker associated with SIG tunnel [chars] is [chars] |
This syslog is generated when tracker(s) associated with SIG tunnel comes UP |
cedge-sig |
No action is required |
SIG-5-ZIA_LOCATION_EVENT_SUCCESS |
5-Notice |
Zscaler location: [chars] event success, [chars] |
This syslog is generated when various REST API(s) to setup ZIA location succeed |
cedge-sig |
No action is required |
SIG-5-ZIA_TUNNEL_EVENT_SUCCESS |
5-Notice |
Zscaler SIG tunnel: [chars] event success, [chars] |
This syslog is generated when a IPSEC/GRE tunnel to Zscaler Secure Internet Gateway transitions through different states successfully |
cedge-sig |
No action is required |
SIMULATION_ERRMSG-3-rw_err |
3-Error |
Cosim simualation failed to [chars] %zu bytes. ret: [chars] |
An error occurred during cosim rw operation. |
INVALID |
Check if Cima memory io socket is over subscribbed. |
SISF_LOG-3-SISF_TRACEBACK |
3-Error |
Error in [chars] |
General SISF Error Message. |
ewlc-sisf |
LOG_STD_ACTION |
SM-2-INITIALIZATION_FAILED |
2-Critical |
Session Manager initialization for [chars] failed. |
Initialization of session manager process failed. |
polaris-infra |
Review SM 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. |
SMAN-2-NO_MEMORY |
2-Critical |
Cannot allocate memory for an internal data structure |
An out-of-memory condition occurred when attempting to create an internal data structure. The daemon encountering the problem will exit, after which the process manager will restart. |
iosxe-shellmgr |
Check the log files for the associated daemon. Monitor processes for excessive memory consumption. |
SMAN-2-TDL_MESSAGE |
2-Critical |
Cannot construct an IPC message for library. The message name is [chars] and the reason is: [chars] |
A problem occurred while constructing a type definition language (TDL) message or setting a field in a TDL message. If the problem occurred during construction of a TDL message, the system is out of memory. If the problem occurred while setting a field in the TDL message, there is a library mismatch issue. |
iosxe-shellmgr |
Check [uipeer] ERR entries in the log files for message reporting problems. |
SMAN-3-CRDU_PATCH_REPLY_TIMEOUT |
3-Error |
Failed to receive patch response from peer process [chars] |
During patch operation the Shell Manager broadcasts a request to all affected processes (peers). If a peer does not respond in time then the patch process cannot be completed correctly |
polaris-crdu |
Check that the process(es) that failed to respond are still active and check their trace files for any potential errors that could prevent them from responding to a patch request in a timely manner |
SMAN-3-CRFT_CLEARCOUNTERS_REQUEST_FAIL |
3-Error |
CRFT clear counters request finished with one or more failures. Check tracelogs for further details. |
After a request to clear CRFT counters if any program reports an error or fails to respond within the timeout period this message will be emitted. |
polaris-crft |
Inspect btrace logs for information about which programs failed and why |
SMAN-3-CRFT_COLLECT_REQUEST_FAIL |
3-Error |
CRFT collection request finished with one or more failures. Check tracelogs for further details. |
After a request to collect CRFT data if any program reports an error or fails to respond within the timeout period this message will be emitted. |
polaris-crft |
Inspect btrace logs for information about which programs failed and why |
SMAN-3-CRFT_EXPORT_REQUEST_FAIL |
3-Error |
CRFT export request finished with one or more failures. Check tracelogs for further details. |
After a request to export CRFT data if an error or failure during the export stage occurs this message will be emitted. |
polaris-crft |
Inspect btrace logs for information about which operation failed and why |
SMAN-3-CRFT_RELOAD_REQUEST_FAIL |
3-Error |
CRFT reload request capture finished with one or more failures. Check tracelogs for further details. |
After a request to capture CRFT data on reload if an error or failure during the reload stage occurs this message will be emitted. |
polaris-crft |
Inspect btrace logs for information about which operation failed and why |
SMAN-3-CRFT_UNSUPPORTED_REMOTE_PATH_FAIL |
3-Error |
CRFT remote requested using an unsupported remote path. Check tracelogs for further details. |
After a request to remotely capture CRFT data an error or failure during the remote stage occurs this message will be emitted. |
polaris-crft |
Inspect btrace logs for information about which operation failed and why |
SMAN-3-CRFT_UNSUPPORTED_REMOTE_SCHEME_FAIL |
3-Error |
CRFT remote requested using an unsupported scheme. Check tracelogs for further details. |
After a request to remotely capture CRFT data an error or failure during the remote archive stage occurs this message will be emitted. |
polaris-crft |
Inspect btrace logs for information about which operation failed and why |
SMAN-3-CRFT_UNSUPPORTED_REMOTE_TAG_FAIL |
3-Error |
CRFT remote requested using an unsupported tag format. Check tracelogs for further details. |
After a request to remotely capture CRFT data an error or failure during the remote archive stage occurs this message will be emitted. |
polaris-crft |
Inspect btrace logs for information about which operation failed and why |
SMAN-3-HOSTINFO_MONITOR_FAILURE |
3-Error |
Error initializing host info monitoring: [chars] |
During initialization, the Shell Manager monitors changes to host-related information, such as the hostname. This error occurs if initialization fails. |
iosxe-shellmgr |
Check the Shell Manager trace file for related details. |
SMAN-3-HOSTINFO_READ_FAILURE |
3-Error |
Error reading host info ([chars]): [chars] |
During process startup and when changes occur, the Shell Manager reads host-related information, such as the hostname. This error occurs if there is a failure reading information. |
iosxe-shellmgr |
Check the Shell Manager trace file for related details. |
SMAN-3-INVALID_EPOCH_FILE |
3-Error |
An upgrade or installation has produced an invalid messaging configuration file [chars], [chars] |
During an upgrade or installation of a new package, an invalid messaging configuration file was produced. The file is either empty or has invalid permissions and cannot be read. |
iosxe-shellmgr |
Repeat the installation or upgrade. If the problem persists, revert to a previous known good package. |
SMAN-3-NO_CDL_FILE |
3-Error |
Could not access command definition file [chars]: [chars] |
During initialization, the Shell Manager loads a XML CDL file to load all the CLI structure. This file is for some reason not found. |
iosxe-shellmgr |
Check the Shell Manager trace file for related details. |
SMAN-3-PTL_RENDERER_FAILURE |
3-Error |
Rendering error with [chars].[chars]. Transform is missing or invalid for data. |
The Shell Manager process attempted to render a command response but the transformation failed due to an internal error. The failure may have been caused by a missing transform file or an included file cannot be found. The transformation may also fail if the data returned in the response is binary and has not been processed correctly. In this case, the rendering engine is unable to interpret the data resulting in a failure. The transformation may also fail if there is a mismatch of packages installed on the system. In this case, incompatible messages are exchanged between the Shell Manager and the daemon servicing the command request and incorrect data is passed to the rendering engine. |
iosxe-shellmgr |
This error indicates a configuration issue resulting from bad or mismatched packages. Review the Shell Manager trace files and log files. Uninstall, then reinstall, any new packages. |
SMAN-5-CRFT_CLEARCOUNTERS_REQUEST_SUCCESS |
5-Notice |
CRFT clear counters completed successfully. |
This message serves to inform the user of exactly when the clearcounters operation completes and they are no longer waiting for additional processes |
polaris-crft |
No action required. This message is expected |
SMAN-5-CRFT_COLLECT_REQUEST_INPROGRESS |
5-Notice |
CRFT collection already in progress. Please try again later |
CRFT collection is something that should happen infrequently so if there is already a collection request in progress we reject the incoming request and emit a message to the user informing them that their request is rejected. |
polaris-crft |
Try the request again later if necessary |
SMAN-5-CRFT_COLLECT_REQUEST_NOT_SUPPORTED |
5-Notice |
CRFT collection request not supported on peer [chars] |
Some processes may not support CRFT collection for any of a number of reasons. This message serves to alert the user so that they do not go searching for CRFT stats for the process in question and determine an error has occurred when they cannot find them |
polaris-crft |
None. Information only. |
SMAN-5-CRFT_COLLECT_REQUEST_SUCCESS |
5-Notice |
CRFT collection completed successfully. |
This message serves to inform the user of exactly when the collection completes and they are no longer waiting for additional processes |
polaris-crft |
No action required. This message is expected |
SMAN-5-CRFT_EXPORT_REQUEST_SUCCESS |
5-Notice |
CRFT export completed successfully. |
This message serves to inform the user of exactly when the export operation completes and they are no longer waiting for additional output/feedback |
polaris-crft |
No action required. This message is expected |
SMAN-5-CRFT_RELOAD_REQUEST_SUCCESS |
5-Notice |
CRFT reload collection completed successfully. |
This message serves to inform the user of exactly when the export operation completes and they are no longer waiting for additional output/feedback |
polaris-crft |
No action required. This message is expected |
SPECTRUM-3-EWLC_EXEC_ERR |
3-Error |
%% Error: AP %02x%02x.%02x%02x.%02x%02x: [chars] |
Improper configuration for dual band AP |
ewlc-rrm |
please check the requested configuration against ap type |
SS-2-INITIALIZATION_FAILED |
2-Critical |
Initialization of [chars] failed for IOx Secure Storage |
Initialization of IOx Secure storage process failed. |
polaris-infra |
Review ioxss 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. |
SSLMGR-0-ASYMMETRIC_KEY_FAIL |
0-Emergency |
Asymmetric key failure: [chars]. |
Asymmetric key failure. |
iosxe-ssl |
No action required - forwarding processor (ESP) rebooted automatically. |
SSLMGR-0-N2_VSERVER_FAIL |
0-Emergency |
Virtual server context failure: [chars]. |
Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted |
iosxe-ssl |
forwarding processor (ESP) is rebooted automatically. no action needed |
SSLMGR-0-SYMMETRIC_KEY_FAIL |
0-Emergency |
Symmetric key failure: [chars]. |
Symmetric key failure. |
iosxe-ssl |
No action required - forwarding processor (ESP) rebooted automatically. |
SSLMGR-3-N2_CONTEXT_FAIL |
3-Error |
Context failure: [chars]. |
Coprocessor context operation failed due to resource limit |
iosxe-ssl |
Monitoring required |
SSLMGR-5-GATEWAY_UPDOWN |
5-Notice |
sslvpn gateway : [chars] changed state to [chars] |
sslvpn gateway changed state |
iosxe-ssl |
ACTION_NONE_REQUIRED |
SSLVPNMGR-5-HTTP_REQUEST_NOT_AUTHORIZED |
5-Notice |
HTTP request without login cookie. [chars]\n |
This message indicates that HTTP request doesn't have valid login cookie and is not authorized to access the resource |
iosxe-ssl |
ACTION_NONE_REQUIRED |
SSLVPNMGR-5-LOGIN_AUTH_FAILED |
5-Notice |
Failed to contact authentication server. [chars]\n |
Authentication server is unavailable because it is down or unreachable |
iosxe-ssl |
Verify if routes are configured correctly to reach authentication and the server is configured correctly |
SSLVPNMGR-5-LOGIN_AUTH_PASSED |
5-Notice |
Authentication successful, user logged in. [chars]\n |
This message indicates that login authentication succeeded for user |
iosxe-ssl |
ACTION_NONE_REQUIRED |
SSLVPNMGR-5-LOGIN_AUTH_REJECTED |
5-Notice |
Failed to authenticate user credentials. [chars]\n |
Authentication server failed to validate credentials provided by the user to login under webvpn context |
iosxe-ssl |
Check username and password configured on authentication server |
SSLVPNMGR-5-SSL_CONNECT_OK |
5-Notice |
SSL/TLS connection successful with client [chars]\n |
This message indicates that SSL/TLS handshake with peer was successful |
iosxe-ssl |
ACTION_NONE_REQUIRED |
SSLVPNMGR-6-CONTEXT_MAX_USERS_LOGIN_DENIED |
6-Information |
Login denied for user [chars]. Max users exceeded for context [chars]\n |
This message indicates that user was denied to login because the the max users for the context has been exceeded |
iosxe-ssl |
Check the gateway configuration and reconfigure the maximum allowed users in the context |
SSLVPNMGR-6-GLOBAL_MAX_USERS_LOGIN_DENIED |
6-Information |
Login denied for user [chars]. Global max users limit reached\n |
This message indicates that user was denied to login because the the max users limit reached |
iosxe-ssl |
ACTION_NONE_REQUIRED |
SSLVPNMGR-6-SESSION_TERMINATE |
6-Information |
Session terminated. [chars]\n |
SSLVPN session was terminated |
iosxe-ssl |
ACTION_NONE_REQUIRED |
STACKMGR-1-DUAL_ACTIVE_CFG_MSG |
1-Alert |
Dual Active Detection [chars]\n |
Switch detected availability or unavailability of Dual Active Detection ports. |
iosxe-fwdmgr |
No action is required |
STACKMGR-1-EPA_MISMATCH |
1-Alert |
[chars]. The mis-match may caused by hardware failure or different EPA types.\n |
The Standby EPA mismatch with Active EPA. |
iosxe-fwdmgr |
Need to make them match |
STACKMGR-1-FATAL_ERR |
1-Alert |
Stack manager encountered an unrecoverable error. [chars]\n |
The stack manager process has encountered an unrecoverable error and the switch is being reloaded. |
iosxe-fwdmgr |
Please ensure valid switch numbers are being used. If you still believe there is an error in the system, please send the system report to a TAC representative |
STACKMGR-1-LIC_MISMATCH |
1-Alert |
License level is [chars] and needs to be upgraded to [chars] for Stackwise Virtual to function.\n |
Current Licnese level on active switch does not support Stackwise Virtual. |
iosxe-fwdmgr |
Need to be upgraded to supported license level |
STACKMGR-1-RELOAD |
1-Alert |
Reloading due to reason [chars]\n |
The specified switch has received a reload request and is being reloaded. |
iosxe-fwdmgr |
No action is required |
STACKMGR-1-RELOAD_REQUEST |
1-Alert |
Received reload request for [chars], reason [chars]\n |
The specified switches are being reloaded. |
iosxe-fwdmgr |
No action is required |
STACKMGR-1-STACK_MERGE_IGNORE |
1-Alert |
Stack Merge Ignored [chars]\n |
Switch detected multiple Active switches. But stack-merge is being ignored. |
iosxe-fwdmgr |
No action is required |
STACKMGR-4-SWITCH_ADDED |
4-Warning |
[chars] [dec] has been added to the stack.\n |
The specified switch has been added to the stack. |
iosxe-fwdmgr |
No action is required |
STACKMGR-4-SWITCH_REMOVED |
4-Warning |
[chars] [dec] has been removed from the stack.\n |
The specified switch has been removed from the stack. |
iosxe-fwdmgr |
No action is required |
STACKMGR-5-CHASSIS_ROLE_UPDATE_FAIL |
5-Notice |
Failed to Set [chars] Chassis [dec] chassis_role [chars] |
This is used to indicate that update to new role failed |
iosxe-fwdmgr |
This is a rare failure condition. Please reach out to TAC |
STACKMGR-5-FAST_RELOAD_DONE |
5-Notice |
Fast reload operation completed successfully on entire stack |
This is used to indicate that the fast reload on stack is complete. |
accsw-p-fsu |
No action needed. This is not an error. |
STACKMGR-6-ACTIVE_ELECTED |
6-Information |
[chars] [dec] has been elected ACTIVE.\n |
The specified switch has been elected active. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-ACTIVE_READY |
6-Information |
Active [chars] [dec] is ready.\n |
The active switch is ready. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-CHASSIS_ADDED |
6-Information |
[chars] [dec] has been added to the stack.\n |
The specified chassis has been added to the stack. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-CHASSIS_READY |
6-Information |
[chars] [dec] is ready.\n |
The specified chassis is ready. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-CHASSIS_REMOVED |
6-Information |
[chars] [dec] has been removed from the stack.\n |
The specified chassis has been removed from the stack. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-CHASSIS_REMOVED_KA |
6-Information |
[chars] [dec] has been removed from the stack due to keepalive failure. \n |
Chassis has been removed due to the keepalive failure. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-DISC_DONE |
6-Information |
[chars] [dec] has finished stack discovery.\n |
The specified switch has completed stack discovery and is moving to the election phase. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-DISC_START |
6-Information |
[chars] [dec] is starting stack discovery.\n |
The specified switch is starting stack discovery. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-KA_MISSED |
6-Information |
Keepalive missed for [dec] times for [chars] [dec] \n |
Chassis has been removed due to the keepalive failure. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-STACK_LINK_CHANGE |
6-Information |
Stack port [dec] on [chars] [dec] is [chars]\n |
The specified stack port has changed status. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-STANDBY_ELECTED |
6-Information |
[chars] [dec] has been elected STANDBY.\n |
The specified switch has been elected standby. |
iosxe-fwdmgr |
No action is required |
STACKMGR-6-SWITCH_READY |
6-Information |
[chars] [dec] is ready.\n |
The specified switch is ready. |
iosxe-fwdmgr |
No action is required |
SUBSYS-3-SUBSYS_CLASS |
3-Error |
[chars] subsystem [chars] has class [chars] |
The task has detected a subsystem which has an unsupported class in its header. |
iosxe-binos-utils |
LOG_STD_ACTION |
SUBSYS-3-SUBSYS_RECURSION |
3-Error |
[chars] subsystem [chars] maxiumum sequence depth [dec] exceeded |
The task has detected that a subsystem upon insertion has exceeded the depth of insertion. |
iosxe-binos-utils |
LOG_STD_ACTION |
SUBSYS-3-SUBSYS_VERSION |
3-Error |
[chars] subsystem [chars] has unsupported version: [dec] |
The task has detected a subsystem which has an unsupported version in its header. |
iosxe-binos-utils |
LOG_STD_ACTION |
SUBSYS-6-SUBSYS_SEQUENCE |
6-Information |
[chars] subsystem [chars] has cross class sequence for [chars] |
The task has detected a subsystem which has an incorrect class for which it is being considered for. |
iosxe-binos-utils |
LOG_STD_ACTION |
SUBSYS-6-SUBSYS_UNORDERED |
6-Information |
Subsystem class [dec] ([chars]) has no order |
The task has detected a class which has an unknown order upon initialization. |
iosxe-binos-utils |
LOG_STD_ACTION |
SYSHW-3-SYSHW_READ |
3-Error |
A read operation has failed for device: [chars] error: [chars] |
A syshw read operation failed for the mentioned device |
polaris-infra |
The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component. |
SYSHW-3-SYSHW_REG_READ |
3-Error |
A register read operation has failed for device: [chars] register: [chars] error: [chars] |
A syshw register read operation failed for the mentioned device |
polaris-infra |
The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component. |
SYSHW-3-SYSHW_REG_WRITE |
3-Error |
A register write operation has failed for device: [chars] register: [chars] error: [chars] |
A syshw register read operation failed for the mentioned device |
polaris-infra |
The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component. |
SYSHW-3-SYSHW_WRITE |
3-Error |
A write operation has failed for device: [chars] error: [chars] |
A syshw write operation failed for the mentioned device |
polaris-infra |
The error message indicates a write failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate a permanent fault with the specific device/component. |
SYSPLAT-3-PLIM_BRIDGE_CRITICAL_ERROR |
3-Error |
Reloading [chars] due critical event %#x in block [chars]/[dec] of PLIM device |
A critical PLIM device I/O event has occurred. |
asr1k-infra-intrnl |
The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
SYSPLAT-3-PLIM_CRITICAL_ERROR_RATE |
3-Error |
Reloading [chars] due to critically high PLIM device error rate. |
A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect. |
asr1k-infra-intrnl |
Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
SYSPLAT-5-PLIM_BLOCK_EVENT |
5-Notice |
Block [chars]/[dec] of PLIM device had I/O event %#x |
A PLIM device I/O event has occurred. This event is not serious but is logged for diagnostic purposes. |
asr1k-infra-intrnl |
No user action is required. |
SYSPLAT-5-PLIM_EVENT_RATE |
5-Notice |
The [chars] event rate of [dec] has exceeded the threshold of [dec] on interconnect [dec] |
A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect. |
asr1k-infra-intrnl |
No user action is required. If this message persists, a PLIM device critical message that needs to be addressed will appear. |
SYSTEM-2-REBOOT_ABORTED |
2-Critical |
System reboot aborted due to [chars] |
This syslog is generated when system reboot is aborted due to an error |
cedge-install |
If reboot is aborted due to software error, please contact Cisco TAC |
SYSTEM-4-SSL_CERT_WARNING |
4-Warning |
SSL certificate warning: [chars] (code: [chars]) |
This syslog is generated when self-signed certificates are used for communication. Self signed certificates are not considered secure and must be replaced with certificates provided by verified distributors |
cedge-install |
Customers are expected to delete self-signed certificates and replace with them Enterprise certificates |
SYSTEM-5-REBOOT_ISSUED |
5-Notice |
System reboot issued, reason: [chars] |
This syslog is generated when system reboot is issued |
cedge-install |
No action is required |
SYSTEM-5-SOFTWARE_INSTALL_STATUS |
5-Notice |
Software install stage: [chars], install-id: [chars], message: [chars] |
This syslog is generated during software installation which goes through multiple stages |
cedge-install |
No action is required |
SYSTEM-6-CLI_COMMIT |
6-Information |
CLI commit done by user [chars] |
This info syslog is generated when a user alters config via CLI. CLI is usually locked when a device is managed by Cisco SD-WAN Manager, however when the control connection is down, CLI session is unlocked for users and user can commit via CLI |
vip-vdaemon |
No action is required |
SYSTEM_CONFIG_MESSAGE-2-AP_FILE_TRANSFER_HTTPS_CUST_PORT |
2-Critical |
CRITICAL, [chars] |
General WLC critical message |
iosxe-binos-utils |
LOG_STD_ACTION |
SYSTEM_CONFIG_MESSAGE-3-ACL_FLEX_ERR |
3-Error |
Error in [chars] |
ewlc ACL flex push error message. |
iosxe-binos-utils |
LOG_STD_ACTION |
SYSTEM_CONFIG_MESSAGE-3-ACL_INDEX_ERR |
3-Error |
Error in [chars] |
ewlc ACL flex index error message. |
iosxe-binos-utils |
LOG_STD_ACTION |
SYSTEM_CONFIG_MESSAGE-5-UNSUPPORTED_FLEX_ACL_RULE |
5-Notice |
Unsupported rule: [chars], in flex acl: [chars] |
unsupported rule in flex acl |
iosxe-binos-utils |
LOG_STD_ACTION |
TAGMGR_DB_SYSLOG-3-TAGMGR_RF_TAG_CREATE_ERROR |
3-Error |
Failure during RF tag [chars] creation, could not add to rf profile tag list |
Failed to add RF tag to RF profile tag list |
ewlc-rrm |
Please delete the RF tag and configure again |
TAGMGR_TRACE_MSG-3-TAG_EASY_PSK_CONFIG_WARNING |
3-Error |
Easy-PSK config validation error: [chars] |
Easy-PSK CONFIG warning message |
ewlc-spwifi |
LOG_STD_ACTION |
TAGMGR_TRACE_MSG-3-TAG_MPSK_CONFIG_WARNING |
3-Error |
MPSK config validation error: [chars] |
MPSK CONFIG warning message |
ewlc-ap |
LOG_STD_ACTION |
TAGMGR_TRACE_MSG-4-TAG_CONFIG_WARNING |
4-Warning |
Warning: [chars] |
General Wireless LAN Controller warning message |
ewlc-ap |
LOG_STD_ACTION |
TAGMGR_TRACE_MSG-5-WLC_MODE_CHANGE |
5-Notice |
Mode Change: [chars] |
Msg indicating AP reboot during Mode Change |
ewlc-ap |
LOG_STD_ACTION |
TDLDB-3-DATABASE_MEMORY_LEAK |
3-Error |
Database memory leak detected in [chars] database, [chars]/[chars]/[chars] size: [dec] bytes |
A memory leak has been detected in the database memory. The leaked object is identified by name |
iosxe-p-db |
LOG_STANDARD_ACTION |
TDLDB-3-DBPERSIST_OPERATION_FAILURE |
3-Error |
Operation: [chars], DB: [chars], Failure reason: [chars] |
Database persistent operation can be triggered by 1. Persist : write memory or reload CLI 2. Delete : write erase CLI 3. Restore : During boot time, when database is first opened When error occurs, it can impact the customer in this way 1. Persist : DB content can not be persisted, data will be lost after system reload. If reload CLI command fails, it does not allow the system getting reloaded. 2. Delete : There may be database residue in the persistent storage media. 3. Restore : Persistent content cab be lost |
iosxe-p-db |
LOG_STD_ACTION |
TDLDB-3-INVALID_TABLE_FREE |
3-Error |
Invalid table free by process [chars] in [chars] on table with luid [chars] |
In shared databases, only the garbage collector should be performing table and record deletes on tables that have read cursors enabled. A non-gc process has performed a table deletion. |
iosxe-p-db |
LOG_STD_ACTION |
TDLDB-3-SESSION_LOCK_TIMEOUT |
3-Error |
Owner: user-proc: [chars], DB: [chars]. Lock expired [chars] ago. |
An application running in a process wishes to have an exclusive write access to DB. It acquires a session lock with for a specific period and is expected to release or renew the session lock. The appication has failed to do so and hence the unexpected timeout has occured |
polaris-infra |
This is unexpected. Report this to Cisco TAC. |
TDLDB-3-WRITE_ON_SNAPSHOT |
3-Error |
Process writing on snapshotted DB [[chars]] |
Application is trying to write on a snapshotted DB. A snapshotted DB is read-only and any write operation is not effective. |
polaris-mdt-infra |
LOG_STD_ACTION |
TDLDB-4-LONG_READ_WRITE_LOCK_HELD |
4-Warning |
Process held [chars] lock on DB [[chars]] for [[dec]] ns |
Application has held the read/write lock for fairly long time. If this error is thrown, it means that the lock has been held for more than 1 sec. |
iosxe-p-db |
LOG_STD_ACTION |
TDLDB-6-DBPERSIST_OPERATION_INFO |
6-Information |
Cancelled [chars] operation and is intended - DB: [chars], Reason: [chars] |
When this message is observed, the reason can be 1. DB format version mismatched - database format definition can be changed. If mismatched, the operation is cancelled and this is an intended behavior. 2. DB base pointer mismatched - database base pointer can be modified. If changed, the operation is cancelled and this is an intended behavior. |
iosxe-p-db |
LOG_STD_ACTION |
TDLDB-6-SUBSCRIPTION_DAMPENING_INACTIVE |
6-Information |
Subscription dampening inactive for DB [chars] on table [chars]. All on-change updates for the table will be sent. Consider re-adjusting the dampening period |
On-change Subscription enabled with dampening will be temporarily in-active due to load on system or due to incorrect dampening interval configured. |
iosxe-p-db |
LOG_STD_ACTION |
TDLDB-6-SUBSCRIPTION_DAMPENING_REACTIVATE |
6-Information |
Dampening subscription re-activated for DB [chars] on table [chars] |
On-change Subscription re-activated with dampening resumed after it got paused |
iosxe-p-db |
LOG_STD_ACTION |
THERMAL-1-THERMAL_GREEN_THRESHOLD |
1-Alert |
Hotspot temperature has exceeded GREEN threshold\n |
The switch is too cold. |
polaris-platform_mgr |
Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. |
THERMAL-1-THERMAL_RED_THRESHOLD |
1-Alert |
Hotspot temperature has exceeded RED threshold. Switch will shutdown soon.\n |
The hotspot temperature is critically overheated. The switch will soon shutdown to prevent permanent damage. |
polaris-platform_mgr |
Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. |
THERMAL-2-THERMAL_YELLOW_THRESHOLD |
2-Critical |
Hotspot temperature has exceeded YELLOW threshold\n |
The hotspot temperature is too high. Improve cooling immediately. |
polaris-platform_mgr |
Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. |
THERMAL_SYM-1-THERMAL_GREEN_THRESHOLD |
1-Alert |
Hotspot temperature has exceeded GREEN threshold\n |
The switch is too cold. |
iosxe-chassismgr |
Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. |
THERMAL_SYM-1-THERMAL_RED_THRESHOLD |
1-Alert |
Hotspot temperature has exceeded RED threshold. Switch will shutdown soon.\n |
The hotspot temperature is critically overheated. The switch will soon shutdown to prevent permanent damage. |
iosxe-chassismgr |
Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. |
THERMAL_SYM-2-THERMAL_YELLOW_THRESHOLD |
2-Critical |
Hotspot temperature has exceeded YELLOW threshold\n |
The hotspot temperature is too high. Improve cooling immediately. |
iosxe-chassismgr |
Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. |
TH_WARN_MGR-2-WIRELESS_CLIENTS_THRESHOLD_CLEAR |
2-Critical |
Current percentage of joined wireless clients ([dec]) returned below the configured threshold ([dec]) |
The number of clients currently joined to the wireless controller returned below the configured threshold for the device |
iosxe-binos-utils |
If this message occurs, you need to carefully check if you need a more capable controller for the number of wireless clients you are trying to serve |
TH_WARN_MGR-2-WIRELESS_CLIENTS_THRESHOLD_HIT |
2-Critical |
Current percentage of joined wireless clients ([dec]) exceeded the configured threshold ([dec]) |
The number of clients currently joined to the wireless controller has exceeded the configured threshold for the device |
iosxe-binos-utils |
If this message occurs, you need to carefully check if you need a more capable controller for the number of wireless clients you are trying to serve |
TIMINGD-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-IPC_CONNECTION_INVALID |
0-Emergency |
An IPC connection has invalid state. |
An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-IPC_CONNECT_MASTER |
0-Emergency |
IPC connection to the active RSP failed because [chars] |
IPC connection to the active RSP failed. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-IPC_INITIALIZATION |
0-Emergency |
IPC initialization failed because [chars] |
IPC initialization failed. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-MESSAGE_REGISTER |
0-Emergency |
Failed to register with active RSP because [chars] |
The active RSP failed to register. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-MESSAGE_RELAY |
0-Emergency |
Failed to relay a message because [chars] |
Failed to relay a message. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-MESSAGE_RESPONSE |
0-Emergency |
An invalid message response was received because [chars] |
An invalid message response was received. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-MQIPC_ADVANCE |
0-Emergency |
Failed to advance MQIPC queue because [chars] |
The MQIPC initialization failed. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-MQIPC_INITIALIZATION |
0-Emergency |
MQIPC initialization failed because [chars] |
MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-PEER_TABLE |
0-Emergency |
A peer table initialization or maintenance function failed because [chars] |
A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
iiot-rtr-timing |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
TIMINGD-0-RESOURSE |
0-Emergency |
Resource allocation failed in [chars] because [chars] |
The system is unable to allocate the requested resource. |
iiot-rtr-timing |
In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command. |
TLSCD-4-DNS_RESOLVER_FAILURE |
4-Warning |
DNS resolver failed for url [chars] session [chars]. |
The TLS Client daemon attempted to resolve the server url and API is failing/timing out. The failure may have been caused by a miss configuration of nameserver or url string in crypto tls-tunnel configuration. Daemon shall be retrying to resolve the url periodically. |
iosxe-p-tlscdinfra |
This error indicates a configuration issue for url resolution. |
TLSCD-4-TPS_CERT_RESP_FAILURE |
4-Warning |
TPS certificate response failed for session session [chars]. |
The TLS Client daemon process attempted to get the ceritificate from IOSd and API is failing/timing out. The failure may have been caused by a miss configuration of pki trustpoint crypto tls-tunnel configuration. |
iosxe-p-tlscdinfra |
This error indicates a configuration issue for pki trustpoint. |
TLSCD-5-SESSION_UPDOWN |
5-Notice |
Session [[chars]] to TLSGW: [[chars]] is [chars]. |
The TLS Client daemon process session status notification. |
iosxe-p-tlscdinfra |
The TLS Client daemon process session status. |
TTYMON-3-AGETTY |
3-Error |
Cannot initiate a switch in console ownership. A required program could not be launched successfully. |
The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. Switching ownership of the console port is initiated by the user entering a 'send break' command at a telnet prompt. The Host Manager launches one or more programs to authenticate users and to provide a shell instance. One or more of these programs has not been configured correctly. |
iosxe-binos-utils |
Some required programs are either not available or not configured correctly or are failing for some reason. If this occurs after a recent upgrade it is possible that the upgrade has corrupted the current installation. |
TTYMON-3-CHASFS |
3-Error |
The software which monitors ownership of the console port cannot [chars] a filesystem configuration value. |
The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for monitoring a change of console ownership uses the filesystem to store various settings. This error indicates that the daemon encountered a problem either reading or writing a value from/to the filesystem. |
iosxe-binos-utils |
Check the log files for the Host Manager and search for entries related to 'ttymon' and 'chasfs' and this should give an indication as to why the operation failed. Check available resources and see if other daemons are also experiencing problems with the chassis filesystem since this may indicate a more pervasive problem. If so the reboot the box. |
TTYMON-3-INIT |
3-Error |
The software which monitors ownership of the console port cannot be initialized correctly |
The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for this has encountered an initialization error and console monitoring is no longer available. |
iosxe-binos-utils |
Check the status of the Host Manager process. Check the Host Manager log files for further indications as to why the initialization failed and if necessary restart the machine. |
U to Z
Facility-Severity-Mnemonic |
Severity-Meaning |
Message |
Message-Explanation |
Component |
Recommended-Action |
---|---|---|---|---|---|
UBD-0-EVENT_LIBRARY |
0-Emergency |
An event facility initialization or maintenance function failed because [chars] |
An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. |
polaris-infra |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered inforation to a Cisco technical support representative. |
UBD-0-MQIPC_ADVANCE |
0-Emergency |
Failed to advance MQIPC queue because [chars] |
The MQIPC initialization failed. |
polaris-infra |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
UBD-0-MQIPC_INITIALIZATION |
0-Emergency |
MQIPC initialization failed because [chars] |
MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. |
polaris-infra |
In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. |
UBD-2-INITIALIZATION_FAILED |
2-Critical |
URSA Bootstrap initialization for [chars] failed. |
Initialization of ursa bootstrap process failed. |
polaris-infra |
Review UBOOTD 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. |
UICFGEXP-3-LIBRARY_ERROR |
3-Error |
Error loading library '[chars]': [chars] |
A configuration message was received which required a library to be loaded. The library failed to load. |
iosxe-ui |
LOG_STD_ACTION |
UICFGEXP-3-MESSAGE_ERROR |
3-Error |
Unable to process message for '[chars]': [chars] |
A message was received by the configuration export module which could not be processed. The message has been discarded. |
iosxe-ui |
LOG_STD_ACTION |
UICFGEXP-3-SYMBOL_ERROR |
3-Error |
Error loading library symbol '[chars]' from '[chars]': [chars] |
A configuration message was received which required a library to be loaded. The library failed to load all required symbols. |
iosxe-ui |
LOG_STD_ACTION |
UICFGEXP-3-WRITE_FAILED |
3-Error |
Unable to write configuration for '[chars]': [chars] |
The configuration export module failed to write the server configuration files. The server configuration change has not occurred. |
iosxe-ui |
LOG_STD_ACTION |
UICFGEXP-6-SERVER_NOTIFIED_START |
6-Information |
Server [chars] has been notified to start |
The server has been notified to start. |
iosxe-ui |
LOG_STD_NO_ACTION |
UICFGEXP-6-SERVER_NOTIFIED_STOP |
6-Information |
Server [chars] has been notified to stop |
The server has been notified to stop. |
iosxe-ui |
LOG_STD_NO_ACTION |
UIPEER-2-TDL_MESSAGE |
2-Critical |
Cannot construct an IPC message for library. The message name is [chars] and the reason is: [chars] |
A problem occurred while constructing a type definition language (TDL) message or setting a field in a TDL message. If the problem occurred during construction of a TDL message, then the system is out of memory. If the problem occurred while setting a field in the TDL message, there is a library mismatch issue. |
iosxe-binos-utils |
Check [uipeer] ERR entries in the log files for message reporting problems. |
UIPEER-3-INVALID_DEBUG_MESSAGE |
3-Error |
The peer process was unable to process an incoming message for 'debug all' from the shell-manager |
When the 'debug all' command is issued, the Shell Manager broadcasts a notification of the command request to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation. |
iosxe-binos-utils |
Check the trace files for the Shell Manager failed process. Restart the system. |
UIPEER-3-INVALID_EPOCH_MESSAGE |
3-Error |
The peer process was unable to process an incoming epoch update message from the shell-manager |
For each new type definition language (TDL) epoch, the Shell Manager broadcasts a change notification message to its peers. If the Shell Manager's message is incorrect or corrupt, the peers are unable to identify the new epoch. In this case, the peers reject the proposed epoch. |
iosxe-binos-utils |
Check the trace files for the Shell Manager failed process. Check or undo any recently installed packages, then restart the system. |
UIPEER-3-INVALID_HOSTINFO_MESSAGE |
3-Error |
The peer process was unable to process an incoming message for host info from the shell-manager |
When host information, such as the hostname, changes, the Shell Manager broadcasts a notification of the change to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation. |
iosxe-binos-utils |
Check the trace files for the Shell Manager failed process. Restart the system. |
UIPEER-3-NO_PEER |
3-Error |
A process was unable to retrieve a shell-manager peer handle. |
A process was attempting to communicate with the Shell Manager daemon using the integrated [uipeer] component. The error occurred because the peer instance could not be found. |
iosxe-binos-utils |
Check [uipeer] ERR entries in the log files for message reporting problems. |
UIPEER-3-SET_LOG_TRACELOG_NUM |
3-Error |
Tracelog number for process [chars] changed to [dec] |
Tracelog number to keep for a process is changed using set logging tracelog-number .. CLI |
polaris-trace |
No action is required. This is informational message |
UIPEER-5-TIMER_ACCURACY_TEST |
5-Notice |
Timer Accuracy Test [chars]. |
Test result of Timer Accuracy Test |
iosxe-binos-utils |
No action is required. This is informational message |
UPGRADE-3-AP_SW_UPDATE_ERR_LOG_MSG |
3-Error |
AP SW update [chars] |
AP Software Update logging |
ewlc-upgrade |
AP software update failed. ISSU image upgrade or SMU patching could be aborted. The user needs to initiate ISSU upgrade/SMU patch again. If the error occured during manual operation, operation can be initiated again |
UPGRADE-3-AP_UPGRADE_CLEAR_REPORT_NAME_ERROR |
3-Error |
AP Upgrade clear report error, failed to find upgrade report name : <[chars]> from upgrade report table |
Error occured in deleting record from upgrade report table. Operation aborted. |
ewlc-upgrade |
LOG_STD_ACTION |
UPGRADE-3-AP_UPGRADE_CLEAR_REPORT_NAME_IN_PROGRESS_ERROR |
3-Error |
Staggered AP Upgrade in progress, failed to delete upgrade record with report name : <[chars]> from upgrade report table |
Error occured in deleting record from upgrade report table. Operation aborted. |
ewlc-upgrade |
LOG_STD_ACTION |
UPGRADE-3-AP_UPGRADE_FALLBACK_ERROR |
3-Error |
AP Upgrade fallback error |
Error occured in upgrade fallback process. Operation aborted. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-3-AP_UPGRADE_FALLBACK_INIT_TIMEOUT |
3-Error |
Timeout occurred either source controller is not responding or has responded with invalid software version. Aborting fallback process |
Timeout occurred. Source controller is not responding to the upgrade fallback version request message or it has responded with an invalid software version. Aborting fallback process |
ewlc-upgrade |
Please reload source controller with valid image and initiate upgrade process from destination controller by using CLI: 'ap image move destination <Destination Name> <Destination IPv4/IPv6 address> <Report name>' |
UPGRADE-3-AP_UPGRADE_FALLBACK_TYPE_MSG_ERROR |
3-Error |
AP upgrade process aborted. Failed to send fallback type message to peer |
Error occured while sending fallback type message to peer. Operation aborted. |
ewlc-upgrade |
Please restore the mobility status between source and destination controller |
UPGRADE-3-AP_UPGRADE_FALLBACK_VERSION_VALIDATION_FAILURE |
3-Error |
Source controller is not responding or has responded with invalid software version |
Source controller is not responding to the upgrade fallback version request message or it has responded with an invalid software version |
ewlc-upgrade |
Please reload source controller with valid image |
UPGRADE-3-DESTINATION_NOT_READY |
3-Error |
Destination controller not ready. Aborting upgrade process |
Destination controller may be going through another AP upgrade or move |
ewlc-upgrade |
Please wait for the current ap upgrade to finish before triggering this command. |
UPGRADE-3-DESTINATION_NOT_RESPONDING |
3-Error |
AP upgrade process aborted. Destination controller is not responding |
Destination controller is not responding to the upgrade request message |
ewlc-upgrade |
Destination Controller may be down or unreachable. Please restore the mobility status between source and destination controllers before initiation of AP move/upgrade to destination |
UPGRADE-3-MOBILITY_TUNNEL_DOWN |
3-Error |
AP upgrade process aborted. Mobility tunnel is down for more than the permissible amount of time |
If the mobility tunnel with the peer is down for more than the permissible amount of time, the current upgrade process is aborted |
ewlc-upgrade |
Please restore the mobility status between source and destination controllers before initiation of AP move/upgrade to destination |
UPGRADE-3-STAGGERED_UPGRADE_ABORT_DEST_ERROR |
3-Error |
Trigger abort CLI from source WLC, fail to abort AP upgrade |
AP upgrade abort CLI should be triggered from source WLC. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-3-STAGGERED_UPGRADE_ABORT_ERROR |
3-Error |
Staggered AP Upgrade not in progress, fail to abort AP upgrade |
Error occured in AP upgrade abort process. Operation aborted. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-3-STAGGERED_UPGRADE_ERROR |
3-Error |
Staggered AP Upgrade error: [chars] |
Error occured in upgrade reset process. Operation aborted. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-3-STAGGERED_UPGRADE_IN_PROGRESS |
3-Error |
AP upgrade is in progress. New ap upgrade process is not allowed |
If an ap upgrade process is already running, either in source or destination mode, new ap upgrade process is not allowed |
ewlc-upgrade |
Please wait for the current ap upgrade to finish before triggering this command. |
UPGRADE-3-STAGGERED_UPGRADE_MOVE_REPORT_ERROR |
3-Error |
Invalid ap upgrade report name |
Upgrade report name entered is invalid |
ewlc-upgrade |
Please enter a valid ap upgrade report name. |
UPGRADE-5-AP_SW_UPDATE_LOG_MSG |
5-Notice |
AP SW update [chars] |
AP Software Update logging |
ewlc-upgrade |
No action required |
UPGRADE-5-AP_UPGRADE_AP_RESET_FAILURE |
5-Notice |
AP with MAC: [chars] has not rejoined after software upgrade. No longer accounting for this AP |
AP has not rejoined the controller |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-5-AP_UPGRADE_EVENT |
5-Notice |
Staggered AP upgrade event: [chars] |
Staggered AP upgrade event message |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-5-AP_UPGRADE_SITE_FILTER_ANY_IGNORE |
5-Notice |
Site-filters for any-image will be ignored for APSP/APDP. |
Site-filters added with any-image are only applicable for N+1 upgrades. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-5-AP_UPGRADE_SSO_FAILURE |
5-Notice |
Staggered AP upgrade was interrupted due to SSO. The upgrade process will continue shortly. |
Staggered AP upgrade was interrupted due to SSO. The process should restart automatically |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-AP_UPGRADE_ANY_IMAGE_DB_DELETE |
6-Information |
Site-filters added with image name 'any' deleted. |
Existing site-filters with image name 'any' are deleted. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-AP_UPGRADE_AP_RESET |
6-Information |
AP: [chars] has incorrect software. AP is going for reset. |
AP is going for a software upgrade |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-AP_UPGRADE_CLEAR_REPORT_NAME |
6-Information |
AP Upgrade record deleted successfully |
Deleted AP upgrade record. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-AP_UPGRADE_DB_DELETE |
6-Information |
Site filters for APSP deleted for the image version [chars]; new image version is [chars] |
Existing site-filters for APSP are deleted since the base image is upgraded. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-AP_UPGRADE_FALLBACK_COMPLETE |
6-Information |
AP Upgrade fallback process completed succesfully |
AP Upgrade fallback process completed |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-AP_UPGRADE_FALLBACK_START |
6-Information |
AP Upgrade fallback process started |
Starting AP upgrade fallback process |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-STAGGERED_UPGRADE_ABORT |
6-Information |
Aborted AP Upgrade successfully |
Aborted AP upgrade process. |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-STAGGERED_UPGRADE_ABORT_DEST |
6-Information |
Aborted AP Upgrade forcibly on destination controller |
AP upgrade was forcibly stopped on destination controller by the user |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-STAGGERED_UPGRADE_COMPLETE |
6-Information |
Staggered AP Upgrade completed succesfully |
All APs in current upgrade process rebooted with the new version |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-STAGGERED_UPGRADE_START |
6-Information |
Staggered AP Upgrade reboot process started |
Rebooting given APs in staggered way |
ewlc-upgrade |
LOG_STD_NO_ACTION |
UPGRADE-6-STAGGERED_UPGRADE_WITH_RESET_FALLBACK_COMPLETE |
6-Information |
Staggered AP Upgrade with fallback type as either reset or reset with fallback completed succesfully |
All APs in current upgrade process rebooted with the new version |
ewlc-upgrade |
LOG_STD_NO_ACTION |
VDAEMON-3-NO_ACTIVE_VBOND |
3-Error |
Device does not have an active connection to SD-WAN validator |
This error syslog is generated when there are no active control connections to Cisco SD-WAN Validator. This could be a temporary situation where control connections flap because of some network issue. This could also imply some issue with SD-WAN Validator |
vip-vdaemon |
If the issue persists, i.e. control connections to SD-WAN Validator do not come up for long, use vdiagnose utility to identify the reason |
VDAEMON-3-NO_ACTIVE_VSMART |
3-Error |
Device does not have an active connection to SD-WAN Controller |
This error syslog is generated when there are no active control connections to Cisco SD-WAN Controller. This could be a temporary situation where control connections flap because of some network issue. This could also imply some issue with SD-WAN Controller(s) |
vip-vdaemon |
If the issue persists, i.e. control connections to SD-WAN Controller(s) do not come up for long, use vdiagnose utility to identify the reason |
VDAEMON-3-NO_SDWAN_MODE |
3-Error |
Device does not suppport SD-WAN control mode |
This error syslog is generated when SD-WAN Edge virtual machine is instantiated on an unsupported hypervisor |
vip-vdaemon |
Please check SD-WAN documentation on which all hypervisors are supported for SD-WAN mode |
VDAEMON-5-CONTROL_CONN_STATE_CHANGE |
5-Notice |
Control connection to [chars] [chars] (TLOC: [chars]/[dec]/[chars] via [chars]) is [chars] |
This notice syslog is generated when control connection to Cisco SD-WAN Validator, Controller or Manager goes down or comes back up |
vip-vdaemon |
No action is required |
VDAEMON-5-PEER_AUTH_FAILED |
5-Notice |
Auth failed for [chars] ([chars]), reason: [chars]. Control connection attempt via [chars] (color: [chars]) |
This notice syslog is generated when control connection to peer device (Cisco SD-WAN Validator, Manager or Controller) cannot be established due to various reasons |
vip-vdaemon |
Please refer to https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/214509-troubleshoot-control-connections.html for troubleshooting control connection failures |
VDAEMON-6-DOMAIN_ID_CHANGED |
6-Information |
Domain id changed from [dec] to [dec] via config |
This info syslog is generated when domain-id is changed via config |
vip-vdaemon |
No action is required |
VDAEMON-6-IPSEC_REKEY |
6-Information |
IPSec SA [chars] rekey done for tunnel established via [chars] (color: [chars]) |
This info syslog is generated when auto/manual IPSEC rekey is initiated for tunnels established over a WAN interface |
vip-vdaemon |
No action is required |
VDAEMON-6-ORG_NAME_CHANGED |
6-Information |
Organization name changed from [chars] to [chars] |
This info syslog is generated when organization name is changed via config |
vip-vdaemon |
No action is required |
VDAEMON-6-SITE_ID_CHANGED |
6-Information |
Site id changed from [dec] to [dec] via config |
This info syslog is generated when site-id is changed via config |
vip-vdaemon |
No action is required |
VDAEMON-6-SYSTEM_IP_CHANGED |
6-Information |
System IP changed from [chars] to [chars] via config |
This info syslog is generated when system IP is changed via config |
vip-vdaemon |
No action is required |
VDAEMON-6-SYSTEM_LICENSE_MISMATCH |
6-Information |
There is a license association mismatch. [chars] instance is being associated to [chars] license |
This info syslog is generated when there is a license association mismatch. Pay As You Go instance cannot be associated with Bring Your Own instance or vice versa |
vip-vdaemon |
Contact Cisco TAC for assistance |
VDAEMON-6-TLOC_IP_CHANGE |
6-Information |
Control connection TLOC changed from [chars]:[dec] to [chars]:[dec] |
This info syslog is generated when TLOC IP and port changes as a result of static configuration change, DHCP renewal or when the edge device learns about public IP/port via Cisco SD-WAN Catalyst validator (which behaves as STUN server in such cases) |
vip-vdaemon |
No action is required |
VDAEMON-6-VMANAGE_CONNECTION_PREF_CHANGED |
6-Information |
vManage connection preference for interface: [chars] (color: [chars]) changed to [dec] |
This info syslog is generated when vmanage connection prefernce value for a WAN interface is changed via config |
vip-vdaemon |
No action is required |
VIP_CONFD-3-VIP_CONFD_ERR_LOG |
3-Error |
vip-confd logging : [chars] |
vip-confd error log: |
cedge-bootstrap |
The vip-confd process console logging. |
VIP_CONFD-5-VIP_CONFD_NOTICE_LOG |
5-Notice |
vip-confd logging : [chars] |
vip-confd notice log: |
cedge-bootstrap |
The vip-confd process console logging. |
VMAN-2-ACTIVATION_STATE |
2-Critical |
[chars] '[chars]' [chars] [chars] |
The activation state of the named virtual service has changed as notified by Virt-manager. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. |
VMAN-2-ALLOC_VIRT_INST_RCS |
2-Critical |
Virtual Service[chars] |
A memory allocation request failed to allocate a data structure required to activate the virtual service. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-COMMIT_VIRT_INST_RCS |
2-Critical |
Virtual Service[chars] |
The request to commit the resources required by the named virtual service failed. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-CPUSHARES_LIMIT |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services. |
vman |
Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-CPUTUNES_INTERNAL_ERROR |
2-Critical |
Virtual Service[chars] |
Virt-manager and its associated infrastructure experienced an internal error. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-CPUTUNES_SHARES_LIMIT |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services. |
vman |
Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-CREATE_VIRT_INST_ENTRY |
2-Critical |
Virtual Service[chars] |
The request to create a DB entry for the named virtual service failed. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-DEACT_FOR_ISSU |
2-Critical |
[chars] Max ([dec]s) |
An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled. |
vman |
None. Allow the ISSU to continue and the VMs will restart when the ISSU completes; or cancel the ISSU and vman will automatically restart the VMs. |
VMAN-2-DEFER_VIRT_INST_PROC |
2-Critical |
Virtual Service[chars] |
The final activation processing failed to successfully defer. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-DISK_IMAGE_PATH |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-FIND_VIRT_INST_ENTRY |
2-Critical |
Failed to find virtual service with id [dec] in the Virt-manager DB |
The virtual service with the ID named could not be located in the Virt-manager DB. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-GENERAL_FAILURE |
2-Critical |
Virtual Service[chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-2-GUESTSHELL_ENABLED |
2-Critical |
The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it. |
Informs the user that the guest shell virtual service has been enabled (which is done by default). |
vman |
The user may use or remove the guest shell with the commands specified. |
VMAN-2-HA_STATE |
2-Critical |
[chars] [chars] [chars] [chars] |
VMAN tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. |
VMAN-2-HA_SWITCHOVER_STATE |
2-Critical |
[chars] [chars] [chars] [chars] |
VMAN HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. |
VMAN-2-HA_SYNC_ERR |
2-Critical |
[chars] '[chars]' [chars] |
The ha-sync persistent storage disk for the virtual service cannot be watched for sync to standby RP. |
vman |
Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-HA_SYNC_THREAD_STATE |
2-Critical |
HA remote sychronize thread has failed and exited. |
VMAN tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same. |
VMAN-2-INCONSISTENT_CPUTUNES_CONFIG |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is requesting invalid CPU tunes parameter. |
vman |
Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-INCONSISTENT_MEM_CONFIG |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is inconsistent in the specification of required memory via the <memory> and <currentMemory> nodes. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-INSERT_VIRT_INST_ENTRY |
2-Critical |
Virtual Service[chars] |
Inserting the named virtual service into the virtual service DB tracked by Virt-manager failed. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-INSTALL_FAILURE |
2-Critical |
Virtual Service[chars] |
The installation of the virtual service failed. |
vman |
Enable the Virt-manager trace logs and repeat the installation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-INSTALL_LOG |
2-Critical |
[chars] [chars] [chars] [chars] |
The installation log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI |
vman |
No action is required |
VMAN-2-INSTALL_MEDIA_RETRY |
2-Critical |
VMAN, VM install media still unavailable.[chars] |
The install media was not detected. Waiting for udev to complete install media(harddisk) detection. |
vman |
After VMAN exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again. |
VMAN-2-INSTALL_STATE |
2-Critical |
[chars] '[chars]'[chars] [chars] |
The installation state of the named virtual service has changed as notified by Virt-manager. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. |
VMAN-2-INVALID_ACT_MSG |
2-Critical |
Virtual Service[chars] |
The virtual service activate message was received, however, the data it contained could not be interpreted |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-INVALID_DEACT_MSG |
2-Critical |
Failed to process virtual service deactivate message |
The virtual service deactivate message was received, however, the data it contained could not be interpreted |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-INVALID_PACKAGE |
2-Critical |
Virtual Service[chars] |
The package definition file for the named virtual service has failed to be validated and the virtual service will not run |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. The most likely cause would be that the package file has been corrupted during file transfer. The suggested action would be to redo the file transfer. |
VMAN-2-INVALID_UNPROV_MSG |
2-Critical |
Failed to process virtual service unprovision message |
The virtual service unprovision message was received, however, the data it contained could not be interpreted |
vman |
Enable the Virt-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-MACHINE_TYPE_NOT_SUPPORTED |
2-Critical |
Virtual Service[chars] |
The virtual service cannot be activated as the machine type specified is not supported |
vman |
Enable the support for the machine type and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-MACH_PARSE_FAILURE |
2-Critical |
Virtual Service[chars] |
The named virtual service has an invalid parameter specified in the .xml file inside the .ova package |
vman |
Fix the .xml file inside the .ova package to have valid values. Then retry installing and activating it |
VMAN-2-MEMORY_LIMIT |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is requesting more memory than the system has available for virtual services. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-MEMORY_LIMIT_WARN |
2-Critical |
Virtual service ([chars])[chars] defines [dec] MB of Memory exceeding the maximum [dec] MB. |
The virtual service machine definition file is requesting more memory for the specified profile, than the system has available for virtual services. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-MORETHANONE_CPUTUNES_CONFIG |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is requesting more than one CPU tunes parameter. |
vman |
Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-MOVE_STATE |
2-Critical |
[chars] '[chars]' [chars] [chars] |
The move of the core or log file of the named virtual service has as been successful or failed as notified by Virt-manager. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. |
VMAN-2-NETWORK_CONFIG_ERROR |
2-Critical |
Virtual Service[chars] |
A network configuration error has been detected for the named virtual service. |
vman |
No action is required |
VMAN-2-PROCESS_PKG_DEF |
2-Critical |
Virtual Service[chars] |
The virtual service package for the named virtual service has failed to be validated and the virtual service will not run. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-PROC_INT_LIST |
2-Critical |
Virtual Service[chars] |
The interface list embedded in the activate request for the named virtual service could not be processed. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-REMOVE_VIRT_INST_ENTRY |
2-Critical |
Virtual Service[chars] |
Removing the named virtual service from the virtual service DB tracked by Virt-manager failed. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-RESET_FORCE |
2-Critical |
Virtual Services non-recoverable reset command processed |
A 'virtual service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked. |
vman |
Once the command is entered and accepted, there is no recourse but to restart the system. |
VMAN-2-RESIZE_OPER_STATE |
2-Critical |
Virtual service '[chars]' [chars][chars] to '[dec]' [chars] |
VMAN attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. |
VMAN-2-RSYNC_STATE |
2-Critical |
[chars] [chars] [chars] [chars] |
VMAN tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised. |
vman |
In the failed case, check Virt-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same. |
VMAN-2-SET_VTX_ROMVAR_SPACE |
2-Critical |
Failed to set ROM monitor variable ENABLE_VTX: No space in table |
Failed to set ENABLE_VTX ROM monitor variable due to no space in Monitor Variable Table. |
vman |
Verify number of entries in Monitor Variable Table. |
VMAN-2-SET_VTX_ROMVAR_STRING |
2-Critical |
Failed to set ROM monitor variable ENABLE_VTX: Invalid string format: [chars] |
Failed to set ENABLE_VTX rom monitor variable due to invalid string format. |
vman |
Verify format of string from error message. |
VMAN-2-START_FAILED |
2-Critical |
Virtual Service[chars] |
The named virtual service failed to start. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-UNINSTALL_ALL_VMS |
2-Critical |
All Virtual Services are being uninstalled [chars][chars] [chars] |
All virtual services are being uninstalled by Virt-manager. |
vman |
Examine the reason given as to why all virtual services are being uninstalled for more information. If the reason indicated is due to some error condition, check Virt-manager's logs for the cause of the failure. |
VMAN-2-UPGRADE_LOG |
2-Critical |
[chars] [chars] [chars] [chars] |
The upgrade log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI |
vman |
No action is required |
VMAN-2-VCPU_INVALID |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is requesting invalid VCPU value. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-VCPU_LIMIT |
2-Critical |
Virtual Service[chars] |
The virtual service machine definition file is requesting more VCPUs than the system has reserved for virtual services. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-VIRT_INST_CRIT |
2-Critical |
VIRTUAL SERVICE [chars] LOG: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-2-VIRT_INST_DISK |
2-Critical |
Virtual Service[chars] |
The virtual service requires Disk Storage in excess of the Free Disk Storage available to virtual services. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-VIRT_INST_INTERFACE |
2-Critical |
Virtual Service[chars] |
The number of configured virtual port group interfaces must match the number of Ethernet Network Interfaces defined in the machine definition file |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-VIRT_INST_LOG_UNTHROTTLE |
2-Critical |
Failed to unthrottle the log for virtual service [chars] |
The named virtual service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason. |
vman |
For debugging collect the virt-manager logs and scan them for the cause. |
VMAN-2-VIRT_INST_MEMORY |
2-Critical |
Virtual Service[chars] |
The virtual service requires physical memory in excess of the free memory available to virtual services. |
vman |
Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. |
VMAN-2-VIRT_INST_MGMT_INTERFACE |
2-Critical |
Virtual service [chars] has no management interface defined but it is configured in CLI. |
A management interface is configured but none is defined. |
vman |
Deactivate the virtual service, remove the management interface configuration CLI, and reactivate the virtual-service. |
VMAN-2-VIRT_INST_STATE |
2-Critical |
Virtual Service[chars] |
The named virtual service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed. |
vman |
An attempt at restarting the virtual service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the Virt-manager logs and scan them for the cause. |
VMAN-3-PSS_ERR |
3-Error |
Purpose: [chars], URI: [chars], errcode: [dec] |
Persistent Storage Service handling error |
vman |
Collect the Virt-manager logs and scan them for the cause. |
VMAN-3-PSS_SNAPSHOT_ERR |
3-Error |
Source URI: [chars], Destination URI: [chars], errcode: [dec] |
Persistent Storage Service snapshot error |
vman |
Collect the Virt-manager logs and scan them for the cause. |
VMAN-3-SDWRAP_ERR |
3-Error |
Description: [chars], errcode: [dec] |
Debug infrastructure error |
vman |
Collect the Virt-manager logs and scan them for the cause. |
VMAN-3-VIRT_INST_ERR |
3-Error |
VIRTUAL SERVICE [chars] LOG: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-4-HA_SYNC_NEEDED |
4-Warning |
If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover |
Message notifying user that he needs to manually synchronize the Virtual service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell |
vman |
User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired. |
VMAN-4-PACKAGE_SIGNING_LEVEL_CHANGED |
4-Warning |
Package signing level changed from allow '[chars]' to allow '[chars]' |
The package certificate signing level global setting has been changed via configuration under the virtual-service global sub-mode. |
vman |
Ensure that this setting has been changed as expected by an authorized user. |
VMAN-4-UPDATE_WARNING |
4-Warning |
Virtual Service[chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-4-VIRT_INST_WARN |
4-Warning |
VIRTUAL SERVICE [chars] LOG: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-4-VIRT_SERV_LIBVIRTD_WARN |
4-Warning |
VMAN not able to connect to the libvirt daemon after '[dec]' attempts |
VMAN has been unable to connect to the libvirt daemon. Virtualization services will not be available until this connection is made. |
vman |
Collect the logs produced by 'show virt tech' |
VMAN-4-WATCHDOG_TIMER |
4-Warning |
[chars] '[chars]' [chars] [chars] |
The watchdog timer configured for the named virtual service has expired. |
vman |
Check any logs produced by the virtual service to determine the cause. |
VMAN-5-AUX |
5-Notice |
Virtual Service[chars] |
The AUX login to a virtual service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution. |
vman |
No action is required |
VMAN-5-PACKAGE_SIGNING_LEVEL_ON_INSTALL |
5-Notice |
Package '[chars]' for service container '[chars]' is '[chars]', [chars] '[chars]' |
A service container software package with the certificate signing level described is being installed. |
vman |
Take note of the service container and software package. Verify the software package is expected to be (un)signed as described and has the appropriate contents. Uninstall the package if unsure of the package origins. |
VMAN-5-PERMISSION_DENIED |
5-Notice |
Virtual Service '[chars]' is not owned by client IOSd |
An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected. |
vman |
No action is required. |
VMAN-5-VIRT_INST |
5-Notice |
LOG FROM VIRTUAL SERVICE [chars]: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-5-VIRT_INST_NOTICE |
5-Notice |
VIRTUAL SERVICE [chars] LOG: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-6-VIRT_INST_INFO |
6-Information |
VIRTUAL SERVICE [chars] LOG: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
VMAN-7-VIRT_INST_DEBUG |
7-Debug |
VIRTUAL SERVICE [chars] LOG: [chars] |
The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. |
vman |
No action is required |
WDAD_TRACE_MESSAGE-3-WLC_REGULATORY_FILE_PROCESS_ERR |
3-Error |
Error : [chars] |
Error in regulatory file processing |
ewlc-rrm |
LOG_STD_ACTION |
WDAD_TRACE_MESSAGE-4-WLC_REGULATORY_FILE_PROCESS_WARN |
4-Warning |
Warning: [chars] |
Regulatory file processing warning message |
ewlc-rrm |
LOG_STD_ACTION |
WDAD_TRACE_MESSAGE-5-WLC_REGULATORY_FILE_PROCESS_NOTICE |
5-Notice |
Notice : [chars] |
Regulatory file processing notice message |
ewlc-rrm |
LOG_STD_ACTION |
WEBSERVER-5-CONNECTION_FAILED |
5-Notice |
connection failed from host [chars] - [chars] |
Failure reason for SSL connection |
ng-web-infra |
No action is required |
WEBSERVER-5-LOGIN_FAILED |
5-Notice |
Login Un-Successful from host [chars] |
Login unsuccessful when user/password is invalid |
ng-web-infra |
No action is required |
WEBSERVER-5-LOGIN_PASSED |
5-Notice |
Login Successful from host [chars] by user '[chars]' |
Login successful |
ng-web-infra |
No action is required |
WEBSERVER-5-MAX_CONNECTION_REACHED |
5-Notice |
HTTP server maximum connection reached '[dec]' |
Maximum HTTP connection reached. |
ng-web-infra |
No action is required |
WEBSERVER-5-SESS_LOGOUT |
5-Notice |
Successfully logged out from host [chars] by user '[chars]' |
Logout successful |
ng-web-infra |
No action is required |
WEBSERVER-5-SESS_TIMEOUT |
5-Notice |
Session timeout from host [chars] by user '[chars]' |
Session Timeout |
ng-web-infra |
No action is required |
WEBSOCKET_SPACES-3-WS_ONBOARDING_DISCONNECTING |
3-Error |
Onboarding websocket to cisco-spaces is disconnecting for reason:[chars] |
Onboarding websocket to cisco-spaces is disconnecting |
spaces-oa |
If this message occurs, it means onboarding websocket to cisco-spaces is disconnecting |
WEBSOCKET_SPACES-3-WS_ONBOARDING_ERR |
3-Error |
Onboarding websocket to cisco-spaces could not be established for error:[chars] |
Onboarding websocket to cisco-spaces could not be established due to errors |
spaces-oa |
If this message occurs, it means onboarding websocket to cisco-spaces could not be established due to errors |
WEBSOCKET_SPACES-6-WS_ONBOARDING_DISCONNECTED |
6-Information |
Onboarding websocket to cisco-spaces is disconnected |
Onboarding websocket to cisco-spaces is disconnected |
spaces-oa |
If this message occurs, it means Onboarding websocket to cisco-spaces is disconnected |
WEBSOCKET_SPACES-6-WS_ONBOARDING_SUCCESS |
6-Information |
Onboarding websocket to cisco-spaces is successfully established |
Onboarding websocket to cisco-spaces is successfully established |
spaces-oa |
If this message occurs, it means onboarding websocket to cisco-spaces is successfully established |
WEBUI-6-INSTALL_OPERATION_INFO |
6-Information |
User: [chars], Install Operation: [chars] [chars] |
This message is used to indicate that an install operation is being performed via WebUI |
web-ui-wireless |
No action required. This is not an error, it is a log message that an install operation is being performed via WebUI |
WLANMGR_TRACE_MESSAGE-2-EWLC_WLANMGR_CRIT_ERR |
2-Critical |
Wlanmgr Error: [chars] |
Wlanmgr ewlc Error Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
WLANMGR_TRACE_MESSAGE-2-EWLC_WLANMGR_CRIT_ERR_TRACE |
2-Critical |
WLANMGR Error: [chars] |
WLAN configs are not getting pushed to Access points. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. |
iosxe-binos-utils |
Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. |
WLANMGR_TRACE_MESSAGE-3-EWLC_WLANMGR_SCHEDULED_WLAN_DISABLE |
3-Error |
WLANs associated with policy profile [chars] are disabled by calendar profile [chars] |
Wlanmgr scheduled WLAN disable message. |
iosxe-binos-utils |
LOG_STD_ACTION |
WLANMGR_TRACE_MESSAGE-3-EWLC_WLANMGR_SCHEDULED_WLAN_ENABLE |
3-Error |
WLANs associated with policy profile [chars] are enabled by calendar profile [chars] |
Wlanmgr scheduled WLAN enable message. |
iosxe-binos-utils |
LOG_STD_ACTION |
WLANMGR_TRACE_MESSAGE-4-EWLC_WLANMGR_WARN |
4-Warning |
Wlanmgr Warning: [chars] |
Wlanmgr ewlc Warning Message. |
iosxe-binos-utils |
LOG_STD_ACTION |
WNCD_ERROR_MESSAGE-3-WNCD_CONFIG_DONE_IPC_FAILURE |
3-Error |
Error: IPC failure to notify wncmgrd on config_done event. |
Critical notification to allow AP join |
ewlc-app-infra |
LOG_STD_ACTION |
WNCD_EWC_ERRMSG-6-INSTALL_CLEANUP_INFO |
6-Information |
INSTALL cleanup after switchover: [chars] |
General EWC WNCD message |
ewcap-image |
LOG_STD_ACTION |
WNCMGRD_ERROR_MESSAGE-3-BULK_SYNC_FAIL |
3-Error |
Error: Bulk sync not complete. Reloading the WLC! |
Switchover happened before bulk sync is complete! |
ewlc-ha |
LOG_STD_ACTION |
WNCMGRD_ERROR_MESSAGE-3-HA_PAIR_ERROR |
3-Error |
Error: Number of wncd instances mismatched between active and standby; HA function will not function correctly. |
Resource provision is different on active and standby |
ewlc-ha |
LOG_STD_ACTION |
WSA_ICAP_MESSAGE-3-EWLC_WSA_ICAP |
3-Error |
%% Error: ICap: [chars] |
General ewlc ICap config failure |
iosxe-binos-utils |
LOG_STD_ACTION |
WUILOGIN-2-AUTHENTICATION_SYSTEM_FAILED |
2-Critical |
WebUI standalone authentication process failed. Reason: [chars] |
During the id and password validation phase of the wuilogin access module authentication attempt, an exception occurred. This message usually occurs as a result of a failure of the underlying PAM authentication module. |
iosxe-binos-utils |
Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed. |
WUILOGIN-2-INITIALIZATION_FAILED |
2-Critical |
WebUI standalone login initialization failed. |
The attempt to access the web user interface using the wuilogin access module failed. The wuilogin access module is used to authenticate web user interface access only when the IOS integrated webserver, which is enabled using the ip http server command, or the IOS process is down or disabled. |
iosxe-binos-utils |
Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed. |
Additional References
Technical Assistance
When the recommended action of an error message advises that you contact Cisco technical support, open a case with the Cisco Technical Assistance Center (TAC).
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |