System Message Guide for Cisco IOS XE 17.16.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.16.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.16.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_COUNTRY_CODE

5-Notice

AP Name [chars] Mac: [chars] Model [chars] Type [chars] : [chars]

Resolved country code

ewlc-ap

LOG_STD_NO_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_INIT-1-CMAN_BOOT_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_INIT-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_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_LED-6-CHASSIS_BEACON_LED_TURNED

6-Information

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

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

iosxe-chassismgr

Check the switch's environment is a safe operating temperature. If problem persists, replace the switch.

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

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