System Message Guide for Cisco Catalyst Series Switches, Cisco IOS XE Bengaluru 17.5.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 Messages for Cisco IOS XE Bengaluru 17.5.x

Facility-Severity-Mnemonic

Severity-Meaning

Message

Message Explanation

Component

Recommended Action

PERF_MEASURE-2-CRIT_ERR

2-Critical

The Perf Measure protocol has encountered the critical error: [chars].

The protocol has run into a critical error. The reason should be given in the brackets.

perf-measure

LOG_STD_ACTION

PERF_MEASURE-4-ISSU_INCOMPATIBLE

4-Warning

\nperf-measure-issu-compat: returned FALSE

The compatibility checking has failed

perf-measure

LOG_STD_SH_TECH_ACTION

PERF_MEASURE-3-TRANSFORM_FAIL

3-Error

PERF MEASURE ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars]

The PERF MEASURE ISSU client could not transform the specified message type. If the transmit transformation failed the checkpoint message was not sent to the standby device. If the receive transformation failed the checkpoint message was not applied on the standby device. In both cases the PERF MEASURE state between the active device and the standby device is not identical.

perf-measure

"show issu session <client_id> and " "show issu negotiated version <session_id>"

PERF_MEASURE-2-GET_BUFFER

2-Critical

PERF MEASURE ISSU client failed to get buffer for message. Error: [dec] [chars]

The PERF MEASURE ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

perf-measure

"show logging and show checkpoint client"

PERF_MEASURE-3-SESSION_UNREGISTRY

3-Error

PERF MEASURE ISSU client failed to unregister session information. Error: [dec] [chars]

The PERF MEASURE ISSU client failed to unregister session information.

perf-measure

"show issu session <client_id> and " "show issu negotiated capability <session_id>"

PERF_MEASURE-2-INIT

2-Critical

PERF MEASURE ISSU client initialization failed to [chars]. Error: [dec] [chars]

The PERF MEASURE ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure there will be downtime during software upgrade or downgrade.

perf-measure

LOG_STD_ACTION

PERF_MEASURE-2-SEND_NEGO_FAILED

2-Critical

PERF MEASURE ISSU client failed to send negotiation message. Error: [dec] [chars]

The PERF MEASURE ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

perf-measure

"show logging and show checkpoint client"

PERF_MEASURE-2-SESSION_REGISTRY

2-Critical

PERF MEASURE ISSU client failed to register session information. Error: [dec] [chars]

The PERF MEASURE ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly.

perf-measure

"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>"

PERF_MEASURE-3-INVALID_SESSION

3-Error

PERF MEASURE ISSU client does not have a valid registered session.

The PERF MEASURE ISSU client does not have a valid registered session.

perf-measure

"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>"

PERF_MEASURE-3-MSG_SIZE

3-Error

PERF MEASURE ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars]

The PERF MEASURE ISSU client failed to calculate the MTU for the specified message. The PERF MEASURE ISSU client is not able to send the message to the standby device.

perf-measure

"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>"

PERF_MEASURE-2-SESSION_NEGO

2-Critical

PERF MEASURE ISSU client encountered unexpected client nego_done. Error: [dec] [chars]

An ISSU-compliant client transitions through a series of internal states. The PERF MEASURE ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

perf-measure

"show issu session <client_id> and " "show issu negotiated capability <session_id>"

IPX-2-RADIXINIT

2-Critical

Error Initializing novell path structure

A programming error has occured

novell

"Please ensure that sufficient memory required to load this " "image is available in this device. If memory requirements " "are met then follow the succeeding procedure. " LOG_STD_SH_TECH_ACTION

IPX-3-BADPATHS

3-Error

Invalid number of paths [dec] for %q

An internal inconsistency was detected in the IPX routing table\n\ structure.

novell

-

IPX-3-BADRDBDATA

3-Error

Inconsistency in the [chars] LSP Linkage data structure detected.

An internal inconsistency was detected in the RDB or SRDB\n\ internal routing table structure. Specifically a data area used by\n\ NLSP to link LSPs.

novell

"Copy and save this message. If NLSP is not running this could mean\n\ there is a software or hardware problem which is corrupting memory.\n\ If the message recurs copy and save the messages and call your\n\ technical support representative for assistance."

IPX-3-BADIGRPSAP

3-Error

Cannot send incremental SAP update to peer on [chars].\n \tIncreasing output-sap-delay may help

An incremental SAP update could not be sent because this might cause\n\ the SAP tables between peers to become out of synch.

novell

"Increase the output SAP delay on the listed interface to reduce\n\ buffer usage. If after changing the delay the message remains\n\ copy the error message exactly as it appears and report it to your\n\ technical support representative."

IPX-3-BADIGRPSAPTYPE

3-Error

Unsupported SAP type for EIGRP being [chars] - type [hec]

-

novell

"Copy the error message exactly as it appears and report it to your\n\ technical support representative. If possible also provide the output\n\ of the <bold>debug ipx sap activity<nobold> and <bold>debug ipx sap event<nobold> commands for the\n\ period during which this message appeared."

IPX-3-BADCOUNT

3-Error

Bad IPX server count. [chars] [dec] [chars] [dec]

The internal SAP service count does not match the number of services\n\currently present and displayed by the <bold>show ipx servers <nobold>command.

novell

"If this message recurs report the problem to your\n\technical support representative along with the output of the <bold>show\n\ipx servers<nobold> command taken before the message appeared and again after\n\ the message appeared."

IPX-6-NOVACCESSLOG

6-Information

[chars] [chars] [chars] [chars] [hec].[enet] [chars] [hec].[enet] [dec] pkt[chars]

If IPX access violation logging is enabled these messages are\n\ displayed when an access list logging event has occurred.

novell

"Verify that the host system is permitted or denied as defined in the\n\ access list."

IPX-3-TOOMANYNETS

3-Error

Too many networks. The number of directly connected IPX networks cannot exceed [dec]

The limit of connected IPX networks has been reached.\n\ Additional IPX interfaces cannot be configured.

novell

"Do not configure IPX on additional interfaces. \n\ Remove IPX configuration commands from inactive interfaces."

IPX-3-BADINSERT

3-Error

Duplicate SAP entry insert attempted. [chars][chars] [chars]0x[hec] [chars]0x[hec] [chars][dec] [chars]0x[hec] [chars]0x[hec] [chars]0x[hec]

An IPX SAP service entry which is being added currently already exists in\n\the current internal table.

novell

"Report the error messages and the tracebacks following them to your technical\n\support representative."

IPX-3-BADHASHTABLE

3-Error

Consistency check failed for SAP table [dec].

An internal SAP table consistency check failed.

novell

"Copy the error message exactly as it appears and report it to your\n\ technical support representative."

IPX-3-NOVNOSTART

3-Error

IPX Failed to Start due to insufficient memory

The Novell IPX routing subsystem failed to initialize properly\n\ due to memory allocation errors usually due to insufficient\n\ amount of available memory.

novell

"Free up memory look for a possible memory leak or upgrade the\n\ system to have more memory."

IPX-7-DEBUGMSG

7-Debug

[chars]: %08x %08x %08x %08x %08x

Internal use only

novell

"Should not be seen in the field"

ETHER_CFM-3-CROSS_CONNECTED_CSI

3-Error

Service ID of received CC [chars] does not match local Service ID [chars].

For a given service within a domain the Service ID in the CC message should match the locally configured Service ID.

ethernet-cfm

"Verify that the service ID's are configured correctly using 'show ethernet cfm " "domain. "

ETHER_CFM-3-RCV_LOCAL_MPID

3-Error

MPID of CC matches local MPID.

The remote MPID matches a MPID configured locally for the service.

ethernet-cfm

"Either the local MPID or remote MPID should be changed as the MPID " " should be unique for a given service in a network"

ETHER_CFM-3-MEP_NOT_CONFIGURED

3-Error

received CC from unconfigured remote MEP.

While performing cross check a CC message was received from a remote MEP which is not configured under the domain submode.

ethernet-cfm

"Verify if the remote MEP should be added to the remote MEP list under the domain" " using 'show ethernet cfm domain."

ETHER_CFM-3-LR_FROM_WRONG_FP

3-Error

received Loopback Reply with correct Transaction IDentifier but from a Maintenance Point different than Loopback Message's destination

An unknown destination sent a reply to a Loopback messages that was intended to another device.

ethernet-cfm

"Verify if the correct destination mac address was specified in the Command Line Interface" " while sending Loopback Message."

ETHER_CFM-3-TM_EGRESS_BOUNDRY

3-Error

egress path found for TM is at a higher level than the traceroute message.

Traceroute found a domain boundry on egress since the egress port level is higher than the Traceroute Message level.

ethernet-cfm

"Check if the MIP level on the egress port is at appropriate level."

ETHER_CFM-6-ENTER_LCK_INT

6-Information

Interface [chars] enters LCK defect condition for [chars] direction

Interface is put in OOS state through exec cli for input direction

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-6-EXIT_LCK_INT

6-Information

Interface [chars] exited LCK defect condition for [chars] direction

Interface has exited LCK defect condition.

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-6-ENTER_LCK

6-Information

local mep with mpid [dec] level [dec] id [dec] dir [chars] Interface [chars] enters LCK defect condition

Ethernet cfm mep has entered LCK Maintenance condition. Id refers to local mep vlan id or bridge-domain id.

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-6-EXIT_LCK

6-Information

local mep with mpid [dec] level [dec] id [dec] dir [chars] Interface [chars] exited LCK defect condition

Ethernet cfm mep has exited LCK Maintenance condition. Id refers to local mep vlan id or bridge-domain id.

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-6-ENTER_AIS_INT

6-Information

Interface [chars] enters AIS defect condition for [chars] direction

Interface has entered AIS defect condition. This is due to traffic effecting indication from lower layer OAM like 802.3ah

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-6-EXIT_AIS_INT

6-Information

Interface [chars] exited AIS defect condition for [chars] direction

LOG_STD_NO_ACTION

ethernet-cfm

"Interface has existed AIS defect condition. This is due to " "clearing of traffic effecting condition and 802.3ah entering " "in send_any operational state"

ETHER_CFM-6-ENTER_AIS

6-Information

local mep with mpid [dec] level [dec] id [dec] dir [chars] Interface [chars] enters AIS defect condition

Ethernet cfm mep has entered AIS defect condition. This is due to receive of ETH-AIS or ETH-LCK frames or CCM errors causing signal fail condition. Id refers to local mep vlan id or bridge-domain id.

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-6-EXIT_AIS

6-Information

local mep with mpid [dec] level [dec] id [dec] dir [chars] Interface [chars] exited AIS defect condition

Ethernet cfm mep has exited AIS defect condition. This is due to not receiving ETH-AIS or ETH-LCK frames for expiry threshold or mep up state if LOC error happened before. Id refers to local mep vlan id or bridge-domain id.

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-5-IGNORED_VLAN

5-Notice

Ignored VLAN [dec] in '[chars]'

Invalid VLAN was ignored in the configuration.

ethernet-cfm

"LOG_STD_NO_ACTION"

ETHER_CFM-6-REMOTE_MEP_UP

6-Information

Continuity Check message is received from a remote MEP with mpid [dec] [chars] [chars] domain [chars] event code [chars].

A CC message is received from remote MEP which is up. Event code: New: A remote MEP first comes up that is when we receive a CC message from the remote MEP for the first time. Event code: Returning: The device receives a CC message from a MEP for which it has an expired CCDB entry. Event code: PortState: The device receives a CC message from a remote MEP for which it has a valid CCDB entry and the message indicates a port status change This message may be for a particular vlan or evc with the corresponding MAID or CSIID

ethernet-cfm

"Information message only."

ETHER_CFM-3-REMOTE_MEP_DOWN

3-Error

Remote MEP mpid [dec] [chars] [chars] in domain [chars] changed state to down with event code [chars].

The entry in CCDB corresponding to this MEP times out or the device receives a CC message with zero hold-time Event code: LastGasp: A valid Continuity Check message with a zero hold-time is received from a remote MEP and the device either has a valid non-expired CCDB

ethernet-cfm

"Check the remote CFM configurations using CFM " " utilities like traceroute and ping."

ETHER_CFM-3-CROSS_CONNECTED_SERVICE

3-Error

Continuity Check message with unmatched [chars] is received from a remote MEP with mpid [dec] [chars] level [dec] domain [chars] MAC: [enet].

The Continuity Check message whose CSIID or MAID is different from what is locally configured on the device for the given EVC or VLAN thereby indicating that there is a potential for having a cross-connected service in the network.

ethernet-cfm

"Configure the CFM CSI ID properly across the " "network."

ETHER_CFM-3-FORWARDING_LOOP

3-Error

Continuity Check message is received with same source MAC [enet] and mpid [dec] [chars] of its own in the [chars].

The device is receiving its own CC messages for a particular vlan or evc within the same CSI or MA.

ethernet-cfm

"Configure the CFM maintenance points properly " "to avoid the forwarding loop."

ETHER_CFM-3-CONFIG_ERROR

3-Error

CFM miss-configuration in the network. Same mpid [dec] configured within the same maintenance name [chars] having [chars] for [chars].

The same MPID as a locally configured MEP but different source MAC Address than its own. The maintenance name can be either maintenance domain or maintenance association. This message may be for a particular vlan or evc with the corresponding MAID or CSIID.

ethernet-cfm

"Configure the CFM maintenance end points properly " "by giving unique mpid in a particular maintenance " "domain or association."

ETHER_CFM-3-CROSSCHECK_MEP_MISSING

3-Error

The device does not receive any CC messages from a remote MEP with mpid [dec] [chars] that it was expecting to be part of the [chars] in the domain [chars] from MAC: [enet].

The configured remote MEP does not come up during the cross-check start timeout interval. This message may be for a particular vlan or evc with the corresponding MAID or CSIID.

ethernet-cfm

"There could be a possible fault in the network. " "Check the CFM cross check configurations are " "proper. "

ETHER_CFM-3-CROSSCHECK_MEP_UNKNOWN

3-Error

The device received a CC message from a remote MEP having mpid [dec] [chars] with MAC: [enet] that it was not expecting to be part of the [chars] in the domain: [chars].

The received remote MEP is not there in the static list configured. This message may be for a particular vlan or evc with the corresponding MAID or CSIID.

ethernet-cfm

"Check whether the CFM crosscheck configurations " "are proper."

ETHER_CFM-6-CROSSCHECK_SERVICE_UP

6-Information

The device received CC messages from all remote MEPs within a given [chars] in the maintenance domain [chars].

The service configured either CSI or MA is up as it receives CC messages from all remote statically configured MEPs.

ethernet-cfm

"Information message only."

ETHER_CFM-3-FAULT_ALARM

3-Error

A fault has occurred in the network for the local MEP having mpid [dec] vlan [dec] [chars] indicating a fault with the event code [chars].

This indicates a fault in the network. Event code: RDICCM: Remote MEP has reported RDI in CCM Event code: MACstatus: The last CCM received by this MEP from some remote MEP indicated that the transmitting MEPP's associated MAC is reporting an error status via the Port Status TLV or Interface Status TLV. Event code: RemoteCCM: This MEP is not receiving CCMs from some other MEP in its configured list. Event code: ErrorCCM: This MEP is receiving invalid CCMs. Event code: XconCCM: This MEP is receiving CCMs that could be from some other CSI or MA.

ethernet-cfm

"There could be a possible fault in the network. " "Check whether the cfm configurations are proper."

ETHER_CFM_HA-2-INIT

2-Critical

Ether CFM ISSU client initialization failed to [chars]. Error: [dec] [chars]

The Ether CFM ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure there will be downtime during software upgrade or downgrade.

ethernet-cfm

LOG_STD_ACTION

ETHER_CFM_HA-3-TRANSFORM

3-Error

Ether CFM ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars]

The Ether CFM ISSU client could not transform the specified message type. If the transmit transformation failed the checkpoint message was not sent to the standby device. If the receive transformation failed the checkpoint message was not applied on the standby device. In both cases the Ether CFM state between the active device and the standby device is not identical.

ethernet-cfm

"show issu session <client_id> and " "show issu negotiated version <session_id>"

ETHER_CFM_HA-3-MSG_NOT_OK

3-Error

Ether CFM ISSU client 'Message Type [dec]' is not compatible

The Ether CFM ISSU client received an incompatible message from the peer device. The message cannot be processed.

ethernet-cfm

"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>"

ETHER_CFM_HA-3-MSG_SIZE

3-Error

Ether CFM ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars]

The Ether CFM ISSU client failed to calculate the MTU for the specified message. The Ether CFM ISSU client will not able to send the message to the standby device.

ethernet-cfm

"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>"

ETHER_CFM_HA-3-INVALID_SESSION

3-Error

Ether CFM ISSU client does not have a valid registered session.

The Ether CFM ISSU client does not have a valid registered session.

ethernet-cfm

"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>"

ETHER_CFM_HA-2-SESSION_REGISTRY

2-Critical

Ether CFM ISSU client failed to register session information. Error: [dec] [chars]

The Ether CFM ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly.

ethernet-cfm

"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>"

ETHER_CFM_HA-3-SESSION_UNREGISTRY

3-Error

Ether CFM ISSU client failed to unregister session information. Error: [dec] [chars]

The Ether CFM ISSU client failed to unregister session information.

ethernet-cfm

"show issu session <client_id> and " "show issu negotiated capability <session_id>"

ETHER_CFM_HA-2-SESSION_NEGO

2-Critical

Ether CFM ISSU client encountered unexpected client nego_done. Error: [dec] [chars]

An ISSU-compliant client transitions through a series of internal states. The Ether CFM ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

ethernet-cfm

"show issu session <client_id> and " "show issu negotiated capability <session_id>"

ETHER_CFM_HA-2-SEND_NEGO_FAILED

2-Critical

Ether CFM ISSU client failed to send negotiation message. Error: [dec] [chars]

The Ether CFM ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

ethernet-cfm

"show logging and show checkpoint client"

ETHER_CFM_HA-2-GET_BUFFER

2-Critical

Ether CFM ISSU client failed to get buffer for message. Error: [dec] [chars]

The Ether CFM HA client failed to get buffer space for building chkpt message. Message cannot be sent to standby device. If a problem occurs the standby device cannot be brought up properly.

ethernet-cfm

"show logging and show checkpoint client"

SCVIF-2-DB_ENTRY_ALLOC_FAIL

2-Critical

SCVIF pair db entry allocation for interface [chars] failed

SCVIF pair database error. Memory chunk allocation for SCVIF pair database entry has failed.

service-controller

"Check for accurate memory management. " "Perform memory leak checks and " "look for memory corruption causes. " "Execute 'show proc memory' command."

SCVIF-2-DB_INSERT_FAIL

2-Critical

SCVIF pair db entry add for interface [chars] failed

SCVIF pair database error. Insertion of a new entry into SCVIF pair database has failed.

service-controller

"Check for accurate memory management. " "Perform memory leak checks " "look for memory corruption causes " "verify correct database management. " "Execute 'show proc memory' command."

SCVIF-2-DB_DELETE_FAIL

2-Critical

SCVIF pair db entry delete for interface [chars] failed

SCVIF pair database error. Removal of entry from SCVIF database has failed.

service-controller

"Check for accurate memory management. " "Perform memory leak checks " "look for mamory corruption causes and " "check for correct database management. " "Execute 'show proc memory' command. "

SCVIF-2-DB_ENTRY_FREE_FAIL

2-Critical

SCVIF pair entry free failed

SCVIF pair database error. Memory chunk free of SCVIF pair database entry has failed.

service-controller

"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute 'show proc memory' command."

SCVIF-2-DB_ALLOC_FAIL

2-Critical

SCVIF pair db allocation failed

SCVIF pair database error. Memory chunk creation for SCVIF pair database has failed.

service-controller

"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute 'show proc memory' command."

SCVIF-2-DB_DESTROY_FAIL

2-Critical

SCVIF pair database destroy failed

SCVIF pair database error. Memory chunk destroy has failed for SCVIF pair database.

service-controller

"Check for accurate memory management. " "Perform memory leak checks " "and look for memory corruption causes. " "Execute show proc memory command."

APPNAV_CONTROLLER-2-SC_SN_UNREACHABLE

2-Critical

APPNAV-CONTROLLER: Alarm #29007 Severity: Major. SN: [chars] is unreachable

Service context has entered Operational state and there is at least one configured node that is not part of the SN view.

service-controller

"Check status of configured SNs."

APPNAV_CONTROLLER-4-SC_SN_REACHABLE

4-Warning

APPNAV-CONTROLLER: Alarm #29007 cleared. SN: [chars] is reachable

Service Node is available

service-controller

"None. All is well"

APPNAV_CONTROLLER-5-SC_MIXED_FARM

5-Notice

APPNAV-CONTROLLER: Alarm #29003 Severity: Minor

When an appnav controller detects upon that there are other appnav-controllers/SNs in the cluster with different ICIMP/DMP minor version number.

service-controller

"Check versions of SNs in network."

APPNAV_CONTROLLER-5-SC_MIXED_FARM_CLEAR

5-Notice

APPNAV-CONTROLLER: Alarm #29003 cleared

There are no appnav-controllers/SNs with different ICIMP/DMP minor version number

service-controller

"None. All is well"

APPNAV_CONTROLLER-2-SNG_UNAVAILABLE

2-Critical

APPNAV-CONTROLLER: Alarm #30001 Severity: Major. SNG: [chars] unavailable

No SN in appnav node group is available for optimization.

service-controller

"Check status of configured nodes."

APPNAV_CONTROLLER-4-SNG_AVAILABLE

4-Warning

APPNAV-CONTROLLER: Alarm #30001 Cleared SNG: [chars] available

SN's in appnav node group is available for optimization.

service-controller

"None. All is well"

APPNAV_CONTROLLER-2-SNG_AO_UNAVAILABLE

2-Critical

APPNAV-CONTROLLER: Alarm #30000Severity: Major. In SNG: [chars] AO: [dec] is unavailable

No node in service node group is available for optimization and traffic is getting optimized by a secondary SNG.

service-controller

"Check status of configured SNs."

APPNAV_CONTROLLER-4-SNG_AO_AVAILABLE

4-Warning

APPNAV-CONTROLLER: Alarm #30000 cleared. In SNG: [chars] AO: [dec] is available

Service node group is available for optimization

service-controller

"None. All is well"

APPNAV_CONTROLLER-2-SC_CONVERGENCE_FAILED

2-Critical

APPNAV-CONTROLLER: Alarm #29001 Severity: Major

CMM is not coming out of convergence state

service-controller

"Check connectivity between SN's and AC's"

APPNAV_CONTROLLER-4-SC_CONVERGENCE_SUCCESS

4-Warning

APPNAV-CONTROLLER: Alarm #29001 cleared

CMM convergence completed

service-controller

"None. All is well"

APPNAV_CONTROLLER-2-SC_DEGRADED_CLUSTER

2-Critical

APPNAV-CONTROLLER: Alarm #29002 Severity: Critical. AC: [chars] is Degraded

Mismatch of stable AC views between AC's

service-controller

"Check connectivity between AC's"

APPNAV_CONTROLLER-4-SC_CLUSTER_STABLE

4-Warning

APPNAV-CONTROLLER: Alarm #29002 cleared. AC: [chars] is Stable

Mismatch of stable AC views between AC's

service-controller

"None. All is well"

APPNAV_CONTROLLER-2-SC_SC_UNREACHABLE

2-Critical

APPNAV-CONTROLLER: Alarm #29006 Severity: Major. AC: [chars] unreachable

Connectivity with AC's under ACG is lost

service-controller

"Make sure AC's configured under ACG are up" " and reachable"

APPNAV_CONTROLLER-4-SC_SC_REACHABLE

4-Warning

APPNAV-CONTROLLER: Alarm #29006 cleared. AC: [chars] reachable

Connectivity with AC's under ACG is regained

service-controller

"None. All is well"

APPNAV_CONTROLLER-2-SC_SN_EXCLUDED

2-Critical

APPNAV-CONTROLLER: Alarm #29008 Severity: Major. SN: [chars] excluded

Stable SN views across AC's are different. Those SN's that are not reachable by other AC's are exlcuded

service-controller

"Make sure excluded SN's are reachable from " "all AC's"

APPNAV_CONTROLLER-4-SC_SN_INCLUDED

4-Warning

APPNAV-CONTROLLER: Alarm #29008 cleared. SN: [chars] included

SN is reachable again

service-controller

"None. All is well"

APPNAV_CONTROLLER-2-ACG_IP_CHANGED

2-Critical

APPNAV-CONTROLLER: Alarm #10000 Severity: Major \nAppnav controller group IP address changed! All relevant service contexts will be disabled

Appnav controller group IP address changed! All relevant service contexts will be disabled

service-controller

"Change AppNav Controller's IP "

APPNAV_CONTROLLER-6-CM_REGISTER_SUCCESS

6-Information

AppNav registered with Central Manager successfully

Received a registration success message from the Central Manager

service-controller

"None. All is well"

APPNAV_CONTROLLER-3-CM_REGISTER_FAILED

3-Error

AppNav registration with Central Manager failed for the following reason: [chars]

Received a registration failure message from the AppNav Central Manager. AppNav has not registered with the Central Manager

service-controller

"Issue the " "<CmdBold>debug waas management errors<NoCmdBold> " "command and the " "<CmdBold>debug waas management events<NoCmdBold> " "Contact your Cisco technical support representative" " and provide the representative with the gathered information."

APPNAV_CONTROLLER-4-SERVICE_CTX_DISABLE

4-Warning

SERVICE-CONTROLLER: Alarm 10001 Severity: Major \n Disabling service context [chars]

Disabling service context

-

-

MDR_SM_LC-3-INIT_FAIL

3-Error

Initialisation error '[chars]'

During MDR SM initialisation an error has occurred that has rendered the MDR SM inoperable. an MDR operation will likely result in the resetting of this line card

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-3-NOTIFY_TIMEOUT

3-Error

Notification timeout for client [chars][dec] in state [chars]

During MDR SM state transition the notification timer expired for the client. Any MDR operation will likely result in the resetting of this line card

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-3-ABORT

3-Error

MDR state machine is aborted due to '[chars]'

MDR state machine is aborted due to an unrecoverable error. Any MDR operation will likely result in the resetting of this line card

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-3-SEMWAIT

3-Error

MDR state machine waiting for semaphore[chars] acquired by pid[dec]

SEMWAIT_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-3-INVALID_EVENT

3-Error

MDR SM LC received an unexpected event [chars] in state [chars]

INVALID_EVENT_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-3-ID_MISMATCH

3-Error

Client ID mismatch during progression on client: [dec] expecting [dec]

ID_MISMATCH_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-3-STATUS_INVALID

3-Error

Client [chars] [dec] returned an unexpected status code [dec]

STATUS_INVALID_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-3-NO_FREE_EVENT_IN_QUEUE

3-Error

The event queue is full for MDR SM MDR SM will abort

NO_FREE_EVENT_IN_QUEUE_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_LC-4-CALLBACK_TOO_MUCH_TIME

4-Warning

MDR SM LC client [chars] [dec] spent too much time [dec] msecs in \

CALLBACK_TOO_MUCH_TIME_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_PROXY-3-NOTIFY_TIMEOUT

3-Error

Notification timeout on MDR [chars] state machine for the remote client '[chars]'

MDR SM Proxy master is unable to communicate with its slave. It did not get any answer to the notification on the slave. An error has occurred that has rendered the MDR SM inoperable. An MDR operation will likely result in the resetting of all Line Cards.

mdr-sm

LOG_STD_ACTION

MDR_SM_PROXY-4-SYS_CALLBACK_TOO_MUCH_TIME

4-Warning

MDR SM SYS client [dec] spent too much time [dec] msecs in \

CALLBACK_TOO_MUCH_TIME_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM_PROXY-4-SLOT_CALLBACK_TOO_MUCH_TIME

4-Warning

MDR SM Slot [dec] client [dec] spent too much time [dec] msecs in \

CALLBACK_TOO_MUCH_TIME_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-INIT_FAIL

3-Error

Initialisation error '[chars]'

During MDR SM initialisation an error has occurred that has rendered the MDR SM inoperable. an MDR operation will likely result in the resetting of all Line Cards.

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-4-QUIESCE_FAIL

4-Warning

Quiesce watchdog timer expired continuing with MDR

At switchover on the old Active RP the MDR SM enters the Quiesce state. While this is occuring the reload of the old Active is blocked which in effect blocks the switchover from taking place. Therefore to prevent a loss of service due to a bug in the MDR SM or one of its clients a watchdog timer ensures that we won't stay in this state for too long.

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-4-UNBLOCK_RF

4-Warning

MDR SM aborted continuing RF Progression [dec]

The MDR State Machine aborts due to a bug in the MDR State Machine or one of its clients. The RF progression was blocked it will be unblocked to allow the standby to boot

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_NO_FREE_EVENT_IN_QUEUE

3-Error

The event queue is full for MDR System SM MDR SM will abort

NO_FREE_EVENT_IN_QUEUE_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_NO_FREE_EVENT_IN_QUEUE

3-Error

The event queue is full for MDR Slot SM [dec] MDR Slot SM [dec] will abort

NO_FREE_EVENT_IN_QUEUE_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_NOTIFY_TIMEOUT

3-Error

Notification timeout on MDR system state machine for the local client [chars] [dec] in state [chars]

NOTIFY_TIMEOUT_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_NOTIFY_TIMEOUT

3-Error

Notification timeout on MDR slot state machine [dec] for the local client [chars] [dec] in state [chars]

NOTIFY_TIMEOUT_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_EVENT_TIMEOUT

3-Error

MDR slot state machine [dec] did not receive the SLOT_UP event from the linecard

Slot MDR SM did not get an expected event form the linecard. This error has rendered this slot MDR SM inoperable

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_CLIENT_ID_ERROR

3-Error

Can not find the data associated to client ID [dec]

CLIENT_ID_ERROR_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_CLIENT_ID_ERROR

3-Error

Can not find the data associated to client ID [dec] for slot [dec]

CLIENT_ID_ERROR_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_STATUS_INVALID

3-Error

Client [chars] [dec] returned an unexpected status code [dec]

STATUS_INVALID_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_STATUS_INVALID

3-Error

Client [chars] [dec] on slot [dec] returned an unexpected status code [dec]

STATUS_INVALID_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_CONTINUE_INVALID

3-Error

Client [dec] returned an invalid status code

CONTINUE_INVALID_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_CONTINUE_INVALID

3-Error

Client [dec] returned an invalid status code on slot [dec]

CONTINUE_INVALID_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_ID_MISMATCH

3-Error

Client ID mismatch during progression [chars] on client: [dec] expecting [dec]

ID_MISMATCH_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_ID_MISMATCH

3-Error

Client ID mismatch for slot [dec] during progression [chars] on client: [dec] expecting [dec]

ID_MISMATCH_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_NOTIFY_STANDBY_FAILED

3-Error

Failed to notify Standby for MDR system state machine Client [chars] [dec] in state [chars]

NOTIFY_STANDBY_FAILED_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_NOTIFY_STANDBY_FAILED

3-Error

Failed to notify Standby for MDR slot state machine [dec]

NOTIFY_STANDBY_FAILED_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SYS_INVALID_EVENT

3-Error

Received an unexpected event [chars] in state [chars]

INVALID_EVENT_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_INVALID_EVENT

3-Error

Slot [dec] received an unexpected event [chars] in state [chars]

INVALID_EVENT_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-3-SLOT_INVALID_ARG

3-Error

Process is unable to get his slot number

MDR State Machine creates one process per slot \ supporting MDR. In that case the process is \ unable to get his slot.

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-4-SYS_CALLBACK_TOO_MUCH_TIME

4-Warning

MDR SM SYS client [chars] [dec] spent too much time [dec] msecs in \

CALLBACK_TOO_MUCH_TIME_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDR_SM-4-SLOT_CALLBACK_TOO_MUCH_TIME

4-Warning

MDR SM Slot [dec] client [chars] [dec] spent too much time [dec] msecs in \

CALLBACK_TOO_MUCH_TIME_EXPLANATION

mdr-sm

MDR_SM_LOG_STD_ACTION

MDNSPROXY-3-INIT_MDNS_FAIL

3-Error

[chars] Initialisation failure.

An internal error occurred during mDNS initialisation.

mDNS

LOG_STD_ACTION

MDNSPROXY-3-PORT_RESERVED_MDNS

3-Error

[chars] Initialisation failure.

UDP Port 5353 Already reserved. Please disable the feature which uses 5353 and And Try Again.

mDNS

LOG_STD_ACTION

MDNSPROXY-3-CHUNK_MEMORY_FAIL

3-Error

Chunk memory allocation failed

Chunk memory allocation failed for Cache element

mDNS

LOG_STD_ACTION

MDNSPROXY-3-API_FAIL_MDNS

3-Error

[chars] API failed

An error occurred while calling the APIs.

mDNS

LOG_STD_ACTION

MDNSPROXY-3-NULL_CONTEXT_ID_MDNS

3-Error

Encountered a NULL context for the ID [dec]

NULL context for the ID passed in id_to_ptr.

mDNS

LOG_STD_ACTION

MDNSPROXY-3-OS_API_FAIL_MDNS

3-Error

IOS API [chars] failed

Whitelist pattern length cannot exceed 100 for DSA snooping.

ios-scansafe

"This message is for informational purposed only"

CGC-0-CGC_EMERG

0-Emergency

[chars]

CGC_INTERNAL_ERROR

CGC_DDTS_COMPONENT

LOG_STD_ACTION

CGC-1-CGC_ALERT

1-Alert

[chars]

CGC_INTERNAL_ERROR

CGC_DDTS_COMPONENT

LOG_STD_ACTION

CGC-2-CGC_CRIT

2-Critical

[chars]

CGC_INTERNAL_ERROR

CGC_DDTS_COMPONENT

LOG_STD_ACTION

CGC-3-CGC_ERR

3-Error

[chars]

CGC_INTERNAL_ERROR

CGC_DDTS_COMPONENT

LOG_STD_ACTION

CGC-4-CGC_WARNING

4-Warning

[chars]

CGC_INTERNAL_ERROR

CGC_DDTS_COMPONENT

LOG_STD_ACTION

CGC-5-CGC_NOTICE

5-Notice

[chars]

Normal but significant conditions

CGC_DDTS_COMPONENT

LOG_STD_ACTION

CGC-6-CGC_INFO

6-Information

[chars]

Informational messages

CGC_DDTS_COMPONENT

LOG_STD_NO_ACTION

CGC-7-CGC_ASSERT

7-Debug

Assertion Failure [chars] @[chars]:[dec] : [chars]

CGC_INTERNAL_ERROR

CGC_DDTS_COMPONENT

LOG_STD_ACTION

TRANSCEIVER-6-REMOVED

6-Information

Transceiver module removed from [chars]

The online insertion and removal OIR facility detected the

spa-infra

LOG_STD_NO_ACTION

TRANSCEIVER-6-INSERTED

6-Information

transceiver module inserted in [chars]

The online insertion and removal OIR facility detected a

spa-infra

LOG_STD_NO_ACTION

TRANSCEIVER-3-CHECKSUM_ERROR

3-Error

Detected in the transceiver module in [chars] module disabled

A checksum error was detected when reading the ID PROM of a transceiver module for the interface specified in the error message. As a result of the error the module is disabled.

spa-infra

"Try reseating the module. If the problem persists LOG_STD_ACTION."

TRANSCEIVER-3-IMPROPER_INSERTION

3-Error

Transceiver module in [chars] not fully inserted remove the transceiver and re-insert with proper seating lock.

An initialization failure occurred for the transceiver module for the interface specified in the error message. This condition is caused by improper insertion of transceiver As a result of the error the module is disabled.

spa-infra

"Try OIR'ing the module and reseat properly. "

TRANSCEIVER-3-INIT_FAILURE

3-Error

Detected for transceiver module in [chars] module disabled

An initialization failure occurred for the transceiver module for the interface specified in the error message. This condition could be caused by software firmware or hardware problem. As a result of the error the module is disabled.

spa-infra

"Try reseating the module. " "Hardware replacement should not occur first occurrence. " "Before requesting hardware replacement review troubleshooting logs " "with a Cisco technical support representative. "

TRANSCEIVER-3-NOT_COMPATIBLE

3-Error

Detected for transceiver module in [chars] module disabled

The transceiver module for the interface specified in the error message is not compatible with the interface. As a result of the error the module is disabled.

spa-infra

"Replace the module with a compatible transceiver. If the problem " "persists LOG_STD_ACTION."

TRANSCEIVER-3-NOT_IDENTIFIED

3-Error

Detected for transceiver module in [chars] module disabled

The transceiver module for the interface specified in the error message could not be identified and may not be compatible with the interface. As a result of the error the module is disabled.

spa-infra

"Replace the module with a compatible transceiver. If the problem " "persists LOG_STD_ACTION."

TRANSCEIVER-3-NOT_SUPPORTED

3-Error

Detected for transceiver module in [chars] module disabled

The transceiver module for the interface specified in the error message is not a cisco supported module. As a result of the error the module is disabled.

spa-infra

"Replace the module with a cisco supported transceiver. If the problem " "persists LOG_STD_ACTION."

TRANSCEIVER-3-ATTACH_FAILURE

3-Error

Detected for transceiver module in [chars] module disabled

A software device driver attach failed. This condition could be caused by software firmware or hardware problem but a software or firmware problem is more likely. As a result of the error the module is disabled.

spa-infra

"Try reseating the module. " "Hardware replacement should not occur first occurrence. " "Before requesting hardware replacement review troubleshooting logs " "with a Cisco technical support representative. "

TRANSCEIVER-3-SM_CREATION_FAILURE

3-Error

Transceiver OIR State Machine creation failed for [chars] module disabled.

A state machine could not be created for the transceiver OIR operation. If a %SYS-2-MALLOCFAIL message was also received with this message this condition indicates insufficient system memory. Other possible causes include invalid subblock pointer.

spa-infra

"If it is insufficient system memory " LOG_STD_REDUCE_ACTION "If this message recurs " LOG_STD_ACTION

TRANSCEIVER-3-OPER_ENABLE_FAILURE

3-Error

Detected for transceiver module in [chars] module disabled

Failed to enable the transceiver module for the interface specified in the error message. This condition could be caused by software firmware or hardware problem. As a result of the error the module is disabled.

spa-infra

"Try reseating the module. " "Hardware replacement should not occur first occurrence. " "Before requesting hardware replacement review troubleshooting logs " "with a Cisco technical support representative. "

TRANSCEIVER-3-RPC_PROCESSING_ERROR

3-Error

Transceiver RPC error: [chars]

Non Fatal error occured in processing an RPC messsage.

spa-infra

show version

TRANSCEIVER-3-RPC_INIT_FAIL

3-Error

Transceiver RPC init failure

The system failed to create the resources required to process user\n\ interface commands for transceivers. The error is not fatal but some \n\ \show\ commands could fail.

spa-infra

show version

TRANSCEIVER-3-RPC_FAILED

3-Error

Application error rc = [dec] in port [chars]

The system failed to retrieve the information required to execute\n\ the comand

spa-infra

show version

TRANSCEIVER-3-DEV_PLUGGABLE_OPTICS

3-Error

Transceiver [chars] table internally inconsistent @ 0x[hec]

One of the transceiver attribute table is not properly updated.

spa-infra

"This is a debug message."

LIC_AGENT-3-MEMORY

3-Error

[chars]

License Agent subsystem has experienced a problem gettting the required \ memory to complete this operation.

lic_agent

"Check system memory for other memory allocation errors and contact \ Technical support for problem resolution. In the absence of IOS errors \ upgrading the memory in the network device may be required."

LIC_AGENT-3-UNKNOWN_EVENT

3-Error

event [dec] [chars]

License Agent tried to execute an unknown event.

lic_agent

"Contact technical support for problem resolution."

PCE-5-PCE_STATE

5-Notice

Connection to PCE server:[chars] [chars]

The connection to PCE server changed state.

-

"If the state change was unexpected check connectivity and state of the PCE server"

PCE-5-PCE_ERR_RX

5-Notice

PCEP peer [chars] sent PCError message - type: [dec] value: [dec]

PCErr message was received from peer

-

"Verify PCEP protocol operation"

SPA_PLUGIN-3-FIRMWARE_BADPATH

3-Error

[chars]: Invalid firmware file path [chars].

Specified fireware file path is invalid. This is a software error.

spa-ser-infra

LOG_STD_ACTION

SPA_PLUGIN-3-FIRMWARE_NOMEMORY

3-Error

[chars]: Insufficient memory for firmware file [chars] size [dec].

Can not allocate memory for firmware image for downloading to SPA.

spa-ser-infra

LOG_STD_REDUCE_ACTION

SPA_PLUGIN-3-FIRMWARE_BADIMAGE

3-Error

[chars]: Firmware file [chars] read failed.

Firmware image pointed by the path is not valid.

spa-ser-infra

LOG_STD_ACTION

SPA_PLUGIN-3-FIRMWARE_DOWNLOAD

3-Error

[chars]: Firmware download failed.

Failed to download firmware image to SPA. It is caused by either lack of memory on SPA IPC failures improperly seated SPA or other download errors.

spa-ser-infra

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-6-FIRMWARE_DOWNLOADING

6-Information

[chars]: Downloading SPA firmware [chars]...

Downloading SPA firmware.

-

"None. Information only."

SPA_PLUGIN-3-FIRMWARE_STARTUP

3-Error

[chars]: Firmware startup failed. SPA status0x%08x host status0x%08x

Can not start Firmware image downloaded to SPA. Possible causes are either bad image on SIP flash disk hardware failures or outdated FPGA and/or ROMMON image.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-FIRMWARE_APPS_DOWNLOAD

3-Error

[chars]: Firmware application download failed.

Failed to download application image to SPA. It may be caused by either lack of memory on SPA IPC failures improperly seated SPA or other download errors.

spa-ser-infra

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-6-FIRMWARE_APPS_DOWNLOADING

6-Information

[chars]: Downloading SPA firmware application [chars]...

Downloading SPA firmware application .

-

"None. Information only."

SPA_PLUGIN-3-FIRMWARE_APPS_STARTUP

3-Error

[chars]: Firmware application startup failed. SPA status0x%08x host status0x%08x

Can not start application image downloaded to SPA. Possible causes might be either bad image on SIP flash disk hardware failure or outdated FPGA and/or ROMMON image.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-FILE_ERROR

3-Error

[chars]: Error accessing file [chars].

Specified file is not found lack of permission out of space or other file system/device errors.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-FILE_TRANSFER

3-Error

[chars]: Failed to transfer file to or from SPA.

Failed to transfer a file to or from SPA. It might be caused by lack of memory on SPA or jacket card IPC failures improperly seated SPA or other errors.

spa-ser-infra

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-3-PLIM_CREATE

3-Error

[chars]: PLIM subblock creation failed.

Can not allocate memory for PLIM structure.

spa-ser-infra

LOG_STD_REDUCE_ACTION

SPA_PLUGIN-3-NOPLIM

3-Error

[chars]: No PLIM subblock.

Invalid pointer was passed in. Can not dereference PLIM subblock pointer. Internal error.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-RETRY_EXHAUSTED

3-Error

[chars]: plugin initialization failedretries exhausted.

One or more critical conditions happened that prevented plugin initialization from moving forward after designated number of retries. Preceeding messages may indicated failure cause.

-

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-FAILED

3-Error

[chars]: Plugin initialization failed.

Plugin initialization can fail for many reasons. Preceding messages may state the cause.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-NULL_SPA_PTR

3-Error

-

Pointer to a SPA object is NULL.

spa-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-SPI4_CREATE

3-Error

[chars]: Device SPI4 creation failed.

Can not allocate memory for SPI4 structure.

spa-ser-infra

LOG_STD_REDUCE_ACTION

SPA_PLUGIN-3-UART_CREATE

3-Error

[chars]: Device UART creation failed.

Can not allocate memory for UART structure.

spa-ser-infra

LOG_STD_REDUCE_ACTION

SPA_PLUGIN-3-SPI4_SETCB

3-Error

[chars]: IPC SPI4 set callback failedstatus [dec].

Can not setup a callback function for SPI4 bus. It might be caused by improperly seated SPA outdated or a hardware failure.

spa-ser-infra

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-3-SPI4_SETCB_PORT

3-Error

[chars]: IPC SPI4 set callback failederror: [dec] for port [dec].

Can not setup a callback function for SPI4 bus for the specified interface port. It might be caused by improperly seated SPA outdated ROMMON/FPGA or a hardware failure.

spa-ser-infra

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-3-SPI4_CONFIG

3-Error

[chars]: Can not configure host side SPI4 profile.

SPI4 configuration from modular services card failed. It indicates either lack of system memory a hardware failure or an outdated ROMMON/FPGA image.

-

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-SPI4_NOTSYNC

3-Error

[chars]: Can not synchronize SPI4 bus.

SPI4 bus between modular services card and SPA is not synchronized. It indicates either a not properly seated SPA a hardware failure or an outdated ROMMON/FPGA image.

-

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-6-SPI4_SYNC

6-Information

[chars]: SPI4 bus synchronization achieved.

SPI4 bus between modular services card and SPA is synchronized.

-

"None. Information only."

SPA_PLUGIN-3-SPI4_INIT

3-Error

[chars]: SPI4 initializaion failed.

-

-

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-ENV_INIT

3-Error

[chars]: Environment monitoring initialization failed.

-

-

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-EFC_NOTSYNC

3-Error

[chars]: Can not synchronize EFC bus.

Extended flow control between modular services card and SPA is not synchronized. SPA is shut down. It indicates either a not properly seated SPA a hardware failure or an outdated ROMMON/FPGA image.

-

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-6-EFC_SYNC

6-Information

[chars]: EFC bus synchronization achieved.

Extended flow contorl between modular services card and SPA is synchronized.

-

"None. Information only."

SPA_PLUGIN-3-EXCEPTION

3-Error

[chars]: Exception with cause [dec].

One of SPA software components crashes.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-AUXC2W_CREATE

3-Error

[chars]: Device auxiliary C2W creation failed.

Can not allocate memory for auxiliary C2W structure.

-

LOG_STD_REDUCE_ACTION

SPA_PLUGIN-4-LED_CREATE

4-Warning

[chars]: LED driver initialization failed.

Can not allocate memory for LED structure.

-

LOG_STD_REDUCE_ACTION

SPA_PLUGIN-4-LED_READ

4-Warning

[chars]: LED read failed for port [dec] status [dec].

Can not read LED register values. It indicates either a not properly seated SPA or a hardware failure

-

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-4-LED_WRITE

4-Warning

[chars]: LED write failed for port [dec] status [dec].

Can not write to LED register. It indicates either a not properly seated SPA or a hardware failure

-

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-3-EEPROM_READ

3-Error

[chars]: Error reading EEPROM.

Can not read EEPROM content. It indicates either a not properly seated SPA or a hardware failure

-

SPA_STD_RESEAT_ACTION

SPA_PLUGIN-3-IOFPGA_CREATE

3-Error

[chars]: Device IOFPGA creation failed.

Can not allocate memory for IOFPGA structure.

-

LOG_STD_REDUCE_ACTION

SPA_PLUGIN-3-ROMMON

3-Error

[chars]: ROMMON reports error. SPA status0x%08x host status0x%08x.

ROMMON has reported a fatal condition during boot up. It may be caused by outdated ROMMON/FPGA images or defected hardware.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLUGIN-3-NOPORT

3-Error

[chars]: Failed to open IPC port.

PLIM client IPC port has not been initialized.

spa-ser-infra

show ipc status

SPA_PLUGIN-3-ALLOC_ERR

3-Error

[chars]: Failed to allocate memory

Failed to allocate the required memory for the data

spa-infra

show ipc status

SPA_CCB-3-CMDFAIL_0ARG

3-Error

[chars]: host command [dec] error: [chars].

A command from host failed to execute for the given reason.

-

LOG_STD_SH_TECH_ACTION

SPA_CCB-3-CMDFAIL_1ARG

3-Error

[chars]: host command [dec]arg0=[dec] error: [chars].

A CCB command failed to execute for the given reason.

-

LOG_STD_SH_TECH_ACTION

SPA_CCB-3-CMDFAIL_2ARG

3-Error

[chars]: host command [dec]arg0=[dec] arg1=[dec] error: [chars].

A command from host failed to execute for the given reason.

-

LOG_STD_SH_TECH_ACTION

SPA_CCB-3-CMDFAIL_3ARG

3-Error

[chars]: host command [dec]arg0=[dec] arg1=[dec] arg2=[dec] error: [chars].

A command from host failed to execute for the given reason.

-

LOG_STD_SH_TECH_ACTION

SPA_CCB-3-CMD_TOOEARLY

3-Error

[chars]: host command [dec] received before handler ready.

Host command comes before handler is initialized

-

LOG_STD_SH_TECH_ACTION

SPA_CCB-3-ENQUEUE_FAIL

3-Error

[chars]: host command [dec] failed to enqueue.

An error occurred while the SPA console was attempting to enqueue a host command to command queue.

-

LOG_STD_SH_TECH_ACTION

SPA_CCB-3-IF_CONFIG

3-Error

[chars]: IF_CONFIG type [dec] failed.

Interface configuration type not valid for SPA card.

-

LOG_STD_SH_TECH_ACTION

SPA_CCB-4-BADENCAP

4-Warning

[chars]: Unknown encapsulation command [dec].

An invalid encapsulation command is received by SPA. This is a software error.

-

LOG_STD_SH_TECH_ACTION

SPA_MIB-4-DATA_LEN

4-Warning

[chars]: MIB message lengths mismatch[chars] expecting [dec] bytes receiving [dec].

MIB updates expect more data than received.

spa-ser-infra

LOG_STD_SH_TECH_ACTION

SPA_PLIM-4-EXCEPTION

4-Warning

[chars] has experienced an exception: [chars]. Writing SPA crash dump information to [chars].

The local CPU in the specified slot indicated in the message has experienced the exception condition. The process that caused the exception might have been restarted. If an exception core dump was created core dump is stored in the SIP flash if available.

-

"If the system continues running normally no action is required. " "If this message recurs or system behaves abnormally please " "collect the crash dump file from SIP flash capture the output of " "the <CmdBold>show hw-module slot/subslot tech-support<NoCmdBold> " "command and open a case with the Technical Assistance Center via " "http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl."

SPA_PLIM-3-FW_RELOAD

3-Error

[chars] is being reloaded due to firmware/application exception.

Firmware application failed at SPA. The SPA is being reloaded to recover its operational state.

spa-ser-infra

"Collect the application core file from flash. Core file name is " "shown in the preceding message with timestamp."

SPA_PLIM-5-RECEIVINGFILE

5-Notice

Receiving [chars] from [chars] and storing to [chars].

SPA has sent a file syslog or core dump to RP and

-

LOG_STD_DBG_ACTION

SPA_PLIM-3-HEARTBEAT

3-Error

[chars] has experienced an heartbeat failure. Current Sequence [dec] Received Sequence [dec] Time since last keep [dec]ms.

The IPC communication between local CPU and host in the specified slot indicated in the message is not functional. The IPC module will be restarted. Following which communication might be re-established. If the problem persists the SPA will be reset.

-

"If the system continues running normally no action is required. " "If this message recurs or system behaves abnormally please " "collect the logs from the systemRP/SIP. Capture the output of "

SPA_PLIM-3-INITFAIL

3-Error

[chars] has failed initialization because SPA [chars].

A failure occurred during the SPA initialization. SPA is not functional and may be restarted by RP or SIP.

-

"If the SIP or RP successfully initialized the SPA " "no action is required. If the SPA was not successfully " "initialized " LOG_STD_ACTION

SPA_PLIM-3-INIT_PORT

3-Error

[chars] PLIM client IPC port has not been initialized.

-

spa-ser-infra

show ipc status

SPA_PLIM-3-FATALERROR

3-Error

SPA in slot [dec] bay [dec] experienced a fatal error [chars] and is being reset.

A fatal error was encountered during SPA operation. The SPA may be restarted.

-

"If the error is not observed more than once it might be " "a one off event and the SPA needs to be monitored. " "If the issue occurs repeatedly " LOG_STD_ACTION

SPA_PLIM-4-SBE_ECC

4-Warning

[chars] reports [dec] SBE occurance at [dec] addresses

SPA has reproted single bit correctable ECC errors.

spa-ser-infra

"The log shows more than 1 SBE has occurred. " "SBEs are correctable memory problems. It will not affect router operation." "Excessive occurances indicate potential memory defections. Standard " "action is to watch at first occurance and replace at the first chance " "when recurs."

SPA_PLIM-4-SBE_OVERFLOW

4-Warning

[chars] SBE table[dec] elements overflows.

SPA has reproted more unique single bit correctable ECC errors than the platform defined internal table can hold.

spa-ser-infra

"Replace the fault memory chip at the earliest " "chance. SBEs are correctable memory problems. It will not affect router " "operation. Excessive occurances indicate potential memory defections."

SPA_PLIM-3-FILEFORWARD_FAIL

3-Error

[chars] failed to transfer a file from SPA to router flash due to IPC [chars].

A file transfer failed due to IPC errors. The file has not been stored in the flash.

spa-ser-infra

"Check flash disk for empty storage space. If it " "is short of space remove some files from the flash. If the message " "occurs repeatedly " LOG_STD_ACTION

SPA_PLIM-3-FILECREATE_FAIL

3-Error

NULL

Check router and make sure it has installed removable flash card or disk e.g. <CmdArg>disk0:<NoCmdArg> <CmdArg>disk1:<NoCmdArg> <CmdArg>slot0:<NoCmdArg> etc.. If the flash is present make sure

spa-ser-infra

"Check router removable disk and make sure it has empty " "storage space. If the flash disk is short of space remove some files from " "the flash. If the message occurs repeatedly " LOG_STD_ACTION

SPA_PLIM-3-FILE_NOTSTORED

3-Error

NULL

This error is seen when storing a file for a SPA to router removable flash failed. The partial file is removed from router removable flash.

spa-ser-infra

"If the error message occurs repeatedly " LOG_STD_ACTION

SPA_PLIM-3-SW_ERROR

3-Error

NULL

-

spa-ser-infra

LOG_STD_ACTION

SPA_PLIM-3-ERRMSG

3-Error

[chars] [chars]

The error message in parentheses was logged by the SPA.

-

SPA_STD_SH_TECH_ACTION

SPA_DATABUS-3-SPI4_UNALIGNED_BURST

3-Error

[chars] [chars] - An error on the data bus has occurred.

In normal situation transitions from the Data Burst state to payload control or idle control are possible only on integer multiples of 8 cycles or upon end of packet. This error could happen if the MW bit flips on the bus with coincidental good dip4 or due to a misbehaving source.

spa-infra

"Power down and reseat the card. " SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_SINGLE_DIP4_PARITY

3-Error

[chars] [chars] - A single DIP4 parity error has occurred on the data bus.

A single parity error has occurred on the data bus between the SPA and the SIP. When this condition is occurring a short duration of packet loss and/or symptoms resulting from data corruption may occur. This condition may indicate a developing hardware failure. This error should occur very infrequently during normal operation and should not occur when no changes are made to the configuration.

spa-infra

"Power down and reseat the interface card. " SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_OUT_OF_FRAME

3-Error

[chars] [chars] - A data bus out of frame error condition has occurred

An error has occurred on the data bus between the SPA and the SIP. When this condition is occurring the interface will be down and/or not forward any traffic.

spa-infra

"Power down and reseat the card. " SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_SEQUENCE

3-Error

[chars] [chars] - A sequence error has occurred.

A sequence error has occurred on the data bus between the SPA and the SIP. When this condition is occurring a short duration of packet loss may be noticed. This condition may indicate a developing hardware failure. This error should occur very infrequently during normal operation and should not occur when no changes are made to the configuration.

spa-infra

SPI4_STD_ACTION

SPA_DATABUS-3-PACKET_GAP_ERROR

3-Error

[chars] [chars] - A packet gap error has occurred

The data bus interface on this line card is experiencing a hardware-related issue. No loss of data or data corruption should occur. Packets should continue to be forwarded.

spa-infra

SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_SINGLE_DIP2_PARITY

3-Error

[chars] [chars] - A single DIP 2 parity error on the FIFO status bus has occurred.

The data bus interface on this line card is experiencing a hardware-related issue. Some packets may be dropped.

spa-infra

SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_FIFO_STATUS_BUS

3-Error

[chars] [chars] - FIFO status bus out of frame condition has occurred.

The data bus interface on this line card is experiencing a hardware-related issue. When this condition is occurring the interface will be down and/or not forward any traffic.

spa-infra

SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_BAD_CHAN_NUM

3-Error

[chars] [chars] - An error condition on the SPA data bus has occurred.

An error condition on the SPA data bus has occurred. This condition can be caused by a software fault only.

spa-infra

SPI4_BUGTOOLKIT_ACTION

SPA_DATABUS-3-SPI4_CALENDAR_LEN

3-Error

[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.

An error condition on the data bus between the SPA and the SIP has occurred. This condition results from a software fault.

spa-infra

SPI4_BUGTOOLKIT_ACTION

SPA_DATABUS-3-SPI4_CRTL_WD_NO_DIP4

3-Error

[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.

This message points to an error condition on the SPA data bus. Symptoms of this error include data corruption and/or a short duration of data loss.

spa-infra

SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_BAD_CNTR_WORD

3-Error

[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.

An error condition on the data bus between the SPA and the SIP has occurred. Symptoms of this error include data corruption and/or a short duration of data loss. In addition the interface may lock up.

spa-infra

SPI4_STD_ACTION

SPA_DATABUS-3-SPI4_SINK_FIFO_OVERFLOW

3-Error

[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.

An error condition on the data bus between the SPA and the SIP has occurred. Possible causes include misconfiguration of Maxburst parameters incorrect FIFO sizing or FIFO threshold settings.

spa-infra

SPI4_BUGTOOLKIT_ACTION

SPA_DATABUS-3-SPI4_SINK_FIFO_UNDERRUN

3-Error

[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.

An error condition on the data bus between the SPA and the SIP has occurred. Possible causes include misconfiguration of Maxburst parameters incorrect FIFO sizing or FIFO threshold settings.

spa-infra

SPI4_BUGTOOLKIT_ACTION

SPA_CONSOLE-3-NOBUF

3-Error

No packet buffer available for sending SPA console messages

An error occurred while the SPA console was attempting to acquire a packet buffer from the IPC buffer pool.

-

show ipc status

SPA_CONSOLE-5-CANTSEND

5-Notice

Cannot send SPA console messages.

An error occurred while a SPA console message was being sent via the IPC. This condition might result in a malfunction in the operation of the IPC.

-

show ipc status

SPA_CONSOLE-5-CANTGET

5-Notice

Cannot get SPA client IPC port

SPA console sub-block is not initialized properly.

-

LOG_STD_ACTION

SPA_CONSOLE-5-CANTSET

5-Notice

Cannot set SPA client IPC port.

SPA console sub-block is not initialized properly.

-

LOG_STD_ACTION

SPA_CONSOLE-3-INITFAIL

3-Error

[chars]: SPA console initialization error: [chars].

A failure occurred during initialization of the SPA console subsystem. The SPA console may not be functioning.

-

LOG_STD_ACTION

SPA_CONSOLE-3-BADDETACH

3-Error

SPA console session detach failed with IPC error [chars].

A failure occurred when attempting to detach SPA console subsystem.

-

LOG_STD_ACTION

SPA_CONSOLE-5-QUEUEFULL

5-Notice

Queue holding SPA console messages is full current console packet will be dropped

An error occurred while the SPA console was Queueing a packet for transmission. Some console data may be lost

-

show ipc status

SPA_CONSOLE-3-TX_BUS_PARAM

3-Error

[chars]: VCON_SPACP: Invalid SPA bus parameters.

There was an error sending a message to SPA.

c7600-ssc-600

LOG_STD_RECUR_ACTION

SPA_CONSOLE-3-RX_BUS_PARAM

3-Error

[chars]: VCON_SPACP: Invalid SPA bus parameters.

There was an error receiving a message from SPA.

c7600-ssc-600

LOG_STD_RECUR_ACTION

SPA_CONSOLE-3-NO_DRIVER

3-Error

[chars]: VCON_SPACP: Driver not ready.

SPA sent a message before SIP was fully initialized.

c7600-ssc-600

LOG_STD_RECUR_ACTION

SPA_HA-3-BADSWITCHOVER

3-Error

[chars]: Invalid HA event detected: [chars]

HA switch over event comes before finishing inialization.

-

LOG_STD_SH_TECH_ACTION

BEEP-3-SLOG_LINE

3-Error

[chars] [chars]

This is an internal BEEP library error message.

beep

LOG_STD_ACTION

BEEP-3-SLOG_LINE_TB

3-Error

[chars] [chars]

This is an internal BEEP library error message.

beep

LOG_STD_ACTION

BEEP-3-SESSION_ERR

3-Error

[chars] at [chars]:[dec]

The BEEP subsystem had an error and may stop running.

beep

LOG_STD_ACTION

SPA-3-BAD_FCITYPE

3-Error

[chars]: Illegal FCI type [dec].

An invalid FCI type is passed to SPA. This is a software error.

-

LOG_STD_SH_TECH_ACTION

SPA-3-INITFAIL

3-Error

Initialization error

A failure occurred during the initialization.

spa-infra

LOG_STD_REDUCE_ACTION

SPA-3-ENTITY_INITFAIL

3-Error

SPA entity initialization error

A failure occurred during the SPA entity management subsystem startup. Entity management is not enabled.

spa-infra

LOG_STD_REDUCE_ACTION

SPA-3-SW_ERROR

3-Error

NULL

-

spa-infra

LOG_STD_ACTION

SPA-3-ENVMON_INITFAIL

3-Error

SPA environmental monitoring initialization error

A failure occurred during the SPA environmental monitoring subsystem startup. Environmental monitoring is not enabled.

spa-infra

LOG_STD_REDUCE_ACTION

SPA-3-ENVMON_NOT_MONITORED

3-Error

Environmental monitoring is not enabled for [chars]

The indicated SPA has not registered any sensors with the environmental monitoring system.

-

LOG_STD_SH_TECH_ACTION

SPA-4-TEMP_WARNING

4-Warning

[chars] temperature too high on sensor [dec] [dec]C.

MSG_SPA_TEMP_HIGH_EXP

-

MSG_SPA_TEMP_HIGH_ACTION

SPA-2-TEMP_CRITICAL

2-Critical

[chars] temperature too high on sensor [dec] [dec]C.

MSG_SPA_TEMP_HIGH_EXP Please correct immediately.

-

MSG_SPA_TEMP_HIGH_ACTION

SPA-0-TEMP_SHUTDOWN_OVR

0-Emergency

[chars] temperature too high on sensor [dec] [dec]C but shutdown has been

MSG_SPA_TEMP_HIGH_EXP SPA shutdown has been overridden by configuration

-

MSG_SPA_TEMP_HIGH_ACTION

SPA-0-TEMP_SHUTDOWN

0-Emergency

[chars] temperature too high on sensor [dec] [dec]C. SPA has been shut down.

MSG_SPA_TEMP_HIGH_EXP The SPA has been shut down.

-

MSG_SPA_TEMP_HIGH_ACTION

SPA-4-TEMP_WARNLOW

4-Warning

[chars] temperature too low on sensor [dec] [dec]C.

SPA temperature too low. Component reliability and data integrity may be compromised.

-

"Raise the ambient temperature if it is too low. If there is no " "issue with the ambient temperature then the SPA temperature sensor has " "likely failed. If there are no data errors this warning can be " "ignored."

SPA-4-POWER_WARNING

4-Warning

[chars] power consumption [dec] Watts is higher than typical max value of [dec] Watts.

SPA power consumption is higher than the typical max value. Component reliability and data integrity may be compromised.

-

"Check for the total power available for the system. If " "there is sufficient power availabe this condition may not have " "any adverse affects."

SPA-2-VOLT_CRITICAL

2-Critical

[chars] voltage outside of nominal range. Nominal [dec]mV value[dec]mV

MSG_SPA_VOLT_EXP_COMMON

-

MSG_SPA_VOLT_ACTION_SCHED_REPLACE

SPA-2-VOLT_SHUTDOWN_OVR

2-Critical

[chars] voltage outside of operating range. Nominal [dec]mV value[dec]mV.

MSG_SPA_VOLT_EXP_COMMON

-

MSG_SPA_VOLT_SCHED_REPLACE

SPA-0-VOLT_SHUTDOWN

0-Emergency

[chars] voltage out of operating range. Nominal [dec]mV value [dec]mV.

MSG_SPA_VOLT_EXP_COMMON The SPA has been shut down to prevent component damage.

-

"Replace the SPA immediately. " "Record the associated messages and return the SPA for service."

SPA_OIR-3-MESSAGE_ERROR

3-Error

[chars]: SPA OIR event message error - [chars][dec]

An error was detected in a SPA OIR event message for the SPA in the slot or subslot specified in the error message. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition could be caused by software or hardware problem but a software problem is more likely. For distributed platforms SPA OIR messages are transported over different media depending on the platform for example c12000 uses the MBUS. An unlikely cause of this error is that an event message

spa-infra

SPA_OIR_EVENT_RECOVERY_ACTION

SPA_OIR-3-UNEXPECTED_EVENT

3-Error

[chars]: SPA OIR unexpected event[dec]

An unexpected SPA OIR event was detected for the SPA in the slot or subslot specified in the error message. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition could be caused by software or hardware problem but a software problem is more likely. For distributed platforms SPA OIR messages are transported over different media depending on the platform for example c12000 uses the MBUS. An unlikely cause of this error is that an event message

spa-infra

SPA_OIR_EVENT_RECOVERY_ACTION

SPA_OIR-3-INVALID_EVENT

3-Error

[chars]: Invalid [chars] event received when SPA is undergoing Minimal Disruptive Restart

An unexpected event was detected when the SPA was was undergoing Minimal Disruptive Restart. This condition is most likely a software problem. The SPA will be reset as normal and this will impact traffic.

spa-infra

SPA_OIR_EVENT_RECOVERY_ACTION

SPA_OIR-3-EVENT_DATA_ERROR

3-Error

SPA OIR event data error - [chars][dec]

Invalid data was detected within a SPA OIR event. The SPA OIR state machines may not reflect the state of the hardware. The problem only affects one SPA but the SPA cannot be determined from the context where the error was detected. This condition could be caused by software or hardware problem but a software problem is more likely. For distributed platforms SPA OIR messages are transported over different media depending on the platform for example c12000 uses the MBUS. An unlikely cause of this error is that an event message

spa-infra

"Check the system log for other messages that may help determine " "which SPA is affected. " SPA_OIR_EVENT_RECOVERY_ACTION

SPA_OIR-3-POST_EVENT_ERROR

3-Error

[chars]: event [dec]

A SPA OIR event message was not enqueued for the SPA in the slot or subslot specified in the error message. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition is most likely due to a software problem.

spa-infra

SPA_OIR_EVENT_RECOVERY_ACTION

SPA_OIR-3-UNEXPECTED_RECOVERY_ACTION

3-Error

[chars]: SPA [chars] unexpected recovery action[dec] for fail code 0x[hec]

An error occured while processing a failure message for the SPA in the slot or subslot number specified in the error message. The recovery action to be taken after a SPA failure is determined by calling a SPA driver function. This message indicates that the SPA driver function returned an invalid recovery action. After this message was issued the SPA was reloaded in an attempt to recover. The SPA driver most likely returned an invalid recovery action because of a software problem.

-

SPA_OIR_AUTO_RECOVERY_ACTION

SPA_OIR-3-EVENT_HANDLING

3-Error

[chars]: [chars]0x[hec]

A data structure error was detected when handling a SPA OIR event for the SPA in the slot or subslot specified in the error message. The SPA OIR state machines may not reflect the state of the hardware. This condition is most likely due to a software problem.

spa-infra

SPA_OIR_STD_ACTION

SPA_OIR-3-CMD_ATTR

3-Error

[chars]: Unexpected command identifier [dec]

An unexpected command identifier was detected when processing command related to a SPA OIR. The command was not processed. This is most likely due to a software problem.

spa-infra

SPA_OIR_STD_ACTION

SPA_OIR-2-INITFAIL

2-Critical

SPA OIR initialization error

A failure occurred during the SPA OIR subsystem startup. SPA OIR is not functional for the RP or line card that generated the message.

-

LOG_STD_REDUCE_ACTION

SPA_OIR-2-SUBSLOTINITFAIL

2-Critical

SPA OIR initialization error for [chars]

A failure occurred during the SPA OIR subsystem startup. SPA OIR is not functional for the slot or subslot specified in the error message

-

LOG_STD_REDUCE_ACTION

SPA_OIR-3-EVENT_TIMEOUT

3-Error

[chars]: Timeout waiting for SPA OIR event

A timeout occurred for the subslot specified in the error message while waiting for a SPA OIR event. The SPA did not complete initialization. When this error occurs the system attempts automatic recovery by reloading the SPA. This condition could be caused by software or hardware problem but a software problem is more likely. For distributed platforms SPA OIR event are transported over different media depending on the platform for example c12000 uses the MBUS. An unlikely cause of this error is that an event message

-

SPA_OIR_AUTO_RECOVERY_ACTION

SPA_OIR-3-SW_INIT_TIMEOUT

3-Error

[chars]: SPA initialization not completed

A timeout occurred for the subslot specified in the error message while waiting for SPA software driver to initialize the SPA. The SPA did not complete initialization. When this error occurs the system attempts automatic recovery by reloading the SPA. This condition could be caused by software firmware or hardware problem but a software or firmware problem is more likely.

-

"Check for other messages reported for futher insight. " "Hardware replacement should not occur first occurrence. " "Before requesting hardware replacement review troubleshooting logs " "with a Cisco techinical support representative. " SPA_OIR_AUTO_RECOVERY_ACTION

SPA_OIR-3-HW_INIT_TIMEOUT

3-Error

[chars]

A timeout occurred for the subslot specified in the error message while waiting for SPA hardware to initialize. The SPA did not complete initialization. When this error occurs the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software firmware or hardware problem but a firmware or hardware problem is more likely.

-

SPA_OIR_AUTO_RECOVERY_ACTION

SPA_OIR-3-OUT_OF_SYNC

3-Error

[chars]: failure code 0x[hec]

The software SPA OIR state did not match the hardware state for the subslot in the error message. When this error occurs the system attempts automatic recovery by reloading the SPA. This condition is expected if a SPA is reloading when an RP switchover occurs. Otherwise this condition could be caused by a software firmware or hardware problem but a firmware or software problem is more likely. This condition could also be caused by a rare interaction between SPA and its SIP.

-

SPA_OIR_AUTO_RECOVERY_ACTION

SPA_OIR-3-HW_SIGNAL_DEASSERTED

3-Error

[chars]

The SPA was not brought up because the SPA bay is in an admin down state. The SPA bay will appear as <CmdBold>hw-module<NoCmdBold> <target spa> <CmdBold>shutdown<NoCmdBold> in the running configuration.

-

"Use the <CmdBold>no hw-module<NoCmdBold> <target spa> " "<CmdBold>shutdown<NoCmdBold> command to administratively enable " "the SPA bay."

SPA_OIR-6-PRECONFIG_MISMATCH

6-Information

[chars]: Inserted SPA type does not match preconfigured SPA type. Configuration updated

This message reports a mismatch between the inserted SPA type and the preconfigured SPA type on platforms that support pre-configuration. The inserted SPA replaces the preconfigured SPA.

-

"Check the configuration with the <CmdBold>show run<NoCmdBold> command. " "If you would like to revert to the preconfigured type remove the SPA " "and then update the configuration from a backup"

SPA_OIR-3-SPA_POWERED_OFF

3-Error

[chars]: SPA [chars] powered off after [dec] failures within [dec] seconds

The SPA was powered off because it failed too often. This condition may be caused by a software firmware or hardware error.

-

"Look for other error messages related to this SPA subslot to " "determine root cause of the failure. " SPA_OIR_EVENT_RECOVERY_ACTION

SPA_OIR-3-CORRUPT_EVENT

3-Error

[chars]

Corruption was detected within a SPA OIR event for the subslot specified in the error message. When this error occurs the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software firmware or hardware problem but a firmware or software problem is more likely. For distributed platforms SPA OIR events are transported over different media depending on the platform for example c12000 uses the MBUS. An unlikely cause of this error is that an event message

-

SPA_OIR_AUTO_RECOVERY_ACTION

SPA_OIR-3-UNRECOGNIZED

3-Error

The SPA of type 0x%X in [chars] is not recognized

The type of the SPA in the specified subslot is not recognized by the operating system. The operating system might not support this SPA type on this platform or the SPA type identification stored on the SPA is invalid.

-

"Ensure that the system is running a version of the operating " "system that supports the SPA type specified in the error " "message on this platform. If the correct operating system " "version is in use copy the error message exactly as it " "appears on the console or in the system log contact your " "Cisco technical support representative and provide the " "representative with the gathered information. Include the " "information about the SPA type found on the front of the " "SPA."

SPA_OIR-3-UNSUPPORTED

3-Error

The [chars] in [chars] is not supported by the [chars] module

The SPA in the subslot specified in the error message is not supported in the specified SIP by the version of the operating system currently running on the system. The SPA type may be supported by another SIP or by a later operating system release.

-

"Ensure that the SIP specified in the error " "message supports the specified SPA type. Ensure that the " "operating system release supports the SPA type in the SIP. " "It may be necessary to upgrade your system to " "the latest operating system release in your release train or " "it may be necessary to use a different SIP type. If " "the SPA type specified in the error message does not match the " "interface types or numbers shown on the front of the SPA copy " "the error message exactly as it appears on the console or in " "the system log contact your Cisco technical support " "representative and provide the representative with the " "gathered information. Include information regarding the SPA " "type found on the front of the SPA."

SPA_OIR-3-RECOVERY_RELOAD

3-Error

[chars]: Attempting recovery by reloading SPA

The OIR facility attempted automatic recovery by reloading the SPA in the subslot specified in the error message. Look for other error messages related to this SPA subslot to determine the failure that triggered the automatic recovery.

-

LOG_STD_NO_ACTION

SPA_OIR-6-REMCARD

6-Information

Card removed from [chars] interfaces disabled

The OIR facility detected the removal of a SPA from the slot or subslot number specified in the error message. The interfaces on that SPA will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.

-

LOG_STD_NO_ACTION

SPA_OIR-6-INSCARD

6-Information

Card inserted in [chars]

The OIR facility detected a newly inserted SPA. The interfaces associated with that SPA are operational but will be shut down until they are configured by the user. If any interfaces of that type were previously configured they will be restored to their previous state.

-

LOG_STD_NO_ACTION

SPA_OIR-6-ONLINECARD

6-Information

SPA [chars] online in [chars]

The OIR facility detected the state change to online for the SPA in the slot or subslot number specified in the message.

-

LOG_STD_NO_ACTION

SPA_OIR-6-OFFLINECARD

6-Information

SPA [chars] offline in [chars]

The OIR facility detected the state change to offline for the SPA in the slot or subslot number specified in the message.

-

LOG_STD_NO_ACTION

SPA_EEPROM-4-DATA_TRUNCATED

4-Warning

[chars]: Data will be truncated for field type 0x[hec] - size [dec] bytes too

The provided data to be written into the indicated field type of SPA EEPROM is too big and the data will be truncated in order to fit into the allowed space.

spa-infra

"Retry the operation again with a data size that will fit into the " "indicated size for the field type."

SPA_EEPROM-4-CANNOT_UPDATE

4-Warning

[chars]: EEPROM data cannot be updated at this moment because the SPA is not in service.

The EEPROM update operation cannot be performed because the indicated SPA could have been in \out of service\ state \admin down\ state or is trying to get initialized.

spa-infra

"Retry the operation when the SPA is in service. The operational status " "of the SPA can be checked with the <CmdBold>show hw-module subslot" "<NoCmdBold> <CmdArg>slot/subslot<NoCmdArg> <CmdBold>oir<NoCmdBold> " "command. If the SPA is shown in \"out of service\" state correct the " "indicated problem before the retry to update EEPROM. If the state shown " "is in \"admin down\" re-enable the SPA with <CmdBold>no hw-module " "subslot<NoCmdBold> <CmdArg>slot/subslot<NoCmdArg> <CmdBold>shutdown" "<NoCmdBold> command."

SPA_EEPROM-3-RPC_FAILED

3-Error

Failed to send RPC message to [chars] EEPROM of [chars] in [chars] - [chars]

System failed to send a RPC message to read/write the EEPROM of the indicated SPA. The cause of the error condition is shown in the error message.

-

SPA_EEPROM_STD_RESOURCE_ACTION

SPA_EEPROM-3-READ_FAILED

3-Error

Failed to read the EEPROM content of [chars] in [chars] offset=0x[hec] num_byte=[dec]

System failed to read the EEPROM content of the indicated SPA with the specified offset value and number of bytes to read.

-

SPA_EEPROM_STD_BUG_ACTION

SPA_EEPROM-3-WRITE_FAILED

3-Error

Failed to write the EEPROM content for [chars] in [chars] offset=0x[hec] num_byte=[dec]

System failed to write data into the EEPROM of the indicated SPA with the specified offset value and number of bytes to write.

-

SPA_EEPROM_STD_BUG_ACTION

SPA_EEPROM-3-SET_WR_PROTECT_FAILED

3-Error

[chars]: Failed to [chars] the EEPROM write protect mode on [chars].

System failed to enable/disable the write protect mode for SPA EEPROM on the indicated device. This might happen if the device were busy performing other tasks.

-

SPA_EEPROM_STD_BUG_ACTION

SPA_EEPROM-3-FIELD_NOT_FOUND

3-Error

[chars]: Failed to find content of field type 0x[hec] with data size = [dec] bytes. The EEPROM might require an update.

System failed to find the content of the indicated field type from the SPA EEPROM. The format of the EEPROM of the indicated SPA might not be up to date.

spa-infra

SPA_EEPROM_STD_BUG_ACTION

SPA_EEPROM-3-FORMAT_ERROR

3-Error

[chars]: [chars]. The EEPROM might require an update.

A format error has been detected in the EEPROM of the indicated SPA. The type of error is indicated in the error message.

spa-infra

SPA_EEPROM_STD_BUG_ACTION

SPA_EEPROM-3-SW_ERROR

3-Error

NULL

-

spa-infra

LOG_STD_ACTION

DUAL-3-SIA

3-Error

Route [chars] stuck-in-active state in [chars] [dec]. Cleaning up

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOMATCH

3-Error

Nexthop and infosource don't match. N = [chars] I = [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOHANDLE

3-Error

Handle [dec] is not allocated in pool.

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-LINKSTILLUP

3-Error

Link [dec] [chars] still exists on [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-LINKSEXIST

3-Error

Interface [chars] going down and [dec] links exist

-

-

LOG_STD_ACTION

DUAL-3-BADCOUNT

3-Error

Route [chars] [dec] successors [dec] rdbs

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-6-EVENT

6-Information

[chars] [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOSOCKET

3-Error

Unable to open socket for AS [dec]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOBUFFER

3-Error

No buffers available for [dec] byte packet

The DUAL software was unable to allocate a packet buffer. The system\n\ may be out of memory.

-

LOG_STD_SH_TECH_ACTION

DUAL-3-UNKTIMER

3-Error

Unknown timer type [dec] expiration

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-REFCOUNT

3-Error

Negative refcount in pakdesc [hec]

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-3-MULTIFLOW

3-Error

Flow control error [chars] on [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-PEERSEXIST

3-Error

[dec] peers exist on IIDB [chars]

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-3-ANCHORCOUNT

3-Error

Anchor count negative

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-5-NBRCHANGE

5-Notice

[chars] [dec]: Neighbor [chars] [chars] is [chars]: [chars]

A neighbor went up or down.

-

LOG_STD_NO_ACTION

DUAL-6-NBRINFO

6-Information

[chars] [dec]: Neighbor [chars] [chars] is [chars]: [chars]

Information regarding a neighbor.

-

LOG_STD_NO_ACTION

DUAL-3-RDBLEFT

3-Error

Lingering DRDB deleting IIDB dest [chars] nexthop [chars] [chars] origin [chars]

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-3-INTERNAL

3-Error

[chars] [dec]: Internal Error

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-4-PFXLIMITTHR

4-Warning

[chars] [dec]: [chars] threshold prefix level[dec] reached.

-

-

-

DUAL-3-PFXLIMIT

3-Error

[chars] [dec]: [chars] prefix limit reached[dec].

Number of prefixes for eigrp has reached the configured or default limit.

-

"Use \"show ip eigrp accounting\" for details " "on the source of the prefixes and take corrective " "measures."

DUAL-3-BADIGRPSAP

3-Error

Cannot send incremental SAP update to peer on [chars].\n \tIncreasing output-sap-delay may help

An incremental SAP update could not be sent because this might cause\n\ the SAP tables between peers to become out of synch.

novell

"Increase the output SAP delay on the listed interface to reduce\n\ buffer usage. If after changing the delay the message remains\n\ copy the error message exactly as it appears and report it to your\n\ technical support representative."

DUAL-3-BADIGRPSAPTYPE

3-Error

Unsupported SAP type for EIGRP being [chars] - type [hec]

-

novell

"Copy the error message exactly as it appears and report it to your\n\ technical support representative. If possible also provide the output\n\ of the <bold>debug ipx sap activity<nobold> and <bold>debug ipx sap event<nobold> commands for the\n\ period during which this message appeared."

DUAL-3-SIA

3-Error

Route [chars] stuck-in-active state in [chars] [dec]. Cleaning up

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOMATCH

3-Error

Nexthop and infosource don't match. N = [chars] I = [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOHANDLE

3-Error

Handle [dec] is not allocated in pool.

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-LINKSTILLUP

3-Error

Link [dec] [chars] still exists on [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-LINKSEXIST

3-Error

Interface [chars] going down and [dec] links exist

-

-

LOG_STD_ACTION

DUAL-3-BADCOUNT

3-Error

Route [chars] [dec] successors [dec] rdbs

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-6-EVENT

6-Information

[chars] [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOSOCKET

3-Error

Unable to open socket for AS [dec]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-NOBUFFER

3-Error

No buffers available for [dec] byte packet

The DUAL software was unable to allocate a packet buffer. The system\n\ may be out of memory.

-

LOG_STD_SH_TECH_ACTION

DUAL-3-UNKTIMER

3-Error

Unknown timer type [dec] expiration

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-REFCOUNT

3-Error

Negative refcount in pakdesc [hec]

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-3-MULTIFLOW

3-Error

Flow control error [chars] on [chars]

A hardware or software error occurred.

-

LOG_STD_ACTION

DUAL-3-PEERSEXIST

3-Error

[dec] peers exist on IIDB [chars]

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-3-ANCHORCOUNT

3-Error

Anchor count negative

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-5-NBRCHANGE

5-Notice

[chars] [dec]: Neighbor [chars] [chars] is [chars]: [chars]

A neighbor went up or down.

-

LOG_STD_NO_ACTION

DUAL-6-NBRINFO

6-Information

[chars] [dec]: Neighbor [chars] [chars] is [chars]: [chars]

Information regarding a neighbor.

-

LOG_STD_NO_ACTION

DUAL-3-RDBLEFT

3-Error

Lingering DRDB deleting IIDB dest [chars] nexthop [chars] [chars] origin [chars]

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-3-INTERNAL

3-Error

[chars] [dec]: Internal Error

A software or hardware error occurred.

-

LOG_STD_ACTION

DUAL-4-PFXLIMITTHR

4-Warning

[chars] [dec]: [chars] threshold prefix level[dec] reached.

-

-

-

DUAL-3-PFXLIMIT

3-Error

[chars] [dec]: [chars] prefix limit reached[dec].

Number of prefixes for eigrp has reached the configured or default limit.

-

"Use \"show ip eigrp accounting\" for details " "on the source of the prefixes and take corrective " "measures."

DUAL-3-BADIGRPSAP

3-Error

Cannot send incremental SAP update to peer on [chars].\n \tIncreasing output-sap-delay may help

An incremental SAP update could not be sent because this might cause\n\ the SAP tables between peers to become out of synch.

novell

"Increase the output SAP delay on the listed interface to reduce\n\ buffer usage. If after changing the delay the message remains\n\ copy the error message exactly as it appears and report it to your\n\ technical support representative."

DUAL-3-BADIGRPSAPTYPE

3-Error

Unsupported SAP type for EIGRP being [chars] - type [hec]

-

novell

"Copy the error message exactly as it appears and report it to your\n\ technical support representative. If possible also provide the output\n\ of the <bold>debug ipx sap activity<nobold> and <bold>debug ipx sap event<nobold> commands for the\n\ period during which this message appeared."

LLIST-3-ONLIST

3-Error

[chars] to 0x[hec] 0x[hec] on list

An internal inconsistency was detected when an attempt was made to\n\ add an item to a list already on the list.

tag-switch

"Copy the message exactly as it appears and report it to your technical\n\ service representative."

LLIST-3-OFFLIST

3-Error

[chars] from 0x[hec] 0x[hec] not on list

TXTHREAD API returned a perror.

tag-switch

"Copy the message exactly as it appears and report it to your technical\n\ service representative."

MPLS_TE_HA-3-PROCESS_CREATE_FAILED

3-Error

Failed to create RSVP HA process

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process"

MPLS_TE_HA-3-PROCESS_KILL

3-Error

Killing RSVP HA process

system may be low on memory. Failed to create RSVP HA \n services

mpls-te

LOG_STD_NO_ACTION

MPLS_TE_HA-3-CF_REGISTER_FAILED

3-Error

Failed to register with CF

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process and \n" "re-register with CF"

MPLS_TE_HA-3-RF_REGISTER_FAILED

3-Error

Failed to register with RF

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process and \n" "re-register with CF"

MPLS_TE_HA-3-RF_UNREGISTER_FAILED

3-Error

Failed to unregister with RF

RSVP HA client may not have registered with RF

mpls-te

LOG_STD_NO_ACTION

MPLS_TE_HA-3-CLI_ADD_FAILED

3-Error

Failed to add RSVP HA to CLI

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process and \n" "re-register with CF"

MPLS_TE_HA-3-DB_INIT_FAILED

3-Error

Database init failed

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process and \n" "re-register with CF"

MPLS_TE_HA-3-MSG_MGR_INIT_FAILED

3-Error

Message Manager init failed

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process and \n" "re-register with CF"

MPLS_TE_HA-3-ISSU_INIT_FAILED

3-Error

In Service Software Upgrade ISSU Init failed

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process and \n" "re-register with CF"

MPLS_TE_HA-3-MAIN_INIT_FAILED

3-Error

Main init failed

system may be low on memory

mpls-te

"Verify system memory availability. Then deconfigure \n" "graceful restart full-mode and configure it again. \n" "This will attempt to re-start the RSVP HA process and \n" "re-register with CF"

MPLS_TE_HA-3-ENTRY_MOVE_FAILED

3-Error

Failed to move a database entry to [chars] tree

An attempt to move a data entry from one wavl tree to another wavl tree failed

mpls-te

"This error should never happen under normal " "operation and indicates an internal error. " "Open a ddts"

MPLS_TE_HA-3-ITEM_SIZE_TOO_BIG

3-Error

Item size [dec] bigger than default CF buffer [dec] supported by

A database entry cannot be sent to the standby because the database entry doesn't fit in a CF maximum size buffer allowed by the platform.

mpls-te

"This error indicates a problem with design in " "handling platform dependent restrictions. " "Open a ddts"

MPLS_TE_HA-3-SSO_UNSUPPORTED

3-Error

Attempt to init RSVP HA subsystem when TE SSO not supported

RSVP TE SSO is included in image that doesn't support SSO

mpls-te

"This error indicates a problem with design in. " "Open a ddts"

MPLS_TE_NSR-3-RESEQUENCE_ERROR

3-Error

Error occurred during TE NSR resequence

An unrecoverable error occurred during TE NSR resequence of state

mpls-te

"Disable and then reenable TE NSR functionality and " "open a DDTS"

TENSRFSM-3-NULLMACH

3-Error

Invalid machine pointer 0x%X

state machine invalid pointer

mpls-te

LOG_STD_ACTION

TENSRFSM-3-INVSTATE

3-Error

Invalid current state 0x%X

state machine invalid state

mpls-te

LOG_STD_ACTION

TENSRFSM-3-INVEVENT

3-Error

Invalid event_id 0x%X

state machine invalid event

mpls-te

LOG_STD_ACTION

TENSRFSM-3-INVTRANS

3-Error

obj: [0x%08X] event_id: [0x%08X] er_p: [0x%08X] arg: [0x%08X] session state [chars] -> [chars]

state machine invalid transition

mpls-te

LOG_STD_ACTION

TENSRFSM-3-NOEVENT

3-Error

Unable to apply event 0x%08X

state machine transition failure

mpls-te

LOG_STD_ACTION

TENSRFSM-3-NOPROCID

3-Error

Unable to launch TE NSR FSM Process.

state machine transition process launch failure

mpls-te

LOG_STD_ACTION

MPLS_TE_PCALC-3-INIT

3-Error

[chars]

An internal inconsistency was detected during MPLS TE path calculation initialization such as an attempt was made to initialize the MPLS TE path calculation system id before the system_id size is known.

mpls-te

LOG_STD_ACTION

MPLS_TE_PCALC-3-PATH

3-Error

[chars]

An internal inconsistency was detected when an attempt was made to establish an MPLS TE tunnel using the MPLS TE path calculation subsystem.

mpls-te

LOG_STD_ACTION

MPLS_TE_PCALC-3-LSA

3-Error

[chars] [chars]

An internal inconsistency was detected when an attempt was made to establish handle received lsa for MPLS TE topology database.

mpls-te

LOG_STD_ACTION

MPLS_TE_PCALC-2-MEM

2-Critical

[chars] [dec]

A failure at an attempt to alloc memory was detected

mpls-te

LOG_STD_ACTION

MPLS_TE_PCALC-2-DUP_RRR_ID

2-Critical

[chars] [chars] [chars]

Two nodes have the same stable router id

mpls-te

"Find the system that has the duplicate router id and configure a " "different one"

MPLS_TE_PCALC-2-INVLD_RTR_ID

2-Critical

Invalid router id [chars] received from [chars] in fragment %lu

Received an Invalid Router LSA. LSA should not contain a Router id of zero. The cause of this problem may be misconfiguration memory corruption or unexpected behaviour on a router

mpls-te

"Locate the problem router and check the configuration. " "To determine what is causing this problem call " "your Cisco technical support representative for assistance."

MPLS_TE_PCALC-2-INVLD_RTR_FRAGMENT

2-Critical

Router id [chars] received from [chars] in fragment %lu

Received Router ID in multiple fragments

mpls-te

"Locate the problem router and contact your Cisco " "technical support representative for assistance."

MPLS_TE_PCALC-2-DUP_IP_ADDRESS

2-Critical

[chars] [chars] [chars]

Two nodes have the same stable ip address

mpls-te

"Find the system that has the duplicate ip address and configure a " "different one"

MPLS_TE_LM-5-CLEAR_COUNTERS

5-Notice

Clear MPLS TE Link Management counters by [chars]

The MPLS TE Link Management counters have been cleared

mpls-te

LOG_STD_NO_ACTION

MPLS_TE_LM-3-CONSISTENCY

3-Error

[chars]: [chars] [chars] [chars]

An action attempted by the MPLS TE Link Management implementation encountered an unexpected condition

mpls-te

"Copy the message exactly as it appears and report it to your " "technical service representative."

MPLS_TE_LM-3-LSP_BAD_SWITCHING_TYPE_REQUESTED

3-Error

[chars]: LSP requests switching type [[chars]] unsupported on link [[chars]]

-

-

-

MPLS_TE_LM-3-LSP_BAD_GPID_REQUESTED

3-Error

[chars]: LSP requests G-PID unsupported or invalid

-

-

-

MPLS_TE_LM-3-LSP_BAD_ENCODING_TYPE_REQUESTED

3-Error

[chars]: LSP requests encoding type unsupported or invalid

The indicated TE LSP routed on the indicated interface requested a Switching Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.

mpls-te

"Verify that the head end originating the TE LSP has a Generalized " "Label Request that is specifying a Switching Type acceptable to the " "interface in question. If not alter the head end configuration " "to request an LSP with an appropriate value or cause the LSP " "to be routed on a different interface. " "If this problem still persists copy the error message exactly as " "it appears on the console or in the system log. Please perform " "a search of the Bug Toolkit " BUG_TOOLKIT ". If you need additional " "assistance open a case with the Technical Assistance Center via " "the Internet " TAC_CASE_OPEN " or contact your Cisco technical " "support representative. Please provide the output of " "<cmdBold>show tech-support<nocmdBold> and a topology diagram " "showing the hops in the LSP marking each hop with the " "vendor/software and identify which hop is the IOS device issuing " "the error message."

MPLS_TE_LM-3-LSP_BAD_ENCODING_TYPE

3-Error

LSP [chars] requesting Encoding Type [[chars]] that is unsupported on interface [chars].

The indicated TE LSP routed on the indicated interface requested an Encoding Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.

mpls-te

"Verify that the head end originating the TE LSP has a Generalized " "Label Request that is specifying an Encoding Type acceptable to the " "interface in question. If not alter the head end configuration " "to request an LSP with an appropriate value or cause the LSP " "to be routed on a different interface. " "If this problem still persists copy the error message exactly as " "it appears on the console or in the system log. Please perform " "a search of the Bug Toolkit " BUG_TOOLKIT ". If you need additional " "assistance open a case with the Technical Assistance Center via " "the Internet " TAC_CASE_OPEN " or contact your Cisco technical " "support representative. Please provide the output of " "<cmdBold>show tech-support<nocmdBold> and a topology diagram " "showing the hops in the LSP marking each hop with the " "vendor/software and identify which hop is the IOS device issuing " "the error message."

MPLS_TE_LM-3-LSP_BAD_SWITCHING_TYPE

3-Error

LSP [chars] requesting Switching Type [[chars]] that is unsupported on interface [chars].

The indicated TE LSP routed on the indicated interface requested a Switching Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.

mpls-te

"Verify that the head end originating the TE LSP has a Generalized " "Label Request that is specifying a Switching Type acceptable to the " "interface in question. If not alter the head end configuration " "to request an LSP with an appropriate value or cause the LSP " "to be routed on a different interface. " "If this problem still persists copy the error message exactly as " "it appears on the console or in the system log. Please perform " "a search of the Bug Toolkit " BUG_TOOLKIT ". If you need additional " "assistance open a case with the Technical Assistance Center via " "the Internet " TAC_CASE_OPEN " or contact your Cisco technical " "support representative. Please provide the output of " "<cmdBold>show tech-support<nocmdBold> and a topology diagram " "showing the hops in the LSP marking each hop with the " "vendor/software and identify which hop is the IOS device issuing " "the error message."

MPLS_TE_LM-3-LSP_BAD_GPID

3-Error

LSP [chars] requesting G-PID [[chars]] that is unsupported on interface [chars][chars].

The indicated TE LSP routed on the indicated interface requested a Generalized Payload Identifier unsupported on the

mpls-te

"Verify that the head end originating the TE LSP has a " "Label Request that is specifying a PID acceptable to the " "interface in question. If not one possibility is to alter the " "head end configuration to request an LSP with an appropriate value. " "Alternatively if this error is generated at the penultimate hop of " "an LSP where the endpoint is advertising an implicit-null label " "penultimate hop popping is in use alter the endpoint to "

MPLS_TE_LM-3-GMPLS_UNSUPPORTED_RESOURCE

3-Error

Interface [chars]: GMPLS [chars] labels unsupported

The indicated interface is unable to provide labels of the indicated type.

mpls-te

LOG_STD_SH_TECH_ACTION

MPLS_TE_LM-3-INVALID_LSP

3-Error

A valid LSP must be present for [chars]

A valid LSP is required for this action. This is not a typical occurrence.

mpls-te

LOG_STD_NO_ACTION

MPLS_TE_AUTOMESH-5-AUTOTEMPLATE_HWIDB_DELETE

5-Notice

Failed to delete hwidb for Auto-Template [dec] index [dec]

Deletion of Auto-Template interface failed.

mpls-te

LOG_STD_ACTION

MPLS_TE_AUTO_TUN-3-LOCK_DOUBLE

3-Error

Unexpected data structure access. Non-zero lock count [dec] when [chars] locks [dec] failure[chars].

MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION

mpls-te

LOG_STD_ACTION

MPLS_TE_AUTO_TUN-3-LOCK_ZERO

3-Error

Unexpected data structure access. [chars] unlocks with count [dec] but not locked [dec] failure[chars].

MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION

mpls-te

LOG_STD_ACTION

MPLS_TE_AUTO_TUN-3-LOCK_COUNT

3-Error

Unexpected data structure access. [chars] unlocks with count [dec] but expected [dec] [dec] failure[chars].

MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION

mpls-te

LOG_STD_ACTION

MPLS_TE_AUTO_TUN-4-REMOVE_FAIL

4-Warning

Removing existing auto tunnels may have failed.[chars][chars] MPLS_TE_AUTO_TUN_STD_CONFIRM Use \show running-config\ to confirm expected configuration. Repeat CLI configuration as needed.

The MPLS Traffic Engineering Auto-Tunnel software detected a possible \ problem removing existing automatic tunnels. It may be necessary to \ repeat the CLI action that caused the removal and reconfiguration of \ automatic tunnels.

mpls-te

LOG_STD_ACTION

MPLS_TE_AUTO_TUN-4-CONFLICT_CFG

4-Warning

[chars]

Conflicting MPLS TE auto-tunnel configuration

mpls-te

"Re-check auto-tunnel configuration for P2P Primary Backup and Mesh" "make sure tunnel-id range are not overlapped."

MPLS_TE-3-SIGNALLERINIT

3-Error

Signaller unable to [chars]register RSVP [chars]

A message handler used by the signaller to receive events or requests from RSVP could not be installed or removed.

mpls-te

"Copy and save the message. If possible re-start " "the TSP tunnel signalling process by issuing the " "no tag-switching tsp-tunnels command followed by " "the tag-switching tsp-tunnels command. If the " "message continues to occur even after re-starting " "the signalling process several times then contact " "your technical support representative for " "assistance."

MPLS_TE-3-TUNNELKILL

3-Error

Tunnel removal attempt by [chars] failed for tunnel [chars]: [chars]

-

-

-

MPLS_TE-3-CONSISTENCY

3-Error

[chars]: [chars] [chars] [chars]

An action attempted by the traffic engineering tunnel implementation encountered an unexpected condition

mpls-te

"Copy the message exactly as it appears and report it to your " "technical service representative."

MPLS_TE-4-LSPREJECT

4-Warning

LSP [chars] rejected: matching passive TE tunnel [chars]

An RSVP Path message for an LSP for a tunnel was rejected with a PathErr message due to the absence of a properly configured MPLS passive tunnel interface which is administratively up.

mpls-te

"Create and/or properly configure an MPLS passive tunnel interface " "which will match the rejected LSP and ensure that it is " "administratively up or modify the tunnel interface configuration " "at the head end of the tunnel."

MPLS_TE-5-LSP

5-Notice

[chars]

An informational traffic engineering tunnel trap was generated for an LSP event.

mpls-te

"Copy the message exactly as it appears and report it to your " "technical service representative."

MPLS_TE-5-TUN

5-Notice

[chars]

An informational traffic engineering tunnel trap was generated for a Tunnel event.

mpls-te

"Copy the message exactly as it appears and report it to your " "technical service representative."

MPLS_TE-5-FRR

5-Notice

[chars]

An informational traffic engineering tunnel trap was generated for an MPLS Fast-Reroute event.

mpls-te

"Copy the message exactly as it appears and report it to your " "technical service representative."

MPLS_TE-3-PHYSINTFCDOWN

3-Error

[chars]'s LSP interface [chars] did not come up after [dec] msecs

The underlying interface for a tunnel LSP did not come up although the tunnel itself is up.

mpls-te

"See if the underlying interface is physically connected."

MPLS_TE-3-MFIERROR

3-Error

[chars]: [chars] [chars]

A traffic engineering request to the label switching database encountered an unexpected condition

mpls-te

"Copy the message exactly as it appears and report it to your " "technical service representative."

MPLS_TE-2-BUNDLE_INSERT

2-Critical

[chars] [chars]

Request for inserting a traffic engineering tunnel bundle failed.

mpls-te

LOG_STD_ACTION

MPLS_TE-2-UNSUPPORTED_LINK_TYPE

2-Critical

[chars]

Unsupported link type

mpls-te

LOG_STD_ACTION

MPLS_TE-2-ADJ_WALK_ERR

2-Critical

[chars]

Error during bundle adjacency walk

mpls-te

LOG_STD_ACTION

MPLS_TE-4-CONFLICT_BIDIR_CFG

4-Warning

[chars]

Conflicting bidirectional association configuration

mpls-te

"Re-check tunnel configuration and make sure destination of tunnel" "is properly set and the bidirectional association is unique against" "all tunnels."

MPLS_TE-4-PCEP_REPORT_FAILED

4-Warning

LSP TID:[dec] LID:[dec] wasn't reported to the PCE server

-

-

-

MPLS_TE-4-PCEP_REQUEST_FAILED

4-Warning

Unable to request path for LSP TID:[dec] LID:[dec] from PCE server

-

-

-

PROCESS_CREATE_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

PROCESS_KILL-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

CF_REGISTER_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

RF_REGISTER_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

RF_UNREGISTER_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

CLI_ADD_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

DB_INIT_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

MSG_MGR_INIT_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

ISSU_INIT_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

MAIN_INIT_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

ENTRY_MOVE_FAILED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

ITEM_SIZE_TOO_BIG-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

STATE_FAILURE-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

SSO_UNSUPPORTED-3-MPLS_TE_HA

3-Error

ERRMSG_NOFLAGS

-

-

-

NULLMACH-3-TENSRFSM

3-Error

ERRMSG_NOFLAGS

-

-

-

INVSTATE-3-TENSRFSM

3-Error

ERRMSG_NOFLAGS

-

-

-

INVEVENT-3-TENSRFSM

3-Error

ERRMSG_NOFLAGS

-

-

-

INVTRANS-3-TENSRFSM

3-Error

ERRMSG_NOFLAGS

-

-

-

NOEVENT-3-TENSRFSM

3-Error

ERRMSG_NOFLAGS

-

-

-

NOPROCID-3-TENSRFSM

3-Error

ERRMSG_NOFLAGS

-

-

-

INIT-3-MPLS_TE_PCALC

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

PATH-3-MPLS_TE_PCALC

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

LSA-3-MPLS_TE_PCALC

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

MEM-2-MPLS_TE_PCALC

2-Critical

ERRMSG_FLAG_TRACEBACK

-

-

-

DUP_RRR_ID-2-MPLS_TE_PCALC

2-Critical

ERRMSG_FLAG_TRACEBACK

-

-

-

INVLD_RTR_ID-2-MPLS_TE_PCALC

2-Critical

ERRMSG_NOFLAGS

-

-

-

INVLD_RTR_FRAGMENT-2-MPLS_TE_PCALC

2-Critical

ERRMSG_NOFLAGS

-

-

-

DUP_IP_ADDRESS-2-MPLS_TE_PCALC

2-Critical

ERRMSG_FLAG_TRACEBACK

-

-

-

CLEAR_COUNTERS-5-MPLS_TE_LM

5-Notice

ERRMSG_NOFLAGS

-

-

-

CONSISTENCY-3-MPLS_TE_LM

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

LSP_BAD_SWITCHING_TYPE_REQUESTED-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

LSP_BAD_GPID_REQUESTED-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

LSP_BAD_ENCODING_TYPE_REQUESTED-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

LSP_BAD_ENCODING_TYPE-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

LSP_BAD_SWITCHING_TYPE-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

LSP_BAD_GPID-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

GMPLS_UNSUPPORTED_RESOURCE-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

INVALID_LSP-3-MPLS_TE_LM

3-Error

ERRMSG_NOFLAGS

-

-

-

AUTOTEMPLATE_HWIDB_DELETE-5-MPLS_TE_AUTOMESH

5-Notice

ERRMSG_FLAG_TRACEBACK

-

-

-

LOCK_DOUBLE-3-MPLS_TE_AUTO_TUN

3-Error

ERRMSG_NOFLAGS

-

-

-

LOCK_ZERO-3-MPLS_TE_AUTO_TUN

3-Error

ERRMSG_NOFLAGS

-

-

-

LOCK_COUNT-3-MPLS_TE_AUTO_TUN

3-Error

ERRMSG_NOFLAGS

-

-

-

REMOVE_FAIL-4-MPLS_TE_AUTO_TUN

4-Warning

ERRMSG_NOFLAGS

-

-

-

NOMEM-2-MPLS_TE_EXT_FWDG

2-Critical

ERRMSG_NOFLAGS

-

-

-

REG_FAIL-2-MPLS_TE_EXT_FWDG

2-Critical

ERRMSG_NOFLAGS

-

-

-

DEREG_FAIL-3-MPLS_TE_EXT_FWDG

3-Error

ERRMSG_NOFLAGS

-

-

-

CBERR-3-MPLS_TE_EXT_FWDG

3-Error

ERRMSG_NOFLAGS

-

-

-

GENERIC-3-MPLS_TE_EXT_FWDG

3-Error

ERRMSG_NOFLAGS

-

-

-

UNKNOWN_EVENT-3-MPLS_TE_EXT_FWDG

3-Error

ERRMSG_NOFLAGS

-

-

-

BATCH_ERR-3-MPLS_TE_EXT_FWDG

3-Error

ERRMSG_NOFLAGS

-

-

-

IF_FAIL-2-MPLS_TE_EXT_FWDG

2-Critical

ERRMSG_NOFLAGS

-

-

-

BIND_FAIL-2-MPLS_TE_EXT_FWDG

2-Critical

ERRMSG_NOFLAGS

-

-

-

UNEXPECTEDEVENT-3-MPLS_TE_SCHED

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

UNEXPECTEDQUEUE-3-MPLS_TE_SCHED

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

UNEXPECTEDTIMER-3-MPLS_TE_SCHED

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

UNEXPECTEDMESSAGE-3-MPLS_TE_SCHED

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

NOMEMORY-2-MPLS_TE_SYS

2-Critical

ERRMSG_NOFLAGS

-

-

-

SIGNALLERINIT-3-MPLS_TE

3-Error

ERRMSG_NOFLAGS

-

-

-

TUNNELKILL-3-MPLS_TE

3-Error

ERRMSG_NOFLAGS

-

-

-

CONSISTENCY-3-MPLS_TE

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

LSPREJECT-4-MPLS_TE

4-Warning

ERRMSG_NOFLAGS

-

-

-

LSP-5-MPLS_TE

5-Notice

ERRMSG_NOFLAGS

-

-

-

TUN-5-MPLS_TE

5-Notice

ERRMSG_NOFLAGS

-

-

-

FRR-5-MPLS_TE

5-Notice

ERRMSG_NOFLAGS

-

-

-

PHYSINTFCDOWN-3-MPLS_TE

3-Error

ERRMSG_NOFLAGS

-

-

-

MFIERROR-3-MPLS_TE

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

BUNDLE_INSERT-2-MPLS_TE

2-Critical

ERRMSG_FLAG_TRACEBACK

-

-

-

UNSUPPORTED_LINK_TYPE-2-MPLS_TE

2-Critical

ERRMSG_FLAG_TRACEBACK

-

-

-

ADJ_WALK_ERR-2-MPLS_TE

2-Critical

ERRMSG_FLAG_TRACEBACK

-

-

-

MPLS_TP_MEM-3- NO_MEM

3-Error

Could not allocate memory for MPLS-TP context

Could not allocate memory for MPLS-TP context. This is an internal issue to MPLS-TP

mpls-tp

LOG_STD_ACTION

MPLS_TP_PROC-3- PROC_CREATE_FAIL

3-Error

[chars] [chars] [dec]

Could not create MPLS-TP process. This is an internal issue to MPLS-TP

mpls-tp

LOG_STD_ACTION

MPLS_TP_PROC-3- UNKNOWN_MESSAGE

3-Error

Received unknwon message:[dec]

An unknown message was posted to the MPLS-TP process. This is an internal issue to MPLS-TP

mpls-tp

LOG_STD_ACTION

MPLS_TP_PROC-3- UNKNOWN_EVENT

3-Error

Received unknown event: Major:[dec] Minor:[dec]

An unknown event was posted to the MPLS-TP queue. This is an internal issue to MPLS-TP.

mpls-tp

LOG_STD_ACTION

MPLS_TP_TIMER-3- UNKNOWN_TIMER_TYPE_EXPIRY

3-Error

Unknown timer type expired:[dec]

An unknown MPLS-TP timer type expired. This is an issue internal to MPLS-TP

mpls-tp

LOG_STD_ACTION

MPLS_TP_LSP_FSM-3- LSP_FSM_ERROR

3-Error

LSP FSM Error occurred. Received event:[chars] in state:[chars]

An erroneous event was received by the TP LSP. This is an error internal to MPLS-TP

mpls-tp

LOG_STD_ACTION

MPLS_TP-3-UPDOWN

3-Error

Tunnel-tp[dec] changed state to [chars]

The MPLS-TP tunnel-tp interface changed state.

-

"If the state change was unexpected confirm the configuration settings " "and those of other LSRs along the tunnel LSPs."

MPLS_TP-5-REDUNDANCY

5-Notice

Tunnel-tp[dec] switched to [chars] LSP as active

The MPLS-TP tunnel-tp interface has changed the LSP over which it data traffic is carried possibly due to a fault or administrative action or to restore traffic to the working-LSP after LSP recovery.

-

"If this change is unexpected examine LSP messages to determine " "if a fault or other failure has occurred or is this is due to " "a lockout condition or configuration change."

MPLS_TP-5-CONFIG_CHANGED

5-Notice

Tunnel-tp[dec] is [chars]

The configuration of the tunnel-tp interface has changed. This message is to notify the NMS of changes.

-

LOG_STD_ACTION

MPLS_TP-5-PSCPREEMPTION

5-Notice

Tunnel-tp[dec] PSC Event: [chars] preempted PSC State: [chars] new PSC State: [chars]

The indicated PSC event on the tuunel interface has preempted the indicated psc event which is of lower priority. This message is to notify the NMS of changes.

-

LOG_STD_ACTION

MPLS_PSC-5-TYPE_MISMATCH

5-Notice

Tunnel-tp[dec] type mismatch local-type: [chars] remote-type: [chars]

The local protection type on the indicated MPLS-TP tunnel interface mismatches with the remote protection type. Local and remote protection types are provided.

-

"Examine the local and remote protection types and configure the remote " "protection type to the local protection type."

MPLS_PSC-5-REVERT_MISMATCH

5-Notice

Tunnel-tp[dec] revertive behaviour mismatch: local is [chars] but remote is [chars]

The local revertive mode for the indicated MPLS-TP tunnel interface mismatches with the remote revertive mode. Local and remote revertive modes are provided.

-

"Examine the local and remote revertive modes and configure the remote " "revertive mode to the local revertive mode."

MPLS_TP_LINK-5-CONFIG_CHANGED

5-Notice

Link [dec] interface [chars] next-hop [chars] [chars]

The configuration of the MPLS-TP link has changed. This message is to notify the NMS of changes.

-

LOG_STD_ACTION

MPLS_TP_LSP-3-UPDOWN

3-Error

[chars] LSP [chars] is [chars][chars][chars]

The indicated MPLS-TP LSP has gone up or down. If the LSP went down the failure condition and the fault source information is provided.

-

"Examine the failure condition and source information to determine why " "the LSP went down."

MPLS_TP_LSP-5-LOCKOUT

5-Notice

[chars] LSP [chars] [chars] lockout state

The indicated LSP has entered or exited lockout state due to administrative action at one endpoint

-

LOG_STD_ACTION

MPLS_TP_LSP-5-CONFIG_CHANGED

5-Notice

LSP [chars] is [chars]

The configuration of the MPLS-TP midpoint LSP has changed. This message is to notify the NMS of changes.

-

LOG_STD_ACTION

MPLS_LABEL-5-CHANGED

5-Notice

[chars] min/max label: [dec]/[dec]

The MPLS label range has changed. This message is to notify the NMS of changes.

-

LOG_STD_ACTION

MPLS_TP_BWPOOL-3- BW_POOL_CHANGED

3-Error

Bandiwdth pool available to MPLS-TP has changed

Bandwidth pool available to MPLS-TP has changed. This is either due to the removal of a link or changing to the pool through CLI configuration

mpls-tp

LOG_STD_ACTION

LDPLIB-3-GENERAL

3-Error

[chars]

Record associated with a withdrawn label has timed out before receiving acknowledgements from all peers.

mpls-ldp

"This is an informational message. This will not " "have any operational impact. The system will ignore any subsequently " "received release messages associated with the label."

LDPLIB-3-INIT

3-Error

Cannot allocate LIB

The LIB revision number used to manage advertisement of labels to LDP peers overflowed. This will result in faulty label distribution to LDP peers. The system recovers by toggling dynamic label switching off and on which forces the revision number to be re-initialized.

mpls-ldp

"None required."

LDP-3-GENERAL

3-Error

[chars]

-

mpls-ldp

ACTION_COPY_REPORT_TDP

LDP-3-CONSISTENCY

3-Error

[chars]

-

mpls-ldp

ACTION_COPY_REPORT_TDP

LDP-5-INFO

5-Notice

[chars]

This is an informational message generated by the Label\n\ Distribution Protocol LDP implementation.

mpls-ldp

ACTION_LOOPING_LSP

LDP-3-PTCLREAD

3-Error

peer [chars] read failure

An error occurred while attempting to read a LDP PDU received\n\ from a peer.

mpls-ldp

ACTION_NEW_SESSION_TDP

LDP-5-IDENT

5-Notice

cannot set [chars][chars] LDP ident

-

mpls-ldp

"This is an informational message. As long as it needs to set\n\ its chassis LDP identifier the system will periodically\n\ attempt to do so until it succeeds. If this message occurs\n\ repeatedly copy it exactly as it appears and report it to\n\ your technical service representative."

LDP-3-SM

3-Error

unexpected event: peer [chars][chars] state=[chars] event=[chars][chars]

An operation on the state machine for a LDP peer failed.

mpls-ldp

ACTION_IGNORE_REST_OF_PIE_TDP

LDP-3-KA_NOMEMORY

3-Error

Can't alloc KA message

An attempt to allocate a buffer for Label Distribution Protocol\n\ LDP Keep Alive protocol message has failed.

mpls-ldp

"The system will continue by omitting transmission of the LDP\n\ Keep Alive Message. This may result in termination of one or more\n\ LDP sessions as the peers time out the sessions. If this\n\ message persists reduce other system activity if possible\n\ and call your technical service representative for\n\ assistance."

LDP-3-TAGATM_BAD_RANGE

3-Error

Interface [chars] Bad VPI/VCI range. Can't start a LDP session

The session parameters proposed by an LDP peer differ from those\n\ preferred by the platform. The differences are not sufficient to\n\ prevent the LDP session from being established but may have an\n\ impact on label distribution operation

mpls-ldp

"If the parameters identified relate to the optional path vector-based\n\ loop detection mechanism note that the IETF LDP specification\n\ recommends that when Loop Detection is enabled in a portion of a\n\ network it is recommended that all LSRs in that portion of the\n\ network be configured with Loop Detection enabled and with the\n\ same path vector limit. If the parameters identified relate\n\ to some other aspect of the LDP session and the message occurs\n\ repeatedly copy it exactly as it appears and report it to\n\ your technical service representative."

LDP-3-TAGATM_NOMEM

3-Error

Interface [chars] Resource failure. Can't start a LDP session

An attempt to allocate a buffer for Label Distribution Protocol\n\ LDP TAGATM VPI/VCI ranges has failed.

mpls-ldp

"The system will not be able to create a LDP session between\n\ the affected LDP peers. If this message persists reduce \n\ other system activity if possible and call your technical \n\ service representative for assistance."

LDP-5-ACL

5-Notice

mpls ldp advertise-labels has no effect for lc-atm

EXPLANATION_ACL_TDP

mpls-ldp

"No action is required."

LDP-5-ACL1

5-Notice

mpls ldp advertise-labels has no effect for lc-atm

EXPLANATION_ACL_TDP

mpls-ldp

ACTION_COPY_REPORT_TDP

LDP-4-PTCL

4-Warning

peer [chars] [chars]

A violation of the LDP protocol by a LDP peer has been detected.

mpls-ldp

ACTION_NEW_SESSION_TDP

LDP-4-ADV

4-Warning

Label advertisement mode DU/DoD mismatch with peer [chars] resolved to [chars].

-

mpls-ldp

ACTION_NEW_SESSION_TDP

LDP-5-CLEAR_CHKPT

5-Notice

Clear [chars] checkpoint state [chars] by [chars]

Checkpoint state for one or more LDP objects has been reset

mpls-ldp

LOG_STD_NO_ACTION

LDP-3-ISYNC_CHKPT

3-Error

[chars]:: [chars] request failed [chars]

An unexpected condition happened while uncheckpointing

mpls-ldp

ACTION_COPY_REPORT_TDP

LDP-3-ISSU_XFORM

3-Error

ISSU [chars] transformation failed for msg type [dec][chars].

-

-

-

LDP-3-AUTOCFG

3-Error

Interface [chars] is in an unexpected autoconfig state 0x[hec] [chars] request.

An interface is in an unexpected LDP auto config state. This could\n\ impact the LDP session running on this interface

mpls-ldp

ACTION_COPY_REPORT_TDP

LDP-3-ISYNC

3-Error

[chars]

An unexpected error happened in LDP-IGP Synchronization operation.

mpls-ldp

ACTION_COPY_REPORT_TDP

LDP-5-NBRCHG

5-Notice

[chars] Neighbor [chars] is [chars][chars]

An LDP neighbor has either come up or gone down. The message\n\ describes the change for it.

mpls-ldp

"This informational message normally appears as routers and\n\ LDP neighbors go up or down. However unexpected neighbor loss\n\ might indicate high error rates or high packet loss in the\n\ network and should be investigated."

LDP-5-CLEAR_NBRS

5-Notice

Clear LDP neighbors [chars] by [chars]

One or more LDP neighbor sessions has been reset

mpls-ldp

LOG_STD_NO_ACTION

LDP-5-GR

5-Notice

[chars]

An informational LDP notice was generated for a Graceful Restart event.

mpls-ldp

LOG_STD_NO_ACTION

LDP-3-RECONNECT

3-Error

[chars]

An error occurred while parsing the incoming LDP Initialization message.\n\ The FT Reconnect Timer value received was greater than\n\ the locally-configured Forwarding State Holding Timer value.

mpls-ldp

"Reconfigure the Forwarding State Holding Timer value."

LDP-4-PWD

4-Warning

MD5 protection is required for peer [chars] no password configured

-

mpls-ldp

"This message indicates a misconfiguration on the router. If the\n\ user requires MD5 password protection for the LDP session configure\n\ a password for the LDP peer. If the user requires MD5 password\n\ protection for a subset of LDP neighbors but not for this specific\n\ LDP peer modify the LDP password configuration to exclude this LDP\n\ peer from the password required list. Otherwise if an LDP session\n\ should not exist disable MPLS to this neighbor."

LDP-5-SP

5-Notice

[chars]

An informational LDP notice was generated for a Session Protection event.

mpls-ldp

LOG_STD_NO_ACTION

LDP-5-PWDCFG

5-Notice

Password configuration changed for [chars]

An informational LDP notice was generated to report password\n\ configuration change for a neighbor.

mpls-ldp

LOG_STD_NO_ACTION

LDP-5-PWDRO

5-Notice

Password rolled over for [chars]

An informational LDP notice was generated to report lossless password\n\ change for a neighbor.

mpls-ldp

LOG_STD_NO_ACTION

LDP-5-PWDKEYTRUNC

5-Notice

MD5 digest uses [dec] chars of longer [chars] keys for peer [chars]

-

mpls-ldp

"This message indicates a possible misconfiguration on the router.\n\ Ensure that you have configured your key chains correctly on each\n\ router. Your LDP session can be established if the MD5 key used by\n\ the specified LDP peer has been truncated by the same amount or is\n\ defined to be equal to the truncated key value on this router."

LDP-5-UNKNOWNCAP

5-Notice

Advertised Capability [chars] not supported by peer [chars]

This information message is returned by peer to assist in\n\ troubleshooting interop issues that may arise when a peer is\n\ not capable of supporting an advertised LDP capability

mpls-ldp

LOG_STD_NO_ACTION

LDP-4-CAPCHANGE

4-Warning

Reset of established LDP sessions required to propagate [chars]

A capability was installed/updated/uninstalled by an LDP client.\n\ LDP peers will not learn of the change until the LDP session has\n\ been reset.

mpls-ldp

"Reset LDP neighbor using the 'clear mpls ldp neighbor ...' command."

LDP-4-CAPCHANGE_DYNAMIC

4-Warning

Reset of established LDP session required to propagate [chars]\n change to peers that don't support Dynamic Announcement

A capability was installed/updated/uninstalled by an LDP client.\n\ LDP peers that don't support Dynamic Announcement will not learn\n\ of the changeuntil the LDP session has been reset.

mpls-ldp

"Use the 'show mpls ldp neighbor capability' command to determine\n\ which neighbors need to be reset. Reset LDP neighbor using the\n\ 'clear mpls ldp neighbor ...' command."

LDP-4-MAXMSGSIZE

4-Warning

Maximum implementation message size exceeded actual [dec] maximum [dec]

This is an informational message that appears when LDP receives\n\ a request to allocate memory resources for an LDP message with\n\ a size exceeding the current implemented maximum.

mpls-ldp

"No action is required unless a larger message size is deemed to be\n\ required to support a new application. In this case the actual\n\ application should be identified and component owners contacted\n\ to increase the implemented maximum message size."

LCON-3-CONSISTENCY

3-Error

[chars]

An action attempted by the Label Control process encountered\n\ an unexpected condition.

mpls-ldp

"The request will be ignored. If it repeatedly occurs\n\ copy the message exactly as it appears and report it to your\n\ technical service representative."

LCON-3-ALLOC

3-Error

Cannot alloc [chars]

An attempt to allocate a LDP data structure failed\n\ because of a low memory condition.

mpls-ldp

ACTION_STD_LOW_MEMORY_TAGCON

LCON-3-PROCESS

3-Error

process not created

An attempt to create the label distribution and control process\n\ failed. The probable cause is insufficient memory.

mpls-ldp

ACTION_STD_LOW_MEMORY_TAGCON

LCON-3-INIT

3-Error

process cannot initialize

The label distribution and control process failed to initialize\n\ itself. The probable cause is insufficient memory.

mpls-ldp

ACTION_STD_LOW_MEMORY_TAGCON

LCON-4-INIT_TAG_ALLOC

4-Warning

Failure to initialize label allocation pool [dec]

The system was unable to initialize the data structure used to support\n\ allocation of labels for label switching for the specified label pool.

mpls-ldp

-

LCON-5-SEND

5-Notice

cannot queue LDP [chars] message for [chars][chars]

-

mpls-ldp

"This is an informational message. Failure to queue a message for\n\ a peer should occur only when the LDP session with the peer no\n\ longer exists. The software should recover from this\n\ situation by discarding the LDP session and trying to\n\ establish a new one. If this message occurs repeatedly copy\n\ it exactly as it appears and report it to your technical\n\ service representative."

LCON-3-PEERSM

3-Error

LDP peer [chars][chars]: [chars]

An operation on the state machine for the label distribution and\n\ control process failed.

mpls-ldp

ACTION_COPY_REPORT_TAGCON

LCON-3-DEADADJ

3-Error

[chars] [chars]

An unexpected failure occurred while building a LDP protocol\n\ message for transmission to a LDP peer. It occurred when\n\ attempting to add a label binding or an address to the message.

mpls-ldp

ACTION_COPY_REPORT_TAGCON

LCON-3-RADIXTREE

3-Error

[chars]LIB walk failed [chars]

-

mpls-ldp

ACTION_COPY_REPORT_TAGCON

LCON-3-LDPID

3-Error

peer [chars] LDP Id/Addr mapping problem [chars]

EXPLANATION_ADDR_TBL_TAGCON

mpls-ldp

ACTION_TOGGLE_TAG_IP_TAGCON

LCON-3-DUP_ADDR_RCVD

3-Error

Duplicate Address [chars] advertised by peer [chars] is already bound to [chars]

EXPLANATION_ADDR_TBL_TAGCON

mpls-ldp

ACTION_TOGGLE_TAG_IP_TAGCON

LCON-3-DEFCASE_BINDING_PIE

3-Error

Unexpected blist_type [dec] for [chars] message from peer [chars]

A LDP protocol message received from a LDP peer contained an\n\ unexpected binding list type. The message will be be ignored.

mpls-ldp

ACTION_IGNORE_PIE_TAGCON

LCON-3-REGISTRY

3-Error

Unexpected [chars] for reg_invoke_[chars]

-

mpls-ldp

-

LCON-4-ADDR_PROC

4-Warning

Can't create lcon addr proc

-

mpls-ldp

"This is an informational message. As long as it needs the\n\ process the system will regularly attempt to create it. If\n\ this message occurs repeatedly copy it exactly as it appears\n\ and report it to your technical service representative."

LCON-4-ADDRQ

4-Warning

Can't alloc work item for [chars]

-

mpls-ldp

"This is an informational message. The system remembers that\n\ it needs to do this work and will regularly attempt to queue\n\ the necessary work item. If this message occurs repeatedly\n\ copy it exactly as it appears and report it to your technical\n\ service representative."

LCON-3-EVENTQ

3-Error

Can't alloc work item for [chars]

An operation on the LDP Directed Adjacency data structure\n\ failed.

mpls-ldp

ACTION_COPY_REPORT_TAGCON

LCON-3-LATREVNUMWRAP

3-Error

Label Local Address Table revision number wrapped

The revision number used to manage advertisement of interface\n\ addresses to LDP peers overflowed. This will result in faulty\n\ advertisement of interface addresses to LDP peers and\n\ faulty label switching on those peers.

mpls-ldp

"To restore proper interface address advertisement reboot the\n\ platform. Report this condition to your technical service\n\ representative."

LCON-3-LCLTAG_ALLOC

3-Error

Cannot allocate local label

-

mpls-ldp

"The number of labels available for allocation can be changed\n\ by the <CmdBold>mpls label range ...<NoCmdBold> configuration command.\n\ Consult with your technical service representative to determine\n\ whether you should use this command to increase the number of\n\ available labels."

LCON-3-LABEL_REGION

3-Error

Platform specified information for label region [chars] is invalid.

A platform service routine provides label region information about\n\ all label regions it supports. This error message is printed when\n\ the service routine does not specify its label region information\n\ correctly.

mpls-ldp

"Report this condition to your technical service representative."

LCON-4-CFGD_LBL_REGION

4-Warning

Adjusting configured label range to default range

The saved configuration has been ignored and the default label range\n\ is being used.

mpls-ldp

"Please reconfigure the label range to a valid range using <CmdBold>\n\ mpls label range ... <NoCmdBold> configuration command."

ICPM-3-ALLOC

3-Error

Cannot alloc [chars]

An attempt to allocate an ICPM data structure failed because\n\ of a low memory condition.

mpls-ldp

ACTION_STD_LOW_MEMORY_ICPM

GENERAL-3-LDPLIB

3-Error

ERRMSG_NOFLAGS

-

-

-

INIT-3-LDPLIB

3-Error

ERRMSG_NOFLAGS

-

-

-

GENERAL-3-LDP

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

CONSISTENCY-3-LDP

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

INFO-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

PATH_VEC-4-LDP

4-Warning

ERRMSG_LIMIT_SLOW*15

-

-

-

PTCLREAD-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

IDENT-4-LDP

4-Warning

ERRMSG_LIMIT_SLOW*15

-

-

-

SM-3-LDP

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

KA_NOMEMORY-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

TAGATM_BAD_RANGE-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

TAGATM_NOMEM-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

ACL-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

ACL1-5-LDP

5-Notice

5*ERRMSG_LIMIT_SLOW

-

-

-

PTCL-4-LDP

4-Warning

ERRMSG_NOFLAGS

-

-

-

ADV-4-LDP

4-Warning

ERRMSG_NOFLAGS

-

-

-

CLEAR_CHKPT-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

ISYNC_CHKPT-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

ISSU_XFORM-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

AUTOCFG-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

ISYNC-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

NBRCHG-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

CLEAR_NBRS-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

GR-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

RECONNECT-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

PWD-4-LDP

4-Warning

ERRMSG_NOFLAGS

-

-

-

SP-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

PWDCFG-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

PWDRO-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

PWDKEYTRUNC-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

UNKNOWNCAP-5-LDP

5-Notice

ERRMSG_NOFLAGS

-

-

-

CAPCHANGE-4-LDP

4-Warning

ERRMSG_NOFLAGS

-

-

-

CAPCHANGE_DYNAMIC-4-LDP

4-Warning

ERRMSG_NOFLAGS

-

-

-

MAXMSGSIZE-4-LDP

4-Warning

ERRMSG_LIMIT_SLOW*15

-

-

-

CONSISTENCY-3-LCON

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

ALLOC-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

PROCESS-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

INIT-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

INIT_TAG_ALLOC-4-LCON

4-Warning

ERRMSG_NOFLAGS

-

-

-

SEND-5-LCON

5-Notice

ERRMSG_NOFLAGS

-

-

-

PEERSM-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

DEADADJ-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

RADIXTREE-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

LDPID-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

DUP_ADDR_RCVD-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

DEFCASE_BINDING_PIE-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

REGISTRY-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

ADDR_PROC-4-LCON

4-Warning

ERRMSG_NOFLAGS

-

-

-

ADDRQ-4-LCON

4-Warning

ERRMSG_NOFLAGS

-

-

-

EVENTQ-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

LATREVNUMWRAP-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

LCLTAG_ALLOC-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

LABEL_REGION-3-LCON

3-Error

ERRMSG_NOFLAGS

-

-

-

CFGD_LBL_REGION-4-LCON

4-Warning

ERRMSG_NOFLAGS

-

-

-

SM_CREATE-2-LDP

2-Critical

ERRMSG_NOFLAGS

-

-

-

MALLOC-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

SLAB_CREATE-2-LDP

2-Critical

ERRMSG_NOFLAGS

-

-

-

SLAB_ALLOC-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

INIT-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

STARTTHREAD-1-LDP

1-Alert

ERRMSG_NOFLAGS

-

-

-

THREADEXIT-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

REGISTRATION_FAIL-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

CLIENT-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

SHUTDOWN_REQUEST_FAIL-6-LDP

6-Information

ERRMSG_NOFLAGS

-

-

-

DECONFIG_SHUTDOWN-6-LDP

6-Information

ERRMSG_NOFLAGS

-

-

-

RESTART_SHUTDOWN-4-LDP

4-Warning

ERRMSG_NOFLAGS

-

-

-

UNKNOWN_SHUTDOWN-6-LDP

6-Information

ERRMSG_NOFLAGS

-

-

-

REG_COMP-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

SIGNAL-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

XIPC-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

TIMER-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

THREAD-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

NOTIFY_BUFFER-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

SNMP_FILL-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

CLNT_REG-7-LDP

7-Debug

ERRMSG_NOFLAGS

-

-

-

API_BAD_ARGUMENTS-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

API_MSG-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

API_BAD_RESPONSE-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

API_FAILED-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

MTS_UNKNOWN_MSG-6-LDP

6-Information

ERRMSG_NOFLAGS

-

-

-

MTS_RECV-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

MTS_DROP-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

SYSMGR_SRV_QUERY-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

HA_TLV-2-LDP

2-Critical

ERRMSG_NOFLAGS

-

-

-

SDB_UPDATE-2-LDP

2-Critical

ERRMSG_NOFLAGS

-

-

-

UNAWAKABLE-3-LDP

3-Error

ERRMSG_NOFLAGS

-

-

-

UNEXPECTEDEVENT-3-LDP_SCHED

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

UNEXPECTEDTIMER-3-LDP_SCHED

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

UNEXPECTEDMESSAGE-3-LDP_SCHED

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

UNEXPECTEDMESSAGE-3-LDP_SCHED

3-Error

-

MPLS_LDP Service nabled

SRVNAME_LDP

SYSLOGDOC_NO_ACTION

UNEXPECTEDMESSAGE-3-LDP_SCHED

3-Error

-

MPLS_LDP Service Disabled

SRVNAME_LDP

SYSLOGDOC_NO_ACTION

ALLOC-3-ICPM

3-Error

ERRMSG_NOFLAGS

-

-

-

MPLSOAM-3-XDR_COMM

3-Error

[chars]:0x[hec] 0x[hec]

XDR Comm module - Unexpected RP/LC XDR condition encountered in MPLS OAM software. This may result in MPLS OAM FIB sub-blocks becoming out of synchronization between RP and LC. This should not affect overall system.

mpls-oam

LOG_STD_ACTION

MPLSOAM-3-WALK_CONSUMED

3-Error

[chars]

FWD RPLC Module - Walk packet unexpectedly consumed in MPLS OAM software. This should not affect overall system performance.

mpls-oam

LOG_STD_ACTION

LSPV-3-COMM_UNKNOWN_RC

3-Error

Unexpected oce return code

Comm module - unexpected oce return code encountered

mpls-oam

LOG_STD_ACTION

LSPV-3-TP_ECHO_REQUEST

3-Error

MPLS-TP Echo request unsupported

MPLS-TP echo request was received. Ignoring as MPLS-TP is not supported on this platform

mpls-oam

LOG_STD_ACTION

MPLSOAM-3-UNAUTH_PROXY_REQ

3-Error

Unauthorized proxy request - dropping packet

MPLS-OAM proxy echo request was received. It was unauthorized and hence dropped.

mpls-oam

LOG_STD_ACTION

MPLSOAM-3-XDR_COMM

3-Error

[chars]:0x[hec] 0x[hec]

XDR Comm module - Unexpected RP/LC XDR condition encountered in MPLS OAM software. This may result in MPLS OAM FIB sub-blocks becoming out of synchronization between RP and LC. This should not affect overall system.

mpls-oam

LOG_STD_ACTION

MPLSOAM-3-WALK_CONSUMED

3-Error

[chars]

FWD RPLC Module - Walk packet unexpectedly consumed in MPLS OAM software. This should not affect overall system performance.

mpls-oam

LOG_STD_ACTION

LSPV-3-COMM_UNKNOWN_RC

3-Error

Unexpected oce return code

Comm module - unexpected oce return code encountered

mpls-oam

LOG_STD_ACTION

LSPV-3-TP_ECHO_REQUEST

3-Error

MPLS-TP Echo request unsupported

MPLS-TP echo request was received. Ignoring as MPLS-TP is not supported on this platform

mpls-oam

LOG_STD_ACTION

MPLSOAM-3-UNAUTH_PROXY_REQ

3-Error

Unauthorized proxy request - dropping packet

MPLS-OAM proxy echo request was received. It was unauthorized and hence dropped.

mpls-oam

LOG_STD_ACTION

XDR_COMM-3-MPLSOAM

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

COMM_UNKNOWN_RC-3-LSPV

3-Error

ERRMSG_FLAG_TRACEBACK

-

-

-

COMM_UNKNOWN_RC-3-LSPV

3-Error

-

MPLS_LSPV Service nabled

SRVNAME_MPLS_OAM

SYSLOGDOC_NO_ACTION

COMM_UNKNOWN_RC-3-LSPV

3-Error

-

MPLS_LSPV Service Disabled

SRVNAME_MPLS_OAM

SYSLOGDOC_NO_ACTION

COMM_UNKNOWN_RC-3-LSPV

3-Error

-

MPLS OAM Daemon Initialization failed. [chars] explains the reason for the failure.

SYSLOGDOC_NO_DDTS

SYSLOGDOC_NO_ACTION

COMM_UNKNOWN_RC-3-LSPV

3-Error

-

-

-

-

DEAD-4-SCARLET

4-Warning

* Interface [chars]: I knew without asking she was into the blues

-

-

-

DEAD-4-SCARLET

4-Warning

-

-

-

-

-

4-Warning

fmt \static message_stats * fac ## _ ## name ## _stat_redir_ptr

-

-

-

-

4-Warning

fmt

-

-

-

-

4-Warning

fmt

-

-

-

CFC_SRV6-3-DISPATCH_OCE

3-Error

Failed to [chars] SRv6 dispath oce [chars][chars]

-

-

-

CFC_SRV6-3-END_OCE

3-Error

Failed to [chars] SRv6 end oce [chars][chars]

An internal software error occurred.

CFC_SRV6_MSG_DDTS_COMP

LOG_STD_ACTION

SR-5-SR_POLICY_UPDOWN

5-Notice

POLICY [chars] [chars]

A policy has either come up or gone down.The message describes the change for it.

sr

" This informational message normally appears as a policy go up or down"

SR-5-SR_POLICY_UPDOWN

5-Notice

POLICY [chars] [chars]

A policy has either come up or gone down.The message describes the change for it.

sr-policy-mgr

" This informational message normally appears as a policy go up or down"

SR-3-SR_POLICY_UNLOCK

3-Error

Try to decrease zero refcount for policy %p

Attempt to decrease the refcount of policy when it is already zero.

sr-policy-mgr

LOG_STD_ACTION

OIRLIB-4-NOTRACE

4-Warning

OIR-LIB trace initialization failed[dec]

-

-

-

XMCP-4-CLIENT_ERR_RSP

4-Warning

Received error response [dec] [chars] from client [chars]/[chars]

-

-

-

XMCP-4-CLIENT_DENIED

4-Warning

Client [chars]/[chars] denied: [chars]

An external XMCP client connection was denied. This may be due to a valid configuration reason for example <CmdBold>max-clients<NoCmdBold> or an <CmdBold>allow-list<NoCmdBold> or it may indicate that a protection mechanism has been triggered - for example an authentication failure or DOS attack prevention

-

"Check that this is caused by configuration. If not " "and if the frequency of this message suggests that " "this may be malicious - contant your TAC security " "support immediately"

XMCP-5-CLIENT_CHANGE

5-Notice

Client [chars]/[chars] is [chars]: [chars]

An XMCP client connected or disconnected.

-

LOG_STD_NOACTION

XMCP-5-CLIENT_CHANGE

5-Notice

-

An error occurred during initialization

SISF_COMP_NAME

LOG_STD_ACTION

XMCP-5-CLIENT_CHANGE

5-Notice

-

An internal software error occurred.

SISF_COMP_NAME

LOG_STD_ACTION

XMCP-5-CLIENT_CHANGE

5-Notice

-

A PSS operation was performed

SISF_COMP_NAME

"This is an informationnal message"

XMCP-5-CLIENT_CHANGE

5-Notice

-

An entry was created in the binding table

SISF_COMP_NAME

"This is an informationnal message"

XMCP-5-CLIENT_CHANGE

5-Notice

-

An entry was created in the binding table

SISF_COMP_NAME

"This is an informationnal message"

XMCP-5-CLIENT_CHANGE

5-Notice

-

An entry was changed in the binding table

SISF_COMP_NAME

"This is an informationnal message"

XMCP-5-CLIENT_CHANGE

5-Notice

-

Reached 80% of maximum # addresses for the target

SISF_COMP_NAME

"A client is approaching red zone and might soon \n\ be blocked. The maximum value configured may be too low \n\ and you should consider increasing it. Or some of this client addresses are \n\ stale and you could clear them"

XMCP-5-CLIENT_CHANGE

5-Notice

-

An attempt to install an entry in the IPv6 binding table was blocked. This can be due to a conflicting entry or maximum number of entries reached

SISF_COMP_NAME

"If the maximum table size is reached consider increasing it.\n\ If a conflicting entry already exist this maybe an attempt \n\ to steal address ownership. You should investigate which host\n\ is connected on the interface and wether it should be disconnected"

XMCP-5-CLIENT_CHANGE

5-Notice

-

A duplicate IP address has been detected IP theft and blocked This can be due to a configuration error on end-device an intentional IP theft or an IP movind too quickly

sisf

"If the existing entry is REACHABLE in the binding table and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration issue that must be resolved"

XMCP-5-CLIENT_CHANGE

5-Notice

-

A duplicate MAC address has been detected MAC theft and blocked This can be due to a configuration error on end-device an intentional MAC theft or MAC moving too quickly

SISF_COMP_NAME

"If the existing entry is REACHABLE in the binding table and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration issue that must be resolved"

XMCP-5-CLIENT_CHANGE

5-Notice

-

A duplicate MAC and IP address has been detected MAC_AND_IP theft and blocked This can be due to a configuration error on end-device an intentional MAC_AND_IP theft or MAC moving too quickly

SISF_COMP_NAME

"If the existing entry is REACHABLE in the binding table and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration issue that must be resolved"

XMCP-5-CLIENT_CHANGE

5-Notice

-

-

-

-

-

5-Notice

0

-

-

-

-

5-Notice

-

A data packet notification has been received because a snooping policy with the data glean option is configured and the Source address of the packet is not currently in the Binding Table.

SISF_COMP_NAME

-

-

5-Notice

-

-

ipv6

"A low rate of vetoed resolutions is not serious. \n\ If there is a high rate of vetos this might suggest that \n\ the link is under attack. Investigate the source of the \n\ packets driving these resolution requests"

SISF-3-INTERNAL

3-Error

Internal error [chars]

An internal software error occurred.

sisf

LOG_STD_ACTION

SISF-6-ENTRY_CREATED

6-Information

Entry created [chars]

An entry was created in the binding table

sisf

"This is an informationnal message"

SISF-6-ENTRY_DELETED

6-Information

Entry deleted [chars]

An entry was created in the binding table

sisf

"This is an informationnal message"

SISF-6-ENTRY_CHANGED

6-Information

Entry changed [chars]

An entry was changed in the binding table

sisf

"This is an informationnal message"

SISF-6-ENTRY_MAX_ORANGE

6-Information

Reaching 80%% of max adr allowed per [chars]

Reached 80% of maximum # addresses for the target

sisf

"A client is approaching red zone and might soon \n\ be blocked. The maximum value configured may be too low \n\ and you should consider increasing it. Or some of this client addresses are \n\ stale and you could clear them"

SISF-4-ENTRY_BLOCKED

4-Warning

Entry blocked [chars]

An attempt to install an entry in the IPv6 binding table was blocked. This can be due to a conflicting entry or maximum number of entries reached

sisf

"If the maximum table size is reached consider increasing it.\n\ If a conflicting entry already exist this maybe an attempt \n\ to steal address ownership. You should investigate which host\n\ is connected on the interface and wether it should be disconnected"

SISF-4-IP_THEFT

4-Warning

IP Theft [chars]

A duplicate IP address has been detected IP theft and blocked This can be due to a configuration error on end-device an intentional IP theft or an IP movind too quickly

sisf

"If the existing entry is REACHABLE in the binding table and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration issue that must be resolved"

SISF-4-MAC_THEFT

4-Warning

MAC Theft [chars]

A duplicate MAC address has been detected MAC theft and blocked This can be due to a configuration error on end-device an intentional MAC theft or MAC moving too quickly

sisf

"If the existing entry is REACHABLE in the binding table and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration issue that must be resolved"

SISF-4-MAC_AND_IP_THEFT

4-Warning

MAC_AND_IP Theft [chars]

A duplicate MAC and IP address has been detected MAC_AND_IP theft and blocked This can be due to a configuration error on end-device an intentional MAC_AND_IP theft or MAC moving too quickly

sisf

"If the existing entry is REACHABLE in the binding table and it moved to a new port \n\ consider reducing the REACHABLE timer \n\ otherwise it is either an attack or a configuration issue that must be resolved"

SISF-4-PAK_DROP

4-Warning

Message dropped [chars]

-

-

-

SISF-4-PAK_DROP

4-Warning

Message dropped [chars]

A message was dropped because one of the IPv6 first-hop \n\ security features said so

sisf

"Look at the reason. It can either be a valid drop and the \n\ could go up to disconnect the host attached to the interface \n\ or the policy configured on this interface is too severed \n\ and should be amended"

SISF-4-DATA_GLEAN_NOTIF_RECEIVED

4-Warning

No binding for [chars]

A data packet notification has been received because a snooping policy with the data glean option is configured and the Source address of the packet is not currently in the Binding Table.

sisf

-

SISF-4-RESOLUTION_VETO

4-Warning

Resolution vetoed [chars]

-

ipv6

"A low rate of vetoed resolutions is not serious. \n\ If there is a high rate of vetos this might suggest that \n\ the link is under attack. Investigate the source of the \n\ packets driving these resolution requests"

SISF_TRACKING_HA-4-ENTRY_OUT_OF_SYNC

4-Warning

Host mac-address [enet] ip-address [inet] interface [chars]

An inconsistency has been detected in the IP device tracking table for this host between active and standby

ipv6

LOG_STD_NO_ACTION

SISF_ISSU-2-INIT

2-Critical

Sisf ISSU client initialization failed to [chars]. Error: [dec] [chars]

The Sisf ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure there will be downtime during software upgrade or downgrade.

ipv6

LOG_STD_ACTION

SISF_ISSU-3-TRANSFORM_FAIL

3-Error

Sisf ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] [chars]

The Sisf ISSU client could not transform the specified message type. If the transmit transformation failed the checkpoint message was not sent to the standby device. If the receive transformation failed the checkpoint message was not applied on the standby device. In both cases the Sisf state between the active device and the standby device is not identical.

ipv6

"show issu session <client_id> and " "show issu negotiated version <session_id>"

SISF_ISSU-3-MSG_NOT_OK

3-Error

Sisf ISSU client 'Message Type [dec]' is not compatible

The Sisf ISSU client received an incompatible message from the peer device. The message cannot be processed.

ipv6

"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>"

SISF_ISSU-3-MSG_SIZE

3-Error

Sisf ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] [chars]

The Sisf ISSU client failed to calculate the MTU for the specified message. The Sisf ISSU client is not able to send the message to the standby device.

ipv6

"show issu message group <client_id> and " "show issu session <client_id> and " "show issu negotiated version <session_id>"

SISF_ISSU-3-INVALID_SESSION

3-Error

Sisf ISSU client does not have a valid registered session.

The Sisf ISSU client does not have a valid registered session.

ipv6

"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>"

SISF_ISSU-2-SESSION_REGISTRY

2-Critical

Sisf ISSU client failed to register session information. Error: [dec] [chars]

The Sisf ISSU client failed to register session information. If a problem occurs with the ISSU session registration the standby device cannot be brought up properly.

ipv6

"show issu capability entries <client_id> and " "show issu session <client_id> and " "show issu negotiated capability <session_id>"

SISF_ISSU-3-SESSION_UNREGISTRY

3-Error

Sisf ISSU client failed to unregister session information. Error: [dec] [chars]

The Sisf ISSU client failed to unregister session information.

ipv6

"show issu session <client_id> and " "show issu negotiated capability <session_id>"

SISF_ISSU-2-SESSION_NEGO

2-Critical

Sisf ISSU client encountered unexpected client nego_done. Error: [dec] [chars]

An ISSU-compliant client transitions through a series of internal states. The Sisf ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

ipv6

"show issu session <client_id> and " "show issu negotiated capability <session_id>"

SISF_ISSU-2-SEND_NEGO_FAILED

2-Critical

Sisf ISSU client failed to send negotiation message. Error: [dec] [chars]

The Sisf ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

ipv6

"show logging and show checkpoint client"

SISF_ISSU-2-GET_BUFFER

2-Critical

Sisf ISSU client failed to get buffer for message. Error: [dec] [chars]

The Sisf ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation the standby device cannot be brought up properly.

ipv6

"show logging and show checkpoint client"

SISF_ISSU-3-CAP_NOT_COMPATIBLE

3-Error

Sisf ISSU client capability exchange result incompatible.

The Sisf ISSU client capability exchange have negotiated as incompatible with the peer.

ipv6

"show issu negotiated capability <Session_ID>"

SISF_ISSU-3-CAP_INVALID_SIZE

3-Error

SISF ISSU client capability list is empty.

The SISF ISSU client capability exchange list size is invalid.

ipv6

"show issu capability entires <Client_ID>"

CALL_HOME-3-HTTP_REQUEST_FAILED

3-Error

Failure to send HTTP request to: [chars] ERR [dec] : [chars]

-

-

-

CALL_HOME-5-SL_MESSAGE_FAILED

5-Notice

Fail to send out Smart Licensing message to: [chars] ERR [dec] : [chars]

-

-

-

CALL_HOME-5-HTTPS_NOT_SUPPORTED

5-Notice

This image version does not support HTTPS

This image does not support secure HTTP although user configures https url

call-home

"Please upgrade your system image to a crypto image which supports" "secure http."

CALL_HOME-4-HTTP_ADDRESS_NOT_SUPPORTED

4-Warning

Http will be or has been disabled on Smart Call Home Server please change the address [chars] to https address for profile [chars]. Otherwise call-home will fail to send messages

Http will be or has benn disabled on Smart Call Home Server call-home will fail to send message to the http destination

call-home

"Please change the http address to https address."

CALL_HOME-3-SMTP_SEND_FAILED

3-Error

Unable to send notification using all SMTP servers ERR [dec] [chars]

-

-

-

CALL_HOME-3-CLI_CMD_RUN_FAILED

3-Error

No VTY connection available to run CLI command for event notification message ERR [dec] [chars]

-

-

-

CALL_HOME-3-MESSAGE_SIZE_OVER_LIMIT

3-Error

XML message size over limit failed to send call-home message. configured message size limit [dec] is less than current message

Unable to create message because configured message size limit is smaller than current message minimum length required.

call-home

"Please re-config the destination message-size-limit."

CALL_HOME-4-MESSAGE_IS_TRUNCATED

4-Warning

message size over limit call-home message is truncated. configured message size limit [dec] is less than current message

call-home message is truncated because configured message size limit is smaller than current message total length required.

call-home

"Please re-config the destination message-size-limit."

CALL_HOME-3-REQUEST_MESSAGE_FAILED

3-Error

call-home request message failed to send ERR [dec] [chars]

-

-

-

CALL_HOME-6-REQUEST_MESSAGE_SUCCEEDED

6-Information

call-home request message succeeded

call-home request message was sent successfully.

call-home

"No action is needed. This is informational message."

CALL_HOME-3-ONDEMAND_MESSAGE_FAILED

3-Error

The call-home on-demand message failed to send for [chars][chars]s

The call-home on-demand message failed.

call-home

"Reconfigure call-home to send call-home on-demand messages."

CALL_HOME-6-DS_UPDATE_SUCCESS

6-Information

call-home diagnostic-signature successfully did [chars] download [dec] new diagnostic-signatures will be added

call-home diagnostic-signature downloaded successfully.

call-home

"No action is required."

CALL_HOME-3-DS_UPDATE_FAIL

3-Error

The call-home diagnostic-signature failed to update.

The call-home diagnostic-signature failed to update.

call-home

"Please check the \"show call-home diagnostic-signature failure\" " "command for details."

CALL_HOME-6-DS_UNDECLARED_VARS

6-Information

There're undeclared variables referenced in DS [chars] please use \show call-home diagnostic-signature <ds-id> variables\ to check it. If they're environment variables please configure them to make DS work as expected.

call-home DS file has undeclared variables.It will not work until users configure it.

call-home

"Please check undeclared variables in the DS."

CALL_HOME-6-DS_PROFILE_HTTP_NOT_SET

6-Information

The Email transport method is currently selected for the Smart Call Home service. To download the Diagnostic Signature from the Smart Call Home Server the HTTP transport method must be enabled and a destination HTTP URL must be configured in the [chars] profile.

The call-home diagnostic-signature update will not start because the HTTP transport method is disabled or the URL destination is not configured in the diagnostic-signature profile.

call-home

"This message is informational only."

CALL_HOME-6-DS_REMEDIATION_ACTION

6-Information

The call-home diagnostic-signature [chars] action was performed. Device status such as configuration or line card status may be affected.

The call-home diagnostic-signature remediation actions were performed

call-home

"No action is required."

CALL_HOME-3-CREATE_EVENT_FAILED

3-Error

Failed to create [chars] event for profile [chars]

The call-home event creation failed.

call-home

"Unsubscribe and then subscribe again to that alert group for " "the spec